Stop rebuilding the backend. Auth, payments and access rules, behind one SDK.

Access is enforced on our servers by eight rules, so there are no RLS policies to write and none for your AI to get wrong. It works from the browser, Expo and Swift. Your framework, your host and your own server code stay yours.

Or set it up in
  • Free to build
  • No card
  • npm install @gemmein/sdk

Works with

From the client

Sign in

await g.auth.sendEmailCode(email)
await g.auth.verifyEmailCode({ email, code })
const user = await g.auth.currentUser()

Two calls. No passwords, no session code, no auth tables.

Save data

const notes = g.collection("notes")
await notes.create({ title })
const { records } = await notes.list()

Each person gets only their own. No policies to write.

Get paid

await g.subscriptions.checkout("pro")
const sub = await g.subscriptions.mine()
if (sub?.plan === "pro") unlock()

Stripe, into your own account. No webhook to build.

Your stack stays yours.

Gemmein adds a gate in front of your data. Your framework, your host and your own server code carry on as they are.

On your side of the line

Declare a collection

// gemmein/collections/bookings.json
{ "rule": "private",
  "means": "each member's bookings",
  "lockedFields": { "status": "requested" } }

A file in your repo, under one of eight rules. A customer can’t set a locked field, so they can’t confirm their own booking.

From your own server

const g = gemmeinServer(
  process.env.GEMMEIN_SECRET_KEY)
const { person, holdings } =
  await g.verifySession(token)
if (!holdings.access.includes("access:pro"))
  return deny()

On Vercel, a VPS, anywhere. Secret keys are scoped per collection, and the SDK refuses to run one in a browser.

Your code on our edge

export default {
  async run(ctx, input) {
    const res = await fetch(input.url, {
      headers: { authorization:
        `Bearer ${ctx.secret("API_KEY")}` } })
    return res.json()
  }
}

For anything the rules don’t cover. It reaches only the collections and hosts you approved, and never holds the real secret.

We built Gemmein after rebuilding the same backend for every app: the auth tables, the webhook handlers, the access policies an AI gets subtly wrong. Now it’s one SDK, and the rules are enforced on our servers.

What breaks at launch.

We keep a living report of verified launch failures, taken from public developer posts. Here’s what Gemmein does instead, on five of those patterns, and one more. Read the research

Configuration, secrets, domains and certificates that differ in production

Keys aren’t values you copy between machines. The Development key works on localhost and any https preview. The Live key works only on domains you verified, and your AI never sees it.

Sign-in that works in development and breaks on the real domain

There’s no callback URL, cookie domain or session store to get wrong. Sign-in is two calls to our servers, the same on localhost as on your domain.

Access, payments and email that fail silently

Your app has no webhook endpoint. Gemmein receives the payment event and grants access. A failed step retries on a schedule, then alerts you, and you can replay it.

Data and schema changes that outrun the code

Collections are files in your repo. Promoting to Live shows exactly what will change first, and never removes anything that’s already there.

Releases that differ from what you tested

If we host the site, every publish opens up to 12 pages at phone and desktop width first, and a broken page stops it. Each publish is kept as a version you can roll back to.

Data and endpoints left open

Access is one of eight rules on our servers, with no policy to write. Two test sessions prove it before launch and in CI, and go-live scans your build for a leaked secret key.

Not on this list: capacity on your own host, and outages at providers you call. Those stay yours.

Start in your editor

Add Gemmein to Cursor, Codex or Claude Code, or install the SDK and write it by hand. npx gemmein dev runs it on your machine.

Prove it in CI

Development is free, with real sign-ins and Stripe’s sandbox. reaffirm.mjs ships in the SDK — run it on every deploy to prove your rules.

Promote when you approve

Your AI and the command line never hold a live key. You approve each live change in the browser, with the changes listed. Live is from $29 a month.

48 things come with every app. Here are ten.

None of it is an add-on or a second product, and none of it is yours to maintain. Press any one to see what it does.

Run your own code on our edge With only the reach you approve.

A small piece of your own code that Gemmein runs. It reaches only the data and outside websites you approved.

Charge for work your own server does Your model, your host, our credits.

Charge credits for jobs your own server runs, such as your own model. Gemmein holds the price and settles what your server reports.

Locked fields A customer can’t mark their own order paid.

