Skip to content

Features

Every capability, and how they fit together.

Each one arrives as finished behaviour rather than a primitive to wire together, and each already knows about the others. A plan change updates permissions. A new account receives the right access. An upload is stored, scoped, and served.

Accounts

Users & auth

Not a users table. The entire account lifecycle, with an endpoint for every step of it.

  • Login, registration, and sessions from day one
  • OAuth, API keys, and bearer tokens for programmatic access
  • Invitations, email verification, and password resets
  • Roles and permissions, with scopes deciding who is granted what

Money

Payments & plans

It is your Stripe account — bring your own or connect through us. Either way you own it, and the money goes to you.

  • Plans created and wired in for you
  • Upgrades and downgrades handled, including proration
  • Usage counted against per-plan limits
  • Access gated on entitlement, and revoked when payment stops

Storage

Data & storage

Not a schema editor. Describe what the app tracks and the rest arrives with it.

  • REST endpoints generated per entity
  • Validation and per-user permissions applied on the way in
  • File uploads stored, scoped, and served
  • Every record addressable over REST and MCP alike

Intelligence

AI & actions

Prompts, chains, and tools wired to the data and integrations your app already has.

  • Prompts and chains defined against your own entities
  • Tools that call your integrations, not just the model
  • Exposed as REST endpoints or MCP tools
  • Metered against a plan like any other usage

Connections

Integrations

Your app talks to the tools your users already use.

  • Connect anything that speaks OAuth, API keys, or bearer tokens
  • Per-user connections, so each customer links their own account
  • Capabilities scoped per connector
  • Callable from your endpoints, chains, and automations

Your app as a platform

APIs & MCP

Everything in your app — data, actions, integrations — is addressable over REST and MCP, with per-user scopes deciding who is granted what.

  • A REST API over every entity and action
  • An MCP server for the same surface, one connection line away
  • Per-user scopes, so a customer grants only what they mean to
  • A customer's assistant can act without a browser involved

Operations

Apps & deployment

Live in five minutes, and still safe to change in month six.

  • Data, endpoints, and hosting live with nothing to provision
  • Deployments versioned, atomic, and reversible
  • Changes that would affect existing users flagged before they ship
  • Custom domain with SSL, and an admin dashboard from day one