Managed Service Model
GGNomad is delivered as a managed cloud service. You consume the web app and the GraphQL API — there is no infrastructure for you to provision, scale, patch, or back up. This page describes what that means in practice: how releases reach you, what environments are available, and the reliability and security commitments behind the service.
Environment selection
GGNomad defaults to production endpoints. Set BURDENOFF_ENV to target a
different environment:
BURDENOFF_ENV | Workspace gateway | Global gateway | Web app |
|---|---|---|---|
prod (default) | https://graphqlworkspaces.burdenoff.com/workspaces/graphql | https://graphql.burdenoff.com/global/graphql | https://app.ggnomad.com |
alpha | https://alphagraphqlworkspaces.burdenoff.com/workspaces/graphql | https://alphagraphql.burdenoff.com/global/graphql | https://alphaapp.ggnomad.com |
local | http://localhost:4003/workspaces/graphql | http://localhost:4000/global/graphql | http://localhost:3000 |
Nothing to run
- No servers, containers, or databases for you to operate
- Capacity scales with demand — you are not sizing anything
- Upgrades, patching, and backups are handled for you
- The web app and the GraphQL API are the surfaces you consume
Environments
GGNomad is offered in separate, isolated environments so you can build and test before you go live:
- A development/test environment for integration work against test data
- A production environment for live inventory and real bookings
- Credentials, data, and configuration are isolated per environment — a development credential never reaches production data
- Partners can request a dedicated tenant
Releases
Releases are continuous and non-disruptive:
- A change is validated in the pre-production environment
- After approval, the same validated build is promoted to production
- Updates roll out without downtime for your workspace
API changes are additive and non-breaking by default. Fields being retired are marked deprecated well ahead of removal, with migration guidance, so integrations keep working across releases.
Reliability
Availability
- Redundant capacity behind the service
- Managed backups and disaster recovery
- Rolling, no-downtime updates
Operations
- Latency and error-rate monitoring with alerting
- Structured operational logs with retention
- End-to-end request tracing for support investigations
Security
In transit and at rest
- TLS on every connection to the API and web app
- Encryption at rest for stored data
- Secrets are held in managed, per-environment secret storage and are never shipped in client builds
Access
- Every operation is authenticated and permission-checked before it runs
- Workspace-scoped data isolation — one workspace never sees another's data
- Audit fields recorded on every write
What you do
As a customer or partner, you don't operate any of this. You:
- Sign in to the web app, or
- Issue a credential and call the GraphQL API
For integration patterns, see the Developer Guide and API Reference.