Assurance you can trace
Every module proves who it is before it is trusted, and every update proves where it came from.
The trust chain
Issuer key
Held offline by the operator. Signs each module’s attestation before it is deployed.
Attestation
Binds a module’s identity to the capabilities it may offer. Claiming anything else is refused.
Identity key
One per module instance, Ed25519 with ML‑DSA‑65. Signs its beacons and the handshake with each peer.
TLS authority
An ML‑DSA‑65 authority each instance generates at start, valid for 13 days. Peers pin it in the handshake.
Post‑quantum cryptography
Velrix uses hybrid key exchange and signatures: each pairs a proven classical algorithm with a post‑quantum one, so breaking one is not enough. Traffic recorded today is protected against “harvest now, decrypt later”, and long-lived trust against future forgery.
- Key exchange
- X25519 with ML‑KEM‑768 (FIPS 203). Required between modules; offered first at the edge, where current browsers and kubectl agree on it and older clients still connect.
- Signatures
- Ed25519 with ML‑DSA‑65 (FIPS 204), and both must hold: identities, releases, licences, receipts, federation. Certificates between modules are ML‑DSA‑65 alone.
Not yet post‑quantum: the certificate a browser checks, until browsers accept ML‑DSA, and the hardware update key, until PIV hardware supports it.
Signed, image-based OS
An AlmaLinux 10 bootc image, updated by hand or in your maintenance windows. A module update failing its health check rolls back.
Secure Boot
From a verified installer to the installed system on servers with a TPM, and a TPM-sealed seed when diskless.
Hardware update key
Offline updates by USB stick, confirmed with a hardware key held by the installation’s operators.
Tenant isolation
Each tenant runs as its own Unix user with its own SELinux categories; jobs and sandboxed apps in microVMs.
Locked-down modules
Each module runs with a read-only root, every capability dropped, no new privileges, and memory and process limits.
Single sign-on and scoped access
Sign-in through OIDC or SAML, a second step required of operators by default, roles per organisation and scoped API keys.
Other known limits are written down in the architecture rather than left out.
Your data stays where you put it
Velrix is developed by Hypefox AB, a Swedish company. It runs where you choose: on your own servers, in your own environment operated by us, or in Velrix Public Cloud in datacentres in Sweden. Sign-in, records, billing and audit evidence live inside your installation.
- On your own hardware
- On-premises and Managed installations run on your servers, in your environment. Nothing leaves except what your operators choose to connect.
- Outside the US CLOUD Act
- Hypefox AB is Swedish-owned, with no US parent. Velrix Public Cloud runs in datacentres in Sweden, operated by Hypefox AB, outside the US CLOUD Act.
- On-premises, able to run offline
- On-premises installations can take licences and updates as signed files on a USB stick, with no outside service reachable.
- Each module owns its data
- Every module keeps its own store, replicated across its own instances, with a change history kept 48 hours by default.
- Personal identity numbers
- Personnummer from SAML sign-in are dropped by default. When accounts are linked by them, only a keyed hash is kept.
- Support for GDPR and NIS2
- Processing records from the modules that hold personal data, and bookkeeping kept for the seven years Swedish law requires.
The paperwork, built in
The records an organisation needs to keep and the requests it has to answer are part of the platform.
Swedish invoicing
Swedish VAT, OCR references, payment terms and credit, paid by bank transfer or card.
Authority requests
Find who held an IP address when, and answer disclosure requests with evidence.
Retention
Seven years for what accounting requires; the rest of a person’s billing data can be erased.
Observatory and metrics
The live mesh, its traffic, and metrics for every machine and app.
Accessible by default
The web client is built to WCAG 2.2 AA and scanned automatically in light and dark.
Swedish and English
Every screen in both languages, with your own wording where you need it.
See Velrixon your own terms
We walk through the platform and the architecture, and how Velrix would run in your organisation.