Hosting and Data Residency

FluidGrids is a managed service. Burdenoff runs, patches, and scales the infrastructure; there is nothing for you to provision, and there is no self-hosted edition.

If some app nodes must run on your own hardware — to reach systems inside your network, or so their requests come from your own IP address — install a runner on one of your machines and set those nodes to Run on it. Private destinations are opened on that machine (fluidgrids-runner network allow). Those nodes then run on your machine. Their input, output, the workflow itself, its run history and its logs still pass through and are stored in FluidGrids.

Where your data lives

Region	India — AWS Asia Pacific (Mumbai), ap-south-1
Workflow definitions, run history, and logs	Stored in region
Credentials	Encrypted at rest, isolated per workspace, stored in region
Backups	Retained in region, encrypted, point-in-time recoverable

Data does not leave the region except where a workflow you build sends it somewhere — an HTTP node calling a third-party API, or a connector writing to a system you own. Those destinations are yours to choose, and yours to govern.

Isolation between workspaces

Every workflow, credential, and run belongs to exactly one workspace. Queries are scoped to the calling workspace, credentials are encrypted with per-workspace isolation, and a run can only read the credentials of the workspace that owns the workflow. Nothing is shared implicitly across workspaces or organizations.

Environments

FluidGrids exposes a production environment for customer use:

Environment	App
Production	https://app.fluidgrids.ai

Alpha (https://alphaapp.fluidgrids.ai) is a pre-release environment used by Burdenoff for validation. It is gated by Cloudflare Access, is not open to customers, and carries no availability or data-retention guarantee.

Availability

Live status and incident history: status.burdenoff.com.

Next steps

• Security — authentication, RBAC, and data protection
• Monitoring and Health — health checks and status