How ORVEXIA is actually built
Not a logo wall. The decisions behind the software — what we use for each layer, what we refuse to add, and the one thing you can verify right now: this page itself.
Six decisions we keep making
They cost more up front and less every month after.
Own the stack
A dependency is a decision someone else gets to change. We add one when it earns its place, and we can explain every line we ship.
A budget, not a hope
Weight and interaction cost are decided before a feature is written. Anything that misses the budget gets rebuilt or cut.
Secure headers by default
Content Security Policy, strict transport security and a locked-down permissions policy ship with the first deploy, not the first audit.
Accessible by construction
Semantic HTML, real focus states, keyboard paths and prefers-reduced-motion respected — decided in the markup, not patched with overlays.
Work offline where it matters
A driver in a dead zone and a clinician on hospital wifi are the same problem. Local-first storage and sync-on-reconnect, not a spinner.
Honest status
Every product carries its real stage. Nothing gets labelled available because it demos well.
What runs where
Chosen per layer, for reasons, and only where it is already in use.
We are not going to list three cloud providers we do not run on yet.
The page you are reading is the sample
Claims about engineering are cheap. Everything below is measurable from your own browser, right now, with developer tools open.