Easel for Platforms
Deploy the apps your users build, each in its own Easel project, from your own backend.
A platform is a product that deploys apps on behalf of its own users: an AI app builder, a site builder, or an internal tool that publishes many small apps. Your backend calls the Easel API, and your users only ever see your product.
The model is simple:
- One project per user app. Each app gets its own builds, functions, environment variables, logs, and domains.
- One Production deployment per publish. Every publish is a new deployment, and rolling back points production at an earlier one.
How an app gets published
For each app your users build, your backend:
- Ensures the app's project exists.
- Upserts its environment variables.
- Ships the source: an upload URL a sandbox can use, a streamed archive, or the files themselves.
- Follows the build with webhooks or by polling.
- Rolls back, assigns domains, and reads usage as needed.
The SDK wraps each step in one call, and the quickstart shows the whole loop in about 20 lines.
Pages in this section
| Page | What it covers |
|---|---|
| Concepts | Projects, hostnames, tokens, and what Easel doesn't run |
| Quickstart | Create a token and publish your first app from your backend |
| Deploy source | Upload URLs, streamed archives, and file lists |
| Tokens | Scoped, short-lived tokens for each job |
| Set up your domains | Your wildcard domain and branded CNAME target |
| Your users' domains | Names under your domain, and domains your users bring |
| Webhooks | Deployment and domain events, signatures, and retries |
| Usage and billing | Usage per app, for your plans or credits |
| UI blocks | Copy-paste components for your users' publish flow |
| API reference | Every endpoint, permission, and error code |