Skip to content
Ambry

Status

What exists, in its own words

A roadmap item dressed up as a feature is the quickest way to lose a technical reader. This page separates the three, and the homepage's counts come from the same lists.

Built and running

Twelve components in use today.

  • The server

    C++ with libsodium and Postgres. Loopback only, behind nginx with TLS.

  • The ambry CLI

    A thin REST client. People log in on the terminal for every command; nothing that can reveal is ever stored.

  • The MCP server

    What agents use. Its tools and the paths it may reach are an allowlist, pinned by a test, with no reveal on either.

  • The dashboard

    Namespaces, versions, requests, tokens and grants, the audit viewer and backup status. Values are masked until clicked, and the session lives only in page memory.

  • The Ansible lookup

    Deploy playbooks read a secret by name with a runner token, and it refuses to hand a value to a run that would print it.

  • The vault importer

    Moves an existing Ansible Vault in. It is run by a person and prints names and fingerprints only.

  • Build-time secrets

    A build fetches what it needs at the moment it starts, rather than reading a file a deploy wrote to the machine earlier. Every Android signing key in the portfolio is fetched this way now, and release builds are signed with them.

  • Backup origin authentication

    Each backup is stamped under the key only the server holds, and a restore refuses a forged one before anything is restored. Which backup is the newest is still settled by a record kept off the host.

  • The KEK recovery kit

    The master key, sealed under a memorized passphrase and printed on paper, with a checksum on every line. It has been made, and typed back in to prove it opens to the key the server runs.

  • Push notification of requests

    A registered phone is told how many requests are waiting, and nothing about what they ask. The sender is a separate process that holds no key and reads one small file the service writes.

  • Phone approval for production

    Revealing a production value, copying one out, or letting a deploy runner reach one waits for a fingerprint on an enrolled phone. The phone signs each approval with a key of its own; a password alone cannot enrol one, and the first phone is enrolled on the host itself.

  • Nightly sealed backups

    Every night a backup is proved by a restore before it is sealed, then copied off the host. Seven nights ran green in a row, and a restore drill has passed.

Built, not yet running

One pieces whose code exists and whose last step has not happened.

  • The mobile app

    Scaffolded: requests to approve or deny, a masked vault view and an audit feed, with the session held in memory only. A signed release build runs on a phone on the local network and is told when a request is waiting; how a phone reaches the service from outside that network is still to come.

Not built

Three things the design names and nobody has made yet.

  • Biometric sign-in

    The phone keeping its session behind a fingerprint, so it need not ask for the password each time. Today the session lives in memory only.

  • Finer reveal permissions

    Outside production, a logged-in person can reveal. Reveal grants per namespace, for when a second person needs access, come later.

  • KEK rotation

    Re-wrapping every value key under a new KEK, with a hand-over the audit chain can follow.

How the built parts fit together