What is sprig?
Your people already vibe-code apps in Claude: dashboards, calculators, internal tools. The building works. What doesn’t work is everything after: the app can’t reach corporate data, it gets passed around as an HTML file over email or a share, there’s no authentication, no audit trail, and nobody knows what’s running where.
sprig is a deploy target for vibe-coded apps, installed inside your own Azure tenant. It gives every builder a governed sandbox and gives Claude a set of skills so that one sentence — “share this solution” — turns an artifact into a running, Entra-secured internal app.
What you get
Section titled “What you get”- A governed publish path. Apps land as Azure Static Web Apps in a per-builder resource group, created by the platform — builders need zero Azure permissions or tooling.
- Locked down by default. Every published app gets its own Entra app registration with assignment required: only the owner can open it until Ops approves a share request.
- Live corporate data, no copies. Apps read data (Microsoft Fabric first) at view time with the viewer’s identity. Sharing an app never shares data access — viewers see exactly what their own permissions allow.
- Ops stays in control without running a ticket queue. Install once, onboard builders with one command, approve share requests. Budgets, policies, provenance tags and an audit trail are part of the install.
What sprig is not
Section titled “What sprig is not”- Not a hosting service. Nothing runs on our infrastructure. sprig is software you install into your subscription; we never hold credentials to your tenant.
- Not a code generator. Claude builds the apps. sprig is the boundary between “Claude made a thing” and “the company runs a thing”.
- Not a data platform. sprig never stores or proxies your corporate data. Data flows directly from Fabric to the viewer’s browser under the viewer’s own token.
- Not a general PaaS. The sandbox is deliberately narrow: static web apps, locked resource types, per-builder isolation. That narrowness is what keeps Ops involvement minimal.
Where it runs
Section titled “Where it runs”Azure today (Static Web Apps, Entra ID, Microsoft Fabric). The platform is self-contained in one subscription: a platform resource group plus one resource group per builder.
Next: How it works · Try it locally