One core, from the operating system up
Our own operating system, our own language for business logic, our own protocol — written from scratch in Rust, with no third-party libraries in the working code.
Eight ideas the platform is built on
Each one has its own article in the blog.
SakinaOS — our own operating system
Written from scratch in Rust, not a line of C. One application per machine, with no processes, system calls or general-purpose scheduler between it and the hardware. Runs on ARM64 and x86-64, on dedicated servers and in public clouds.
In the blog: SakinaOS: why we wrote our own operating systemCambium — one language for business logic
Typed and deterministic: data and permissions, formulas, queries, decision tables, state machines and rules. Programs always finish, and money is exact 128-bit arithmetic where overflow is an error, never a silent rounding.
In the blog: Cambium: one language for business logicATL — our typed protocol
One schema gives a compact binary format, symmetric request-response and ready clients for Rust, TypeScript, Dart, Go and Python. Every changing request is applied exactly once.
In the blog: ATL: one typed protocol for the whole platformMulti-axis access control
Action, record and field — plus the trust level of the session. The answer is allow, deny, or «allowed after a stronger factor».
In the blog: A permission is not enoughDeterminism
No wall clock, randomness or floating point in business logic. State is a pure function of an append-only journal, so restoring from the journal gives exactly the state that running produced.
In the blog: Same inputs, same outputsA network as a trust domain
Its own root key, weighted k-of-n signatures for critical decisions, revocation, and an append-only transparency log with inclusion proofs.
In the blog: Two networks: your partners and your nodesData residency with proof
Policies by country (ISO 3166-1) and region, data class and key-storage class. A placement is accepted only with a proof checked against the policy; a refusal names its reason.
In the blog: Choose where your data lives — and prove itA symbolic reasoning engine
Runs on ordinary CPUs in exact arithmetic, with no neural networks or language models. It plans towards a goal, explains each decision with the facts behind it, and rehearses a rule change on history before applying it.
In the blog: A reasoning engine that shows its workWhat every business feature stands on
The same components serve a partner network, a warehouse and an accounting department.
Double-entry ledger for any resource
Money, points, stock. Books balance to zero per asset after every operation; holds, two-phase settlement, idempotent operations and reversals.
Exact arithmetic
No floating point anywhere in business logic. Minimal units, decimal fixed point and exact fractions; allocation always sums to the total.
Bitemporal history
Each record keeps when a fact was true and when it was recorded. Query any past moment «as of»; corrections are new records.
Tamper-evident audit
Every action and every refusal is recorded as who, what, when, why and result, in a hash chain. Editing, deleting or truncating an entry is detected.
Own cryptography
TLS 1.3 with hybrid X25519 + ML-KEM-768 key exchange by default, AES-256-GCM, Ed25519 + ML-DSA-65 hybrid signatures — implemented in-house, no foreign library.
Standard protocols built in
HTTP/1.1, HTTP/2, WebSocket, TLS 1.3, QUIC with HTTP/3, and the PostgreSQL, Redis and Kafka wire protocols.
A sealed, self-updating appliance
A node is one server running SakinaOS. Its role — business platform, compute, storage or a protocol endpoint — is set by configuration.
Our cloud or your own nodesSigned and reproducible
Every image carries a signed manifest checked at boot. Building twice from the same sources gives a byte-identical image.
A/B updates with automatic rollback
A new version boots on probation; if it is not confirmed, hangs or crashes, the node returns to the previous version.
Management without SSH
Only over ATL inside TLS 1.3 with mutual key verification. There is no shell. Separate certificate roles: monitor only, unlock only.
Encrypted disks, key in memory
The disk key arrives over the management channel at boot and is never written to disk. Disk health is watched and suspect areas are quarantined automatically.
Own drivers
Written from official specifications: NVMe, SATA, Intel 10 GbE and standard virtual devices. ARM64 and x86-64.
About 5 MB
The node with its operating system takes about 5 MB. Every limit is a parameter and every refusal has a name.
Tested, not promised
We publish only what we have measured, with the date and the conditions.
5 hard power cuts, nothing lost
Power was cut 5 times during writes on a dedicated AMD EPYC server with NVMe (October 2026): all 248 acknowledged writes were intact, none lost, none corrupted.
6 hours, 17 updates, 35 reboots
A 6-hour run under load in an x86-64 virtual machine with 4 vCPU (October 2026): 17 update cycles — 8 confirmed, 9 rolled back automatically — 35 reboots and about 407,000 HTTP operations. Every confirmed piece of data was intact and memory use stayed flat.
About 5 MB per node
A node with its own operating system takes about 5 MB. Everything else on the server is left for your work.
The 9 rollbacks in the 6-hour run were deliberate: those updates were left unconfirmed to prove that rollback works on its own.
See it on your own business
Book a demo: we show the platform on your processes and agree where your data will live — in our cloud or on your own nodes.