Skip to content
Office

Membership for developers and indie saas

Accounts and paid plans for your app, without writing billing code

If you're shipping a small app, sign-in and subscriptions are a week of work you'd rather skip. Members handles sign-up, email code sign-in, Stripe checkout and plan changes, and gives your backend a signed token that says who the person is and which plans they have.

What gets in the way

  • Wiring auth, Stripe Checkout and webhooks together by hand
  • Keeping plan state in sync when a card fails
  • Building account and billing pages nobody will praise
  • Auth providers that charge per monthly active user

How developers and indie saas set up Members

  1. 1

    Drop in the script

    Sign-in and checkout windows open from `members.openLogin()` and `members.openCheckout(priceId)`.

  2. 2

    Verify on your server

    Send `members.getToken()` with each request and verify it against your workspace's JWKS. Middleware samples cover Next.js, Express and Workers.

  3. 3

    Listen for changes

    Signed webhooks for subscription, payment and plan events keep your own records in step.

  4. 4

    Skip the account page

    Plan changes, cards, receipts and cancellation live on the hosted account page.

Example

A $0 tier and a Pro tier for a CLI's web dashboard

A developer runs a web dashboard for her command-line tool. Free users sign in on the $0 plan; Pro is $12 a month with a 7-day trial. Her Next.js middleware verifies the member token and lets plans containing Pro through to the team features. A members.plan_changed webhook updates usage limits in her database the moment someone upgrades.

Everything here is part of Office Members, on every plan. See how other kinds of business use Members.

Try Office Members with your whole team

7-day trial with every feature. Cancel from the billing page whenever you like.