Each signed-in person sees and edits only their own records.
Orders, client notes, saved work — anything where people keep their own things and nobody else's.
How it works
The whole of Gemmein, in detail.
The homepage is the short version. This is every part of it: how a rule is written and where it is held, what the five layers actually do, what the console gives you when a customer emails, what it costs, and what it cannot do yet. Nothing here is a roadmap item.
gemmeinregister
enforcing
OPEN
her own records
Amara, signed in
- Identityit's Amara
- Rulesshe owns them
- Data3 found
- Paymentsplan active
- Auditwritten down
Every time anyone tries anything in your app, this decides what they're allowed to see, and writes down what happened. You never build any of it.
Rules
How a rule is written, and where it is held.
Not settings — decisions. Who your app is for, and what each person is allowed to do, isn't configuration. It's the product itself.
Almost every idea is one of these three.
Anyone can read the posts. Signed-in people write their own.
A directory, a community, a marketplace — the world can look, only your people can add.
Anyone can look. Only paying members can open a lesson.
A course, a newsletter, a paid tool — where the money and the access are the same question.
Whichever it is, that one sentence is the decision. Gemmein asks it once, writes it down, and holds every part of your app to it from then on — whatever your AI builds next.
Run this first, then build
npx -y gemmein init
What Gemmein handles
What each of the five layers actually does.
Not a kit to assemble. All five are on from your first command, and they are the same on the free plan as on the paid one.
They get a one-time code by email. There is no password database, so there is nothing to leak and no reset flow to abuse.
IdentityOne plain-English rule per collection. Gemmein checks it on every request — the browser never gets a vote, whatever your AI wrote.
RulesStored, backed up and handed back only to the people your rule allows. No server to run, patch or pay for.
DataStripe takes the card on your own account. Gemmein remembers who paid, so what someone can see can depend on it.
PaymentsWho did what, and when — including every request that was refused. So "why couldn't they see it?" always has an answer.
AuditSecurity is the product, not the upsell. The same foundation is included while you build and when you go live. Read the whole story
The console
What the console gives you when a customer emails.
Refund me. I can't sign in. Delete my account. Your app has nowhere to answer that — Gemmein does: every customer, what they paid, what they did, and the controls to put it right.
Benchtimelive — already yours
healthy
Today
People signed in, records were created, and unsafe reads were refused.
128people signed innew this week
1,204records createdtoday included
3,441receipts writtenevery action
while you were away all activity →
record_createamara@your.imaginationplan_startjoel@your.imaginationrefusedanonymous read of someone's recordssigned_inpriya@your.imagination
What you'd otherwise have to build, secure and keep running.
Build as many ideas as you like, for as long as you like — that part is free and stays free. You pay the day someone who isn't you signs in, and on that day everything you decided is already holding. Nothing to rebuild, nothing to switch on.
Build everyone starts here
Free
As many ideas as you want, for as long as you want. No card, no account, no time limit.
- All five foundations, on your machine
- The full console while you build
- Nothing leaves your computer
npx -y gemmein init
Live
from$50/mo
The day it stops being yours alone. Same app, same rules, now open to customers.
- Room for 1,000 people — an account in your live app
- Its own keys, kept apart from anything you build with
- Same security as every other plan
card enters through Stripe, at go-live
Growing
from$150/mo
More room, for when it's working and more people keep coming.
- Room for 10,000 people
- Move up when you choose to, never automatically
building something larger? talk to us
You choose when the bill starts. Your card enters at go-live through Stripe, and building stays free until then.
Building something larger? Talk to Gemmein
Questions
Asked before you have to ask.
If the answer would be embarrassing, it's still here. Nothing on this page is a roadmap item.
Ask us something elseThe infrastructure under an app built with AI, plus the back office to run it: passwordless sign-in, Rules, Data, Payments and Audit under the app you build. You paste one command into your AI builder and answer four plain questions.
Never. Stripe processes every payment end-to-end, on your own Stripe account. Gemmein only listens for "they paid" and keeps the record straight — who's subscribed, who bought what. Your money goes to you.
Those are professional toolkits: enormously flexible, and safe only if you configure the security correctly — which AI-written code routinely gets wrong. Gemmein is deliberately smaller: the safety rules are the only rules, they're written in plain English, and the server enforces them no matter what code your AI writes. Less to configure is the feature.
We'd rather tell you now: it's web apps only (no mobile SDKs yet), there are no teams-with-roles, no realtime sync, and no marketplace payouts. If your app needs those today, Gemmein isn't your backend yet — and your AI will tell you so instead of faking it.
You move your app to Live in the console: your card enters (through Stripe), the shape of your data is locked so nothing can quietly corrupt it, and your live app gets its own keys. Building stays free forever; you pay only when your app serves real people.
That's all of it.
Nothing above is coming later. It is what runs the moment you paste the command.