What your app can do

Technically OAuth, with the same session the emailed code produces.

Technically An organisation with members, roles and one balance.

Technically Roles checked in one place rather than remembered in every handler.

Technically A payment provider's subscription, with the webhook that keeps your database honest.

Technically A checkout session and a receipt.

Technically Generated per period, downloadable, with your details on them.

Technically MDX posts with metadata, a feed, and the tags that make search work.

Technically A docs layout with search across it.

Technically Postgres full-text, because you already have Postgres.

Technically Threaded, moderated, tied to whoever wrote them.

Technically A block editor storing structured content rather than a soup of HTML.

Technically A widget that writes to a table you own, with the page it was sent from.

Technically Requests and votes in your database, ranked, with a board that reads them.

Technically A provider account, a verified sending domain, and templates in your repository.

Technically Generated from what actually deployed.

Technically Routed to your app's agent first, escalated with the conversation attached.

Technically A grid that survives having two items or seven.

Technically Tiers from a config file, wired to your checkout.

Technically Quotes with attribution and a photo, or without.

Technically An accordion that is still readable with JavaScript off.

Technically A call to action that reads differently to somebody signed in.

Technically Subscribers in your own database, yours to export.

Technically Signed direct upload to a bucket, so files never touch your server.

Technically Transformed on the way out and cached at the edge.

Technically An export they can ask for and download.

Technically An import that shows you what it will do before it does it.

Technically An Eve project in your repository, deployed with the app.

Technically Typed tools, one per file.

Technically Skills the runtime loads.

Technically Memory slots scoped per person, in your own Postgres.

Technically A frontend client wired to the agent's sessions.

Technically A gateway the app calls; the key is mine and the spend lands on your credits.

Technically One setting, read at call time, so changing it needs no deploy.

Technically Subagents with their own tools and their own instructions.

Technically Durable runs that resume where they stopped rather than starting again.

Technically Append-only, per account.

Technically Flags evaluated per account, changeable without a deploy.

Technically Events in your own database rather than somebody else's script.

Technically Generated from what you told me your app collects.

Technically Shown only where the law asks for it, remembering the answer.

Technically A cascade across every table, and a record that it happened.

Technically Fed by the same build and health data I already read.