One collection.
Three callers.
Different answers.

A hosted database with visitor identity and per-collection access rules, for frontends with nothing behind them. Change the caller and watch the same collection answer differently.

GET /reviewsAS PUBLIC
reviews  read public  create authenticated  update owner:author  email visible:none
RATING
BODY
BY
EMAIL (visible: none)
POST /reviews
Leave a review…
01

It persists

Every row above lives in a real database, written from a page with no server behind it.

02

It knows who

A visitor is remembered from their first write, with no account, and can verify an email later.

03

It refuses

A field you may not read does not come back at all. The rules live in the schema, not in code you host.

Join the beta.

Accounts open in batches. Leave an address and we send an invite.

This form is not a mockup. It is a sch3ma collection on sch3ma, saved by the code beside it. Only project authority can read the list back.

# anyone may join. no read rule, so only project # authority ever reads the list back. curl -X PUT "https://admin.sch3ma.com/$P/_schemas/waitlist" \ -H "Authorization: Bearer $SK" \ -d '{ "prefix": "wlt", "rules": { "create": "public" }, "fields": { "email": { "type": "text", "required": true, "maxLength": 254, "visible": "none" } } }'