Möbius

Security

Deployment models, credential handling, and the audit trail — what Möbius promises about your data.

Deployment models

Möbius runs in exactly three deployment models. There are no sub-variants — a deployment is one of these three, and every governance behavior is identical across them.

ModelWhere it runsWhat that means for you
CloudMöbius's own infrastructure, multi-tenantFastest to start. Environments are logical (one instance, tagged environments).
ConnectYou host it, on your own infrastructure — a single self-contained container stack you run on any infrastructure of your choosing: your own cloud account, or a rack with no internetThe full product, no feature ceiling. Data and workloads stay on infrastructure you control.
EnclaveSame self-hosted stack as Connect, run with zero required outbound connectivityFor air-gapped or fully sovereign environments. Möbius never phones home.

Connect and Enclave are the same underlying artifact — a set of versioned container images you run yourself — differing in commercial packaging and network posture, not in code. Every release ships as one versioned image set: connected deployments pull it from Möbius's registry, air-gapped deployments receive the identical versions as a signed offline bundle. There is no long-term-support fork and no appliance-only branch — everyone runs the same product on their own schedule.

Air-gap is your control; air-gap-capable is our product. Möbius doesn't grant or enforce your network isolation — that's a decision you make on your own infrastructure. What Möbius commits to is that the product stays fully operable with the cable cut: every external dependency (object storage, embeddings, secrets, email) has either an in-box substitute or degrades honestly and visibly, never silently. An Enclave deployment that chooses to allow some outbound traffic — to reach a warehouse, or send outbound webhooks — remains fully supported; Enclave is a capability, not a rule enforced on you from outside.

What's inside the box

Every Connect/Enclave deployment ships as built container images — your Next.js application, its data-plane gateways, its background workers, and the packaged database migrations. It never ships application source, source maps, or .ts/.tsx files: the build produces a minified, standalone production bundle, and a build-time check fails the image outright if any source file is found inside it. You run compiled software, not a copy of the codebase.

TLS

Every Connect/Enclave deployment requires TLS in front of it — including a fully internal, network-isolated Enclave. That surprises people, so it's worth saying why: without a certificate your browser silently drops login cookies over plain HTTP, and several internal configuration checks refuse a non-loopback plain-HTTP address outright rather than let it run insecurely. An internal-only deployment doesn't need a certificate from a public authority — a certificate issued by your own internal certificate authority is sufficient, and no outbound connectivity is required to obtain one.

Credential handling — what you can count on

  • Your credentials are stored encrypted, never in the clear. Warehouse connector credentials, cloud identity bindings, and API keys you provide are encrypted at rest under your deployment's key.
  • Möbius never receives more than it needs to do the job. Where a delegated-identity model is available (for example, cloud object storage access), Möbius asks for a scoped role binding rather than a standing secret wherever the provider supports it.
  • A credential is never echoed back to you, or to anyone, once stored. Every credential-bearing configuration screen shows only whether a credential is present, never its value.
  • On Connect and Enclave, Möbius never accepts a pasted credential at all. A raw secret is refused outright — you point Möbius at a reference into your own secrets manager instead, so the raw value never reaches Möbius. On Cloud, you choose: paste it and Möbius vaults it encrypted, or supply your own reference.
  • Möbius verifies the identity of every warehouse it connects to, not just the encryption of the channel. Warehouse connections default to full certificate verification (matching hostname, trusted authority — including an internal CA you provide) rather than merely encrypting the wire. Editing a connector's connection target requires re-verifying it before it can be used again; there is no configuration that skips this.
  • Every credential edit is audited, including a downgrade of a connector's verification strictness — visible in your workspace's governance audit trail, never a silent change.

Audit

Every governance-relevant action in your workspace — a certification, a row-gate decision, a connector change, a token mint, a workspace configuration change — writes to a single audit channel, described in full in the audit trail concept page. There is no second, quieter log: an action that isn't in the audit trail didn't happen.

Certification is the access gate

Data is only reachable through the certified API doors (REST, GraphQL, MCP) once it has passed certification. This isn't a configurable setting — there is no mode that serves uncertified data through those doors. See Certification and gates for what certification checks.

On this page