new · rust sdk and boxtra environment clone

seal every
secret

one boxtra id per environment. your app resolves exactly what it may see, sealed to a key only it holds. plaintext lives in one process.

No more .env files to copy, paste, forget or leak. Bring them in once, then run your app through Boxtra.

boxtra run --id bxt_8K2M4Q -- npm start
boxtra · activity
  • resolvebxt_8K2M4Q46 keys
  • import.env67 created
  • clonedev → amaka-local46 keys

illustrative output

1 sealed copy per environment, 1 process that sees plaintext, and 0 values stored in the clear

X25519 + XChaCha20-Poly1305fresh key per resolveappend-only auditrust · go · node · python

~/copies

Every copy is a leak you haven't found yet

Secrets rarely escape through the vault. They escape through the copies around it. We found all three of these moving our own services onto Boxtra.
  • incident 01

    Production keys still sitting in a preview file nobody opens.

    where
    .preview/prod.env
    exposure
    forgotten
  • incident 02

    A container running for two days on config everyone thought was gone.

    where
    one node, no record
    exposure
    unnoticed
  • incident 03

    A .env pasted into a chat so a new teammate could get started.

    where
    message history
    exposure
    permanent

~/how-it-works

From copying secrets to resolving them

A copy is readable by whoever finds it. A resolve is readable by one process, for one request. Pick a secret and follow it through every layer.

what each layer sees · pick a secret

  1. 01

    your process

    plaintext
    DATABASE_URL=postgres://api:s3cr3t-pw@db.internal:5432/shop

    Opens the response with a key it generated for this request, then holds the value in memory.

  2. 02

    on the wire

    sealed
    {
      "key": "DATABASE_URL",
      "version": 3,
      "client_payload": {
        "recipient_key_id": "client_ephemeral",
        "sender_public_key": "izDAbgdPgmQ5p2cetW02yMlB10cGKyhM…",
        "ciphertext": "7yINmKEhdnf3kA1ymaUhCiHtPhjAO7Qp5K7NNGOFjA0SGjrAw7CErBf6…"
      }
    }

    X25519 + XChaCha20-Poly1305, bound to this secret, version and tenant. Readable by one process.

  3. 03

    go control plane

    sealed
    forward(secret_id=6b00…1183f, v3)
      payload: 58 bytes, sealed → can't open

    Authorizes and forwards. It handles the envelope but has no key that opens it.

  4. 04

    mongodb

    ciphertext only
    { key: "DATABASE_URL", version: 3,
      envelope: { key_id: "kek-2026-11", ciphertext: 0x3f9621b3df4b511064c53659fa7ff1af0f04df98a400… } }

    Stores storage-envelope ciphertext and metadata. A full dump reveals no values.

example values · bytes are illustrative · field names match the runtime API

~/platform

Everything that touches a secret, in one sealed place

fig. 2 · the platform
  • Import & clone

    Bring every .env in once, then hand teammates their own re-sealed copy.

    boxtra secret import · environment clone

  • Run & resolve

    Inject at start-up through the CLI, or resolve in-process with an SDK.

    boxtra run · rust · go · node · python

  • Machine identities

    Deployed workloads get credentials scoped to exactly the environments they need.

    bxt_client_ · 15-minute tokens

  • Audit

    Every resolve and change is appended with an integrity hash.

    actor · action · outcome · hash

~/developers

A few lines in any stack

Wrap any process with the CLI, or resolve in-process with an SDK. Every SDK has the same three modes: cli on a laptop, machine when deployed, and agent beside a local agent. A failure in one never falls back to another.

terminal
# Bring an existing .env in once. Values are sealed before they leave.
boxtra secret import .env \
  --project shop --app api --env development

# Give a teammate their own copy, re-sealed for them.
boxtra environment clone amaka-local \
  --project shop --app api --from development

# Run anything with the environment injected. Nothing is written to disk.
boxtra run --id bxt_8K2M4Q -- npm start

~/limits

The numbers, as shipped

Read straight from the control plane, compute and CLI. If a limit changes, this table changes with it.
limits.toml
LimitCurrent
Secrets returned per resolve256
Sealed value size1 MiB per value
Key name length256 characters
Secrets per bulk import5,000 per request, atomic
.env file accepted by import1 MiB
Resolve response read by SDKs2 MiB
Machine access token lifetime15 minutes
Ingest key rotation (production)every hour, 5-minute overlap
Invitation lifetime7 days

import your .env
then delete it

Create an environment, bring in what you have, and run your app through Boxtra. Rolling back is a re-import away.