Skip to content
About the company

Whyone companydoes it all

This is not an item on a capability list. It is the reason this company was founded. It starts with a common scene on site.

ⅠThe problem

When the system does not work,
every vendor can prove it was not at fault

Liaoning Yuhox Intelligent Technology Co., Ltd.

One vendor for software, one for hardware, one for installation, another for maintenance. When the data is wrong, software blames the device, the device vendor blames the wiring, and the installer says it was built to the drawings.

All three sides can be right and not one of the customer's problems is solved. What they want was never "nobody is at fault" but "this thing works". Once responsibility is cut into segments, nobody owns "it works".

ⅡWhat follows

So we do not just produce proposals

Systems that keep working.For that to hold, someone has to own everything from the sensor to the business system with no subcontracting in between. Without that, "integrated" is just the cover of a slide deck.

This is not a slogan, it is a responsibility boundary

One company doing it all does not mean "we can do everything". It meanswhen something goes wrong, you only need one phone number. How we divide the work internally is our business.

ⅢHow we are built

Three kinds of engineers on one project

Since responsibility cannot be split, the company has to be organized around one job from start to finish, not by trade.

SOFTWARE

Software engineers

Make it run reliably

Internet outages, power cuts, devices reporting out of order, the site's network changing three times a day — on customer sites these happen daily; they're not accidents. The people who write the software own stability to the end; it doesn't get pushed onto the field.

DOMAIN

Domain engineers

Make it calculate correctly

Whether a conclusion is right is judged not by the software but by regulations, the site and the consequences. Domain engineers join at the requirements stage, not as a reviewer brought in before delivery.

FIELD

On-site delivery

Make it survive

Installed and running isn't delivery. Commissioning, joint debugging, training and long-term maintenance are done by our own team; for the parts we outsource, nobody speaks for the customer when things break.

For the second kind of engineer, this is the team we have now

Mine ventilation safety

The company has a mine ventilation safety team with an engineering background, able to take on ventilation-system technical work on its own.

Mine ventilation is a safety discipline bound by regulations: the standard of right and wrong does not live in the software but in the regulations, the site and the consequences. Ventilation-related systems built without a ventilation engineer usually end up with a correct interface and a wrong conclusion — the charts look good, but the judgement about the air network does not hold. Our specialists are involved from the requirements stage, rather than someone being asked to review it shortly before delivery.

Services we take on
  • Mine ventilation system technical services and optimization advice
  • Ventilation network calculation, airflow and pressure checks, and result review
  • Support for ventilation resistance surveys and data analysis
  • Roadway pipes and air-duct layout, plus asset registers
  • Ventilation monitoring: product selection, sensor placement, and joint commissioning
  • Requirements gathering and professional acceptance for ventilation IT systems
How software relates to expertise

For the company's ventilation-related software, this team takes part in requirements, algorithm definitions and result checks. Software engineers own stability; ventilation engineers own correctness. The two are signed off by different specialists.

ⅣEvidence

What this setup has produced

Claims only count if delivered. Each item below can be opened and checked. They are not adjectives.

11

in-house product lines

of which 8 are already shipping. All written by us, not rebranded, and not open source under a new name.

Product matrix
1

in-house license and identity system

All products share one account system, and offline activation is supported. Underground and inside intranets there's no internet — a system you buy but can't activate might as well not have been bought.

We use this ourselves

Our own accounts, licensing, releases and operations run on the same system we sell to customers. We would not ask a customer to run something in production that we do not use ourselves.

Code and documentation can be yours

Source code and documentation for custom projects are delivered to the customer; some base components are open source. We keep customers because the system works, not because you cannot leave.

Open-source projects

These were built one by one since founding. For the timeline, seeCompany milestones。

The six engineering principles we follow when building them are written inHome, not repeated here.

ⅤThe name

Yuhox

Yù is the first light of morning; hóng is breadth that holds things. The mark is a gate cut through. Written in Latin as YUHOX, at yuhox.com. Dawn gold is reserved for that cut alone, and is caught again where it meets the structure. On the X of the wordmark only a small piece of it shows, at the upper right.

Yuhox logo
ⅥNext

If you have a site, let's start there

Describe what the site looks like, how things run today, and where it hurts most, and we'll give you a judgment that can be acted on.