LESS SETUP. MORE “I MADE THIS.”
A little app.
A clear starting point.
Publish HTML, give it persistent data, and share a link. Use the Studio yourself, or give these API instructions to your coding agent.
Your first app.
- Open Sprigbase Studio and start a playground. No account is needed.
- Keep the lunch template or replace it with your own HTML.
- Review its collections and choose who can open the app.
- Select Publish app. Open the returned link to use the live app and its database.
A playground app expires exactly seven days after creation. Publishing an update does not reset the clock. Use Keep this playground before expiration to sign in and retain its apps.
Signed-in users can publish owner-only apps. This early-access private mode allows the owner to open the app; team and group sharing are on the roadmap.
Make your first app ↗Small data, clear permissions.
An app declares the collections it needs. A collection has a name, typed fields, and read/write policies. The lunch template uses this schema:
[
{
"name": "signups",
"read": "owner",
"write": "public-create",
"fields": {
"name": "string",
"note": "string"
}
}
]| Setting | Meaning |
|---|---|
read: "public" | App visitors may read this collection. |
read: "owner" | Reading the collection requires its workspace owner credential. |
write: "public-create" | App visitors may create records. This does not grant permission to read existing records or modify them. |
write: "owner" | Writing requires its workspace owner credential. |
fields | Field values must match their declared type: string, number, or boolean. |
A public signup form does not need a public list of signups. Keep responses private with read: "owner". Never embed a workspace credential in your app HTML.
Public app access and collection access are separate. A visitor can open a page while the platform still restricts its data operations.
A small browser SDK.
Published apps receive a window.sprig client for their own declared collections. To create a signup:
try {
await window.sprig.collection("signups").insert({
name: "Alex",
note: "Vegetarian"
});
// Show a success message in your interface.
} catch (error) {
// Show error.message and let the visitor retry.
}To list a collection that allows public reads:
const records = await window.sprig.collection("items").list();
// Each record has its fields plus id, created_at, and updated_at.Database calls are available on the published app. Studio’s Live app link opens the last published version in a new tab. Changes in the editor stay private drafts until you publish them.
Give your agent a place to publish.
The early-access integration is an HTTP API. A coding agent with network access can create a playground and publish a bundle. A packaged CLI and MCP integration are not part of this release.
1. Create a playground workspace.
POST /api/workspaces
Content-Type: application/json
{"mode":"playground"}The response includes a workspace and a secret token. The agent’s integration should retain that credential securely outside the conversation and use it as a bearer token for subsequent management requests.
2. Publish an app.
POST /api/apps
Authorization: Bearer YOUR_WORKSPACE_TOKEN
Content-Type: application/json
{
"name": "A little idea",
"html": "<!doctype html><h1>Hello, world.</h1>",
"visibility": "public",
"collections": []
}The response is {"app":{...}}, including the app ID, URL, and its expires_at deadline when applicable. Return the app URL and expiration to the person who requested it.
| Operation | Endpoint |
|---|---|
| List apps | GET /api/apps |
| Inspect an app | GET /api/apps/:id |
| Publish changes | PUT /api/apps/:id |
| Export code and data | GET /api/apps/:id/export |
| Delete an app and its data | DELETE /api/apps/:id |
Updates accept the same app fields as creation. Inspect the existing app before changing it. Deletion is destructive: confirm the user wants the app and its data removed.
Use the installation’s own HTTPS origin for every request. Treat workspace tokens as secrets. Do not place them in app HTML, browser URLs, logs, or chat replies.
One browser connection.
An integration can request account access through POST /api/auth/device, passing a descriptive client_name. Include its existing playground bearer credential to request keeping that playground.
POST /api/auth/device
Content-Type: application/json
{"client_name":"My coding agent"}The response contains a browser verification URL, a user code, a separate secret device code, an expiration, and a polling interval. Show only the verification link and user code to the person. They choose an available sign-in option and approve the named connection. Use the same sign-in option when returning to existing apps; accounts from different providers are kept separate.
The integration uses its secret device code to retrieve the approved workspace credential:
POST /api/auth/token
Content-Type: application/json
{"device_code":"YOUR_SECRET_DEVICE_CODE"}A 202 response means approval is still pending. Wait for the supplied polling interval before checking again, and stop when the request expires. After approval, the response contains a token and workspace. Store the credential securely and resume publishing. Signing in never requires copying credentials into a conversation.
A connection started from an existing playground can retain its app URLs and data. Each connection is scoped to the selected workspace. In a signed-in workspace, open Agent access in Studio to review or revoke connected agents. Revoking a connection keeps the workspace’s apps and data. Company SSO and directory provisioning are future enterprise features.
Your code. Your data.
Select an app in Studio and choose View data to inspect collection records, including private form responses. Choose Export app to download its current source, collection definitions, and data as JSON. Exports can contain private responses; store them accordingly.
Download the early-access platform source to inspect the implementation and its setup instructions. The project uses Apache-2.0. Your hosted apps and their data retain their own ownership.
The source includes both the Cloudflare implementation and a self-hosted server using Node.js 24 and SQLite. Follow the included README, install the dependencies with npm ci, then run npm start. A Docker setup is included as well. You do not need an account on our hosted service to run your own installation.
Early access, deliberately small.
This release supports HTML, CSS, browser JavaScript, schema-checked persistent collections, public or owner-only app access, workspace credentials, and export.
Playground apps have a fixed seven-day lifetime. Account apps have no playground deadline, but usage is bounded and subject to early-access limits. The API reports validation and quota errors when a request cannot be accepted.
Arbitrary server-side middleware, packages, scheduled jobs, custom domains, team sharing, enterprise SSO, SCIM, and compliance reports are not included in this release. The enterprise section on the marketing page describes the roadmap.
Use early access for small experiments. Keep exports of important data, and avoid collecting sensitive or regulated information in experimental apps.