Features
Built for static sites.
Not for infrastructure teams.
A focused set of primitives — each one designed to solve a specific problem that static site developers face.
Collections & Schema Validation
A Collection is a named bucket of JSON documents — like a table, but schemaless by default. Add a JSON Schema (draft 2020-12) to enforce shape. Every submission is validated before it's written; failures return a 422 with field-level errors.
- Schemaless by default — start fast, add constraints later
- Schema updates apply to future items only — existing data is never invalidated
- Page through Items from the API, up to 100 at a time
- Stored as PostgreSQL JSONB for fast querying
{
"type": "object",
"required": ["text", "author"],
"additionalProperties": false,
"properties": {
"text": {
"type": "string",
"maxLength": 1000
},
"author": {
"type": "string"
},
"rating": {
"type": "integer",
"minimum": 1,
"maximum": 5
}
}
}
const API = 'https://app.extatic.io/api/app_3f9a1c7d2b8e4f60';
async function login(email, password) {
const res = await fetch(`${API}/auth/login`, {
method: 'POST',
headers: { 'Content-Type': 'application/json' },
body: JSON.stringify({ email, password }),
});
if (!res.ok) throw new Error(`Login failed (${res.status})`);
return res.json();
}
const session = await login(email, password);
// → { access_token, token_type, expires_in,
// refresh_token, user }
// Send it on writes:
// Authorization: Bearer ${session.access_token}
AppUser Authentication
Your site's visitors are AppUsers, separate from your dashboard team. They register and sign in with email and password. Extatic stores the passwords, sends verification and reset emails, and issues a short-lived JWT scoped to your App, plus a refresh token.
- Register, verify email, sign in, refresh, reset a password, and sign out everywhere
- Visitors can update their profile, change their password, or delete their account
- AppUsers own the Items they create; only they can edit or delete them through the Client API
- From the dashboard you can disable an AppUser, revoke their sessions, or send a password reset
File Attachments
Turn on uploads per Collection. Files are stored in Azure Blob Storage, and each attachment gets its own URL. Choose allowed file types per Collection, and size, count, and storage limits per App, from the dashboard.
| Setting | Scope | Default |
|---|---|---|
| attachments_enabled | Per Collection | false |
| allowed_attachment_types | Per Collection | All types |
| max_file_size_mb | Per App | 10 MB |
| max_attachments_per_item | Per App | 10 per Item |
| storage_quota_gb | Per App | 1 GB |
const form = new FormData();
form.append('file', fileInput.files[0]);
// Signed-in AppUser, on an Item they own
const res = await fetch(
`${API}/collections/photos`
+ `/items/${itemId}/attachments`,
{
method: 'POST',
headers: {
'Authorization': `Bearer ${session.access_token}`,
},
body: form,
}
);
const attachment = await res.json();
// → { id, filename, content_type, size_bytes, url, ... }
console.log(attachment.url);
Supported Events
item.created
item.updated
item.deleted
appuser.registered
appuser.verified
appuser.login
appuser.deleted
Feature modules add their own events, such as form.submitted.
Retry Schedule
- 1. Immediate
- 2. +1 minute
- 3. +5 minutes
- 4. +30 minutes
- 5. +2 hours
- 6. +12 hours → deactivated if it fails
Webhooks
Subscribe any HTTP endpoint to Extatic events. Every delivery is signed with HMAC-SHA256 so you can verify the payload came from Extatic. Failed deliveries retry automatically with exponential backoff.
-
HMAC-SHA256 signature on every payload (
X-Extatic-Signature: sha256=…) - 7-day delivery logs with the payload, response status, and response body
- Manually re-trigger any delivery from the dashboard
- Deactivated after six failed attempts, with an email to the App owner; turn it back on from the dashboard
Team Collaboration
Share App management with your team using roles. Invite by email; collaborators accept the invitation before they get any access.
| Capability | Owner | Admin | Editor | Viewer |
|---|---|---|---|---|
| View Apps, Collections, and Items | ||||
| Create and edit Items | ||||
| Manage Collections | ||||
| Manage Webhooks | ||||
| Manage Collaborators | ||||
| Regenerate the secret API key | ||||
| Delete App |
Schema Library
Don't write every JSON Schema from scratch. Pick a ready-made schema when you create a Collection, or save your own and reuse it across Collections. Every App has it.
- Shared schemas from Extatic, plus your App's own
- Schemas are versioned, with a version history
- See which Collections use a schema before you change or archive it
Creating a Collection
- Click Choose from library, preview a schema, and click Use this schema.
- The schema is copied into the Collection, so you can adjust it there. Later library edits never change it on their own.
- When the library has a newer version, the dashboard shows what changed, and Apply update takes it. Only Items saved afterwards are affected.
claude mcp add --transport http extatic \
https://app.extatic.io/mcp \
--header "Authorization: Bearer $EXTATIC_TOKEN"
# Then ask:
# "Create a posts Collection with a title, body,
# and publish date, add three sample posts,
# and write an index.html that lists them."
AI assistants (MCP)
Extatic runs a Model Context Protocol server, so Claude Code, Cursor, or any MCP client can set up your backend: create Apps and Collections, seed content, and read the same guide you would, then write site code that calls Extatic correctly.
- Acts as you, within your role on each App
- Limit a token to read-only, to certain Apps, and to an expiry date
- Visitors' data stays hidden unless you allow it
- No delete tools, and it never sees the secret API key
- Every change it makes is logged with the token's name
Keys and tokens
Each caller gets its own credential, so nothing secret ever has to go into your site's code.
| Credential | Looks like | Used for | Handling |
|---|---|---|---|
| App ID | app_… |
In every Client API URL | Public: safe in browser code |
| Secret API key | X-Extatic-Secret-Key: exk_… |
Server-to-server calls to some feature endpoints, such as search indexing | Secret: servers only. The owner can regenerate it |
| Personal access token | Bearer ext_pat_… |
Your AI assistant, at the MCP server | Secret: shown once, expires, revocable |
| AppUser access token | Bearer eyJ… |
A signed-in visitor's writes | Short-lived; refreshed with a refresh token |
Feature modules
Ready-made backends for common site features
Turn on what your site needs. Each module comes with its own dashboard screens, Client API endpoints, and webhook events.
Authentication
Every AppVisitors register and sign in with email and password. Extatic handles verification, password resets, and sessions, and issues an App-scoped JWT.
Schema Library
Every AppStart a Collection from a ready-made JSON Schema, or save your own to reuse. Collections remember which version they started from.
Forms
Coming soonAccept submissions from a plain HTML form or fetch, with schema validation, spam trapping, email notifications, and a form.submitted webhook.
Comments
Coming soonModerated comments for your pages: approve, reject, or mark as spam, close a page's thread, and show comment counts.
Search
Coming soonFull-text search over your Collections, with suggestions as visitors type. No external search engine.
Events
Coming soonEvent registration with capacity limits, waitlists, confirmation emails, calendar files, and check-in.
Scheduling
Coming soonBookable time slots from your calendars and availability rules. Customers cancel or reschedule from a link.
Members
Coming soonMembership plans that signed-in visitors join, with optional approval, expiring terms, renewals, and an opt-in member directory.
Donations
Coming soonOne-time and recurring donations through your own Stripe account. Extatic never holds funds or sees card data.
How features roll out
- Coming soon
- We're building and testing it. Contact us if you'd like early access.
- Preview
- Try it for free from your App's Features page. Details may still change.
- Available
- Stable, and either included with every App or offered as a paid add-on.
If a preview becomes a paid add-on, Apps using it are emailed and keep access for 30 days. If a feature isn't enabled,
its API calls return 403 with code: "feature_not_enabled", and your
existing data for it stays readable and exportable. See the changelog for what's new.