Licensing
Licensed governance for real deployment scope
Möbius is sold as an annual license, not a self-serve seat-based SaaS product. Choose the right license and deployment model for your governance scope, security posture, and operating model.
This page explains how Möbius is priced rather than quoting a number. The number is a function of the posture you choose — where the instance runs, how separated it has to be, and what we operate on your behalf — so it is settled in a conversation, not on a price list.
Möbius is in early access. Licensing opens with the early-access programme, so the request form below is the way in today.
The model
Full product everywhere. Posture is what moves the price.
One full product. Every deployment runs all of it. Capabilities differ only where the deployment physically forces the difference — never by commercial gating. There is no entry tier that is a deliberately reduced version of the product, and nothing to unlock by paying more. Price tracks deployment posture and risk, not a feature count.
Posture
Möbius-operated, customer-hosted, or sovereign. This is the primary price axis — it sets the risk transfer, the hosting model, and the support commitment that comes with each.
Separation
How much of the estate is governed and how separated it has to be: governed domains, certified data products, policy-gated interfaces, environments, and the consumption running across them.
Services
Implementation and onboarding, deployment engineering, certification rule development, and governance operating-model advisory — scoped and contracted separately from the license.
Deployment
Run Möbius in the model your environment requires
Möbius can be operated by Möbius, deployed into your environment with managed support, or run as an isolated self-controlled instance. The license rides on the deployment posture — Standard on Cloud, Enterprise on Connect or Enclave — so the commercial model stays simple: choose the operating posture your environment requires and the license follows. It is the same full product on every deployment; the posture, not a feature ceiling, is what changes.
The ladder runs Cloud, then Connect, then Enclave — least to most. Because the product is identical on all three, price never follows features. It follows the posture premium, the delivery and service intensity that posture demands, and the risk being transferred off your side of the boundary.
The line between the last two is simple. If Möbius can still reach in to help, it is Connect. If Möbius is blind, it is Enclave — wherever it runs. Cutting the cord is choosing Enclave. An Enterprise customer can run both at once: Connect for most teams, Enclave for a regulated division.
Licenses
Two licenses. The deployment decides which one.
Möbius is licensed by governance scope and deployment posture, not by UI seats. Start with the right operating model for your environment, then expand by domains, interfaces, and certified data products as adoption grows.
Standard runs on Möbius Cloud — production governance with Möbius operating the instance. Enterprise runs on Connect (your environment, optional managed support) or Enclave (fully sovereign). Standard does not run on Connect or Enclave. Enterprise does not run on Cloud. Wanting the Enterprise customer-hosted, sovereign posture means moving deployments — that is the upgrade path by design, and it is a posture change, not a feature unlock.
What actually differs
Three differences, and every one of them is physical
These are the only places a deployment changes what is possible — and each one is a consequence of where Möbius is running, not a commercial decision about what to withhold.
- Private models on your own compute
- Running a model on your own hardware needs your compute and your network, which vendor-operated infrastructure does not have. Available on Connect and Enclave. Bringing your own model provider account and key is a different thing, and that works on Cloud too.
- Sovereignty and zero vendor visibility
- Sovereignty is the absence of the vendor, so it cannot exist on vendor-operated infrastructure. Connect keeps a deliberate, narrow license touchpoint; Enclave removes vendor visibility entirely, with air gap optional.
- Where warehouse credentials and the data path live
- Warehouse connectivity itself runs on every deployment. What changes is posture: on Cloud, Möbius holds the warehouse credentials and the read and write path traverses the public internet — a disclosed risk decision you make, never a capability we withhold. On Connect and Enclave, both stay inside your environment.
- Everything else
- The governance engine, the certification and recertification workflow, policy gates, the audit record, the REST, MCP and GraphQL gateways, webhooks and notifications, semantic enrichment, AI guardrails and mobile governance are identical on all three.
Scope
What the license actually measures
These are commercial scale dials — how big the contract is — applied to the same whole product. They are not capability gates. On Cloud they are also a genuine multi-tenant fairness limit: Standard runs on shared infrastructure Möbius operates, so throughput has to be balanced across everyone on it. Enterprise is uncapped, because Connect and Enclave are single-tenant and you own the capacity.
- Deployment posture
- Cloud, customer-hosted, or sovereign. The primary axis — everything else is sized inside it.
- Governed domains
- Each domain — customer data, finance, product — is a distinct governance context, and the meaningful unit of scope.
- Certified data products
- The core output of Möbius: how much of your data has been declared safe to act on.
- Policy-gated interfaces
- Every attachment point where certified data crosses the boundary to a consumer — REST endpoints, webhook channels, MCP tools, AI access points, mobile approval endpoints. The budget is fungible across all of them. Warehouse connectors are entry motion and never count.
- Environments
- Each environment — production, staging, a region — carries its own operational scope and deployment complexity.
- Consumption
- Vector and metadata processing volume, agent activity, and gateway call volume above the licensed threshold — metered on top of the base license, and optional.
How it is billed
Five separate lines. The license never bundles the rest.
Each line has its own contract and its own renewal. You can renew the license and separately renew — or decline — an audit engagement. That separation is what keeps the assurance work independent of the software sale, and what lets a consulting partner attach their own services without mixing into the Möbius license line.
What Möbius is not priced like
“It is SaaS, so we are billed monthly per user.”
No. Annual license, not per user. Seat pricing punishes exactly the adoption Möbius is meant to accelerate, and none of the value maps to headcount.
“The cheaper option is a crippled version of the product.”
No. The product is whole on every deployment. Price tracks deployment posture and risk, never withheld features.
“There is a free tier to try it on.”
No. Evaluation is a 12-month commercial engagement on Standard, paid from day one, under NDA.
“More users means more revenue for Möbius.”
No. Revenue tracks deployment posture and governance scope. Consumer identity counts are an advisory signal in your own governance health view, never an enforced limit.
“Möbius has to see our data to validate the license.”
No. On Connect and Enclave the license is validated locally against a signed key, and the renewal signal carries an instance heartbeat, a license identifier, a version and a nonce — no customer data, no workspace names, no user information.
“We need cloud-native infrastructure to adopt it.”
No. Enclave runs in your own cloud account or on your own premises, fully air-gapped if that is the requirement.
Getting started
There is no signup form, and that is deliberate
Every Möbius instance is provisioned by an administrator against a signed agreement — there is no trial, no free tier, and no self-serve path into a governance instance. An evaluation is a 12-month commercial engagement on Standard, at negotiated pricing, scoped to one domain and under NDA. Every Möbius customer pays from day one.
Intro call
We work out the governance problem you are actually solving and the deployment constraints your environment imposes.
Agreement
A 12-month engagement on Standard at a negotiated rate, scoped to one domain, under NDA.
Deployment
Möbius-assisted setup on Cloud, with your team defining the governance scope, the policies, and the interfaces that are allowed to exist.
Commercial review
At month nine: renew at the standard rate, move to Enterprise on Connect or Enclave if the posture now requires it, or end the engagement.
If the customer-hosted posture is a hard requirement from the start — credentials and the data path inside your perimeter, private models on your own compute, or sovereign operation — say so on the first call and the conversation starts at Enterprise instead.
Pricing is a conversation about posture, not a table of numbers. Tell us where the instance has to run and who is allowed to see it, and the rest of the commercial model follows from there.