Software
Native applications and business systems built for real work. From AI-assisted development workflows to fully offline ERP software, our products are designed around the people who use them.
Explore our software
An independent software studio building native applications, business systems, and the technology beneath them. We build our own foundations because the software we ship should be ours to understand, improve, and stand behind.
Hyperoche is an independent software studio. We build applications for people who expect their software to be capable, dependable, and worth owning.
That means we do more than build products on top of existing platforms. We build parts of the technology underneath them as well — from rendering and UI systems to platform infrastructure and shared application components.
This is not an end in itself. It is a way of working.
When we control more of the foundation, we can understand more of the system, make better engineering decisions, and build products without having to design around somebody else's priorities.
Our products begin as software we need ourselves.
The development tools we use every day were built in-house. Phengos grew from that same environment: an AI-assisted workflow designed around actual development rather than a hypothetical user.
Our business software follows the same principle. The Restaurant ERP is being built as part of a broader ERP platform designed to work offline and remain under the customer's control.
We build software by using it, finding what is wrong with it, and fixing it before asking anyone else to depend on it.
Phengos 1.3.1 is Hyperoche's first public software release.
The Community edition is available free of charge with no account required. Phengos Pro adds capabilities including unlimited files per run, persistent history, multi-turn conversations, and run integrity verification through a one-time perpetual licence.
We are deliberate about what we ship. Features that have been thoroughly exercised are treated differently from features that are experimental or incomplete. Where something has limitations, we document them rather than hiding them behind marketing language.
See the provider support tiers for an example of how we document those boundaries.
Different products may solve completely different problems. The engineering principles behind them do not need to.
Native where it makes sense.
Offline where it should be.
Private by architecture.
Built to be understood.
Built to be owned.
That's Hyperoche.