FAQ
General
Q: Can I self-host FluidGrids? A: No. FluidGrids is a managed SaaS product. Burdenoff runs and scales the infrastructure; there is no self-hosted edition.
Q: Where is my data stored? A: In India. See Hosting and Data Residency.
Q: How are credentials protected? A: They are encrypted at rest, scoped to a single workspace, and never returned in plaintext through the API or UI once saved. See Security.
Operations
Q: How do I know if there is an incident? A: status.burdenoff.com carries live status and incident history. Subscribe there to be notified.
Q: Is there a maintenance window? A: No. FluidGrids is continuously delivered — changes ship after passing automated checks, with no downtime window and nothing required from you.
Q: How do I get alerted when a workflow fails? A: Add a failure branch to the workflow that notifies you, or poll the GraphQL API for failed runs. See Monitoring and Health.
Q: Where do I view run logs? A: In the run detail view, per node. Use the GraphQL API or the SDKs for programmatic access and for exporting beyond your plan's retention period.
Connecting
Q: What are the API endpoints? A:
| Client | Endpoint |
|---|---|
| GraphQL API | https://graphqlworkspaces.burdenoff.com/workspaces/graphql |
| App | https://app.fluidgrids.ai |
Q: How do I point the CLI or SDKs at FluidGrids?
A: BURDENOFF_ENV is read only by the browser and VS Code extensions, not by
the CLI or SDKs. For the CLI, set FLUIDGRIDS_API_URL (or pass -u/--url, or
run fluidgrids config set url <endpoint>). For the Node and Python SDKs, set
FLUIDGRIDS_ENDPOINT (or pass the baseUrl/endpoint argument). All clients
default to production.
Q: How do I authenticate a script or CI job?
A: With a workspace-scoped API key, supplied as FLUIDGRIDS_API_KEY. Create and
rotate keys under Developer Portal › API Keys in the app; revocation is immediate.