Technology

Hyperoche develops and maintains the core technology behind its software. This is a deliberate and costly choice, but it allows us to shape the underlying tools around each product rather than shape the product around the limitations of third-party frameworks.

Our own engine

At the centre of our software is a real-time Vulkan engine, together with the user interface framework built on top of it. Both are developed and maintained in-house. They are foundations for our products rather than products in their own right.

Every application we ship uses the same rendering path. There is no Electron, embedded browser, Node.js runtime, or bundled web dependency tree. Our applications are written in native modern C++, from the platform layer upwards.

This architecture helps our applications start quickly and remain responsive under load. It also means they require a working Vulkan driver. There is no software fallback because we do not maintain a second rendering path.

Bring your own key

The AI features in our software use your own provider account. API keys are kept in your operating system's credential store, and requests are sent directly to the provider you select. Hyperoche does not process those requests in between, and your working files remain on your disk.

We do not operate an inference service, resell API access, or use a credit system. You pay your chosen provider directly at its standard rates. Alternatively, you can use a supported local model server and run the processing on your own computer.

Why we build this way

Owning the stack gives us direct control over what data our software creates, where that data is stored, and when information is sent elsewhere. It also means that core privacy and maintenance decisions do not depend on a third-party framework continuing to behave as expected.

There are faster ways to build software, including assembling products from readily available components. We have chosen a slower path where it gives us meaningful control over reliability, privacy, performance, and long-term maintenance.

The result is technology built with a clear purpose: understandable, maintainable, and shaped around the needs of the software and the people who use it.