Evaluating sprig?
Start with What is sprig, then run the local evaluation on a laptop — the full platform, no Azure subscription required.
Vibe-code inside your boundary.
Your people already build apps with Claude. sprig plants what they build in your own Azure tenant — Entra-secured by default, governed by your Ops team, reading corporate data with each viewer's own identity.
The artifact is easy. The connection isn’t.
Section titled “The artifact is easy. The connection isn’t.”An app vibe-coded in Claude can’t reach your Fabric workspace, your internal APIs, or your data. It lives outside your boundary — a demo, not a tool. sprig is the deploy target that brings it inside. One prompt moves the artifact into your tenant, where Entra decides what it can reach, for the owner and for everyone they share it with.
Security review?
Trust model, the data-access principle, and the exhaustive list of permissions the installer creates in your tenant.
Installing sprig?
Requirements → Install → onboard builders. One command runs preview, install, deploy and smoke test.
Reference
The sprig CLI, platform API, skills and configuration.
How a publish happens
Section titled “How a publish happens”- A builder describes an app to Claude — and says “share this solution”.
- The sprig plugin calls your platform’s publish API with the builder’s Entra identity.
- The platform creates an owner-locked Entra app registration and a static web app in the builder’s own resource group, records provenance and audit metadata, and uploads the content.
- The app is live on an Entra-gated URL. Only the owner can open it — until your Ops team approves sharing with a team.
- When the app shows corporate data, it fetches it at view time with the viewer’s identity. Nobody ever sees data their own permissions wouldn’t allow.
Rooted in your cloud. Deploy with a prompt.