Book a briefing

Inside the bank, and nothing outside it

How it deploys

Inside the bank, and nothing outside it

One statically linked binary on a small virtual machine. No Docker, no JVM, no database server to stand up, no internet. From an empty VM to examiner-ready evidence inside one change window.

Nothing to stand up

SQLite and zstd are compiled in. No dependency to install, no runtime to patch, no schema to migrate.

Nothing to activate

No update channel, no licence server, no telemetry, no call-home. It is whole in a segregated zone and stays whole when the link to it is cut.

Nothing listening

No inbound port is required. The HTTP API is off by default, and bound to loopback when it is on.

Accounted for

Signed packages and raw binaries, a bill of materials with every build, and a reproducible-build recipe your change board can check.

Platforms, sizing, TLS posture, the 300-device benchmark and the replica DR procedure are specified in the technical datasheet.

Get the paper

The technical datasheet

Platforms, packaging, sizing, TLS posture, the 300-device benchmark, the replica DR procedure and the requirements list — the document a platform team reviews.

Sent by email rather than published, because we would rather know who is reading it.

One address, stored to decide who to follow up with. Not sold, not shared, no tracking pixel, no newsletter.