Cost profile

Platform footprint (fixed, one bill regardless of headcount)

At pilot scale, the fixed meters are approximately USD 5 per month each for the dedicated Azure Container Registry and platform metadata database, plus the warm platform and gateway replicas described below. Variable request, active compute, storage, telemetry, and any per-app database usage are additional.

The base footprint does not grow with the number of builders or published apps. Azure Container Apps uses consumption pricing with a monthly free grant. The gateway and platform API each keep one minimum replica for predictable access, so the exact charge depends on active and idle seconds, memory, requests, region, and the rest of the subscription’s use of the free grant.

Enabling Fabric Warehouse or lakehouse sources adds consumption only while a source’s schema is being read, which happens when an operator registers or refreshes a source. That work reserves 0.25 vCPU and 0.5 GiB while it runs and nothing at all in between, so there is no idle charge to estimate. At the same West Europe retail meters quoted below (USD 0.000034 per active vCPU-second and USD 0.000004 per active GiB-second, July 19, 2026), 100 schema reads a month at 6 seconds each is 10 minutes of active time: 150 vCPU-seconds (USD 0.0051) plus 300 GiB-seconds (USD 0.0012), or approximately USD 0.0063 per month before the monthly free grant. The charge is linear in total active seconds, so doubling either the number of reads or their duration is about USD 0.013 and doubling both is about USD 0.025. A figure anywhere near a dollar would mean schema reads are happening far more often than registering and refreshing sources can account for.

The platform VNet and its private address space have no hourly charge. VNet integration for the Container Apps environment adds Azure-managed networking resources, including public IP and load-balancer meters plus processed-data charges. Later VNet peering adds per-GB transfer charges; Sprig does not create peering, private endpoints, NAT Gateway, or private DNS during the base install.

The platform API replica reserves 0.75 vCPU and 1.5 GiB across the application and telemetry sidecar. Microsoft’s public West Europe retail meters on July 19, 2026 were USD 0.000004 per idle vCPU-second, USD 0.000004 per idle GiB-second, USD 0.000034 per active vCPU-second, and USD 0.000004 per active GiB-second. Before the monthly free grant, that is approximately USD 23.64 for a 30.4-day all-idle month or USD 82.74 if continuously active. Normal pilot usage falls between those bounds before the free grant is applied.

The dedicated Sprig-owned ACR adds a fixed registry charge. The installer creates or reuses one deterministic Basic registry for the subscription and prefix, with no registry input from the operator. A Basic registry is commonly about USD 5 per month and includes 10 GiB of storage, with additional storage and network transfer billed separately. Full uninstall deletes the registry with the platform resource group. Check the Azure Container Registry pricing page and Azure Container Apps pricing page for your agreement and region before installation.

The platform metadata database reuses Sprig’s existing logical SQL server and managed identity. It is one 5-DTU Basic database with 2 GiB maximum storage. Microsoft’s public retail meter for West Europe was USD 0.161 per day on July 19, 2026, or approximately USD 4.90 for a 30.4-day month. The platform applies forward-only schema migrations before it becomes ready; a failed migration leaves the new revision unavailable instead of serving an unknown schema. Demo reset deletes this database but retains the free logical server, and the next install recreates an empty migrated database.

Per-app costs

Publishing, republishing, and rolling back an app stores another small bundle and does not create a new runtime service. An app that only reads an Ops-exposed source adds request and data-transfer usage, not a separate fixed Azure resource.

Archive publishing uses existing platform storage for bundles and one dedicated Standard LRS storage account for retained source. The source account is consumption-priced, with no fixed account fee. At pilot scale, 10 GiB of retained source (100 apps, 20 versions each, and 5 MiB per version) is approximately USD 0.20 per month, plus ordinary storage transactions and data transfer. Lifecycle rules remove abandoned uploads after one day. Full uninstall removes the account with the platform resource group. Required Azure RBAC assignments have no fixed or per-assignment charge.

The fixed sprig-users and sprig-operators Entra security groups have no per-group charge. Group-based app-role assignment uses the Entra ID P1 or P2 license already listed in the installation requirements.

An app that provisions its own database (a tracker, a signup list; see Publishing & sharing) adds a serverless Azure SQL cost that auto-pauses to near-zero when the app is idle and only bills while it’s actively serving queries.

Data-side costs

Azure SQL sources and Power BI / Fabric semantic models are read with the caller’s own identity (on-behalf-of), and Fabric Warehouse / lakehouse sources with sprig’s service identity; either way there’s no separate sprig data-egress cost, and you pay whatever your source already costs.

Guardrails

The installer creates a subscription cost budget that alerts at 80% and 100% of its limit: a safety net set above the expected pilot footprint, to catch a runaway early. Azure budgets notify; they do not stop spend. Enforcement automation is a roadmap item.