How GGNomad Runs
GGNomad is delivered as a fully managed service. You don't deploy or operate it yourself — you consume the web app and a single GraphQL API, with identity, billing, files, conversations, and audit built in. This page explains how the service is operated so partners and operators understand the reliability and security model behind it.
Dedicated-tenant and regional options are confirmed separately for partner deployments.
Environment selection
All GGNomad services default to production infrastructure. To target a
different environment, set BURDENOFF_ENV:
BURDENOFF_ENV | Description |
|---|---|
prod (default) | Live production endpoints and data |
alpha | Pre-production validation environment |
local | Local development stack (localhost:4003 / localhost:4000) |
export BURDENOFF_ENV=alpha
Hosting model
Managed SaaS
- One managed service — nothing to install or self-host
- Continuous, non-disruptive releases
- Automatic updates with no downtime for your workspace
- The web app and the GraphQL API are the surfaces you consume
Multi-tenancy
- Strict per-workspace data isolation by default
- Dedicated tenancy available for partner deployments
- Workspace context is established from your authenticated session, never from a client-supplied argument
- Every action scoped by role and attributable in the audit log
One API surface
- A single GraphQL endpoint covers inventory, bookings, trips, and analytics
- Identity, billing, files, conversations, and audit are part of the same API
- Every operation is authenticated and permission-checked before it runs
Reliability & scalability
Scalability
- Capacity scales automatically with demand
- Caching of read-heavy inventory and discovery paths
- Pagination on every list query to bound result sets
- Event-driven sync instead of polling
Performance
- Field-level GraphQL selection — clients fetch only what they need
- Read paths optimized for discovery and listing detail
- Continuous performance monitoring
Operations
Resilience
- High availability with redundant capacity
- Backups and disaster recovery handled for you
- Security hardening applied uniformly across the service
- Additive, non-breaking API evolution with deprecation notice
Observability
- Health checks and structured operational logging
- End-to-end request tracing for support investigations
- Usage metering and analytics
- Audit and activity timelines
What this means for partners
Because identity, billing, audit, files, and i18n are part of the same service, every GGNomad release ships enterprise-ready. Partners integrate against a stable API and rely on us for the operational backbone — spending their own effort on the travel experience, not infrastructure.
For the service and integration model in more detail, see Managed Service Model and the Developer Guide.