Lock a field so only you, an automation or your own server can set it. A customer can’t mark their own order as paid.

Sign-in by email code or Google No passwords to store, leak or reset.

Customers get an 8-digit code by email, or use Google if you switch it on. There are no passwords.

Subscriptions and free trials Through Stripe, into your own account.

Daily, weekly, monthly or yearly plans through Stripe. Free trials run from 1 to 730 days, one per customer.

A hosted site with a private preview Share a link before anyone else sees it.

Gemmein hosts your site the moment your AI builds it. One private link lets anyone you send it to see the preview. Change the link and the old one stops working. You can also host the app anywhere else and use Gemmein behind it.

An Expo SDK and a Swift SDK For iPhone, Android and Mac.

Build a phone or Mac app on the same sign-in, customers and data as your website: an Expo SDK for iPhone and Android, and a Swift SDK for iPhone and Mac.

Automations When this happens, do that.

A rule that runs by itself. When someone pays, when a record changes or on a schedule, it can give access, add credits or send an email. A failed step retries.

Eight privacy rules Checked by Gemmein on every request.

Each kind of data sits under one of eight rules, such as “only mine” or “anyone can view”. Gemmein’s servers check the rule on every request.

Your approval on every live change With the exact changes shown first.

Your AI can build freely in Development. Anything that changes your live product waits for you to approve it in your browser, with the changes listed.

And 38 more

Launch it

Your own web address

Put the live site on a domain you own by adding one record at your domain provider. Https is set up for you. It’s optional: every app also gets a free Gemmein address.

Stay signed in on up to 10 devices

Each customer can stay signed in on up to 10 devices for 30 days, and can sign any of them out.

Sell one-off products and downloads

Sell a single item such as a PDF, a video or a licence. The buyer gets a download, and it stops working if you refund them in full.

Let people buy before they sign up

Someone can buy a product without an account. It becomes theirs the first time they sign in with that email.

Sell credit packs

Sell a balance of credits that customers spend on AI features or on any action you put a price on.

App Store and Google Play purchases

In-app purchases reach Gemmein through RevenueCat, so buyers get their access automatically.

Photo, audio and video uploads

Customers can upload images and documents up to 25 MB, audio up to 100 MB and video up to 500 MB. Files follow the same privacy rule as the data they belong to.

Pages tested before every publish

Before a publish goes out, Gemmein opens up to 12 pages at phone and desktop width. A page that breaks stops the publish.

Run it

An inbox for customer replies

When customers reply to your emails, the messages land in one Inbox. Reply yourself, or approve a draft from your AI.

A dashboard with a page per customer

See each customer’s plan, payments, credits, activity and signed-in devices in one place.

Show any data as a table, cards, calendar or board

A page over one kind of record, shown as a table, cards, a calendar or a board, with totals. Ask your AI for one.

Add buttons like Confirm and Cancel

A view can carry buttons that move a record from one state to the next, such as from requested to confirmed.

Send email from your own address

Receipts and updates go out from your own domain, never from a Gemmein address.

Receipts and sign-in emails in your branding

Add your logo and colours to sign-in emails, and let your AI write the receipt and update emails.

Run something every 15 minutes, hour, day or week

Put any automation on a schedule: every 15 minutes, every hour, every day or every week.

Give a customer free access or credits

Give one customer free access, a trial or extra credits from their page, with a reason and an optional end date.

Suspend, sign out or delete a customer

Suspend a customer, sign them out of every device, or delete them for good.

Roll the site back to any earlier version

Each publish is kept as a version. Go back to an earlier one in one step, or download any version as a zip.

A record of every change and approval

Every change to your app and every approval is recorded, so you can see what happened and when.

Trust it

Hold customer posts until you approve them

Set a collection so customer posts stay hidden until you approve them.

An emailed code for bigger changes

Changes to how the business runs, such as prices or domains, also need a code we email you.

An authenticator app on your own account

Add an authenticator app to your Gemmein account for a second code on important changes.

A live key your AI never sees

The key to your live app is shown to you once, on your own screen. It is never sent to your AI.

New-device sign-in alerts for customers

Customers get an email when their account is signed in from a new device or country.

Customers can export or delete their data

Every customer can download their data or delete their account from inside your app.

A scan for leaked keys before you go live

Before you go live, Gemmein reads your site and stops if a secret key was left in it.

Nothing deleted if you stop paying

If your plan ends, your live app pauses. Your data, customers and settings stay, and building is still free.

Going over a limit never bills you

Going over a limit never adds a charge or moves you up a plan. We email you first.

Go further

Follows, blocks and private accounts

Customers can follow each other, block someone, or make their account private so that follows need approval.

Private groups and followers-only posts

Customers can make small groups called circles and post just to them, or just to their followers.

Likes, polls and RSVPs

Add a like, a one-choice poll or a yes, maybe or no answer to any post. Each person counts once.

Direct and group messages

Customers can message each other one to one or in groups of up to 20. You can read these from your dashboard.

Leaderboards

Rank records by a number, such as a score, with ties handled for you.

AI features with a price in credits

Add an AI feature and set what it costs in credits. Customers can’t change the prompt, the model or the price.

AI images, video, speech and transcription

Beyond chat, AI features can make images and video, speak, or turn audio into text.

Charge credits for any action

Charge credits for something that isn’t AI, such as a premium export. Credits go back if the action fails.

Paddle, GoCardless and other payment providers

Take payments through another provider. An automation gives the buyer their access.

A command line and SDKs for web, Expo and Swift

Developers get a command line and code libraries for the web, Expo and Swift.

Eight rules, not RLS policies.

  1. Each collection sits under one of eight rules, checked on our servers on every request. There’s no policy language for you or your AI to get subtly wrong. Try them.

  2. Two test sessions try to read each other’s data and must be refused. Your AI runs it before launch, and the same check runs in your CI.

  3. It builds freely in Development. Putting changes live, deleting a collection and issuing a server key all wait for your approval in the browser, with the exact changes shown first. How we secure it

Free until you have a business.

One flat price for your whole account, not per app. Pay yearly and get two months off.

Build

Build and test with your AI.

$0Start building
  • Apps 3, not live
  • Sign-ins Real, capped daily
  • Card Not needed
  • Logs kept 30 days
  • Support 1 business day

Launch

Your first business, live.

$29 a monthChoose Launch
  • Apps Up to 5
  • Customers a month 100,000
  • Emails a month 10,000
  • Storage 50 GB
  • Support 1 business day

Run a business Recommended

When it’s earning.

$79 a monthChoose Run a business
  • Apps Up to 10
  • Customers a month 100,000
  • Emails a month 24,000
  • Storage 200 GB
  • Support 1 business day

Grow

Several businesses at once.

$199 a monthChoose Grow
  • Apps Up to 25
  • Customers a month No visible limit
  • Emails a month 70,000
  • Storage 500 GB
  • Support Priority

No cut of your salesNever an automatic chargeNothing deleted if you stop paying

Questions

What if a rule doesn’t fit?

Write an Edge function: one module of your own code that we run, with only the collections, outside hosts and secrets you approved. For long or heavy work, run it on your own server with a scoped secret key. The rules are the default, and they don’t box you in.

Do I have to host with Gemmein?

No. Keep your framework and your host, such as Vercel or Cloudflare, and use Gemmein behind it. Our own hosting serves static files and is optional.

Can I use it without an AI?

Yes. Run npm install @gemmein/sdk, declare your collections as JSON files, and npx gemmein dev gives you a local runtime. The AI connector drives the same files and the same calls.

What doesn’t it do?

Our site hosting serves static files, so for server-side rendering you host on Vercel or anywhere else and use Gemmein behind it. No realtime push: live data is polled, every 10 seconds by default. No passwords: customers sign in by emailed code, or with Google if you turn it on. One owner per account, with no team seats. No carts or physical goods. If one of those is a must, we’re the wrong fit.

How do I get my data out?

Export the whole account, any one customer’s data, or any version of your site as a zip. If your plan ends, the live app pauses and nothing is deleted.

Where does the money go?

Straight into your own Stripe account. A Stripe account is free to open, your AI walks you through it, and Stripe charges its usual card fee.

Who’s behind this?

Gemmein Limited, registered in England and Wales (no. 17339623) and with the ICO. Write to hello@gemmein.com.

  1. Declare the data.
  2. Pick a rule.
  3. Take the payment.
  4. Prove it in CI.
  5. Spend your time on the product.

Add Gemmein to your editor. Or install the SDK and write it yourself.

Building is free. No card until you go live.

Add Gemmein to your AI

Add to Cursor