FAQ

Does any of our data or credentials ever leave our tenant?

No. sprig is installed software, not a service. The platform runs in your subscription; we hold no keys, no telemetry endpoint, no phone-home. Corporate data streams gateway → database under the viewer’s own identity (on-behalf-of) for the default db-delegated sources, or under a scoped, audited service identity for gateway-enforced ones (currently Fabric only), and is never stored or cached by sprig - the gateway is a proxy in the request path, not a copy of your data.

What does Ops actually have to do, day to day?

Approve share requests, and expose new data sources when builders need them (both from a Claude conversation). Everything else (budgets, policies, audit) is set up once by the installer. Onboarding a new builder is one step.

What can builders break?

Their own apps. Builders hold no Azure permissions at all; every action goes through the gateway as their own identity, scoped to the apps and data Ops has exposed to them. There is no per-builder Azure resource for a bad app to escape.

Which cloud and which data sources are supported?

Azure today. Ops can expose Azure SQL Database. With Fabric support enabled during installation, Ops can also expose Microsoft Fabric Warehouse tables that have a declared primary key, and Power BI / Fabric semantic models (their tables and measures, read-only, always queried under each viewer’s own identity so the model’s row-level security applies). Fabric lakehouse SQL analytics endpoints can be registered and discovered, but their keyless tables cannot be exposed until sprig supports operator-nominated logical keys. See Supported data sources for the current support and access mode of each source. Internal APIs behind your API Management and per-user LLM budgets are on the roadmap.

What does it cost to run?

The fixed meters include approximately USD 5/month each for the dedicated Basic container registry and platform metadata database. One platform API replica and one gateway replica stay warm; their Container Apps consumption depends on idle and active time and the monthly free grant. The footprint does not grow with builder or app count. The only per-app fixed resource is an app that provisions its own database: an auto-pausing serverless Azure SQL database that bills near-zero while idle. The installer also sets a subscription cost budget that alerts at 80% and 100%. See Costs.

How does licensing work?

Per-tenant licensing during the pilot phase: contact us.