Deployment
SemanticFed is delivered as a managed, multi-tenant SaaS. You don't operate any infrastructure — you register sources, model metrics, and run governed federated queries from your workspace.
How SemanticFed runs
- Fully managed — the service, the web app, and the API are operated for you; there is nothing to install, patch, or scale
- Multi-tenant with hard isolation — every connector, source, model, query, and policy belongs to a workspace, and all access is workspace-scoped
- Encrypted in transit and at rest — including the credential references you register for your sources, which are stored in encrypted, environment-isolated secret storage and never returned by the API
- Your data stays put — SemanticFed holds model and governance metadata; your data is queried in place in your own systems
- Resilient by default — health-checked, horizontally scaled, and updated with rolling releases
- Reviewed releases — every change is validated in a pre-production environment and promoted to production only after an explicit approval
Environments
| Environment | Purpose | Gateways |
|---|---|---|
| Production | The live service | graphqlworkspaces.burdenoff.com, graphql.burdenoff.com |
| Alpha (pre-production) | Validation of every release before it reaches customers | alphagraphqlworkspaces.burdenoff.com, alphagraphql.burdenoff.com |
| Local | Development on your machine | localhost:4003, localhost:4000 |
Environment selection
All SemanticFed clients default to production. Switch to alpha or local via BURDENOFF_ENV. See Environment Selection for per-client instructions.
Environments are fully isolated from one another, with separate data stores and separate secrets.
Deployment options (roadmap)
A managed multi-tenant SaaS is the launch offering. Private-cloud and self-host deployment for regulated industries — keeping data inside residency and compliance boundaries — is on the roadmap.
See Cloud deployment for more on the managed cloud model.