Is this a real person?
A valid verification needs a passport-verified human, on their own phone, authenticating with Face ID, Touch ID, or their passcode at the moment you ask. No bot, script, or AI can produce one.
not.bot Verify
AI can fake anyone. not.bot Verify proves your users are real.
not.bot™ Verify sorts the real users from the bots and the burner accounts, and can check age thresholds. Users prove they are human once, then move through your site with no selfie and no doc upload. More conversions, fewer bots.
Three answers, one integration
Ask only what you need. Learn nothing else.
not.bot Verify answers three kinds of question about a user. You choose which to ask. The user sees the request and approves or declines.
Is this the same person again?
A Site Pass recognizes a returning human across every alias and account they use on your site, and tells you nothing about who they are off it. Ten “different” accounts that are one person stop working: fake reviews, promo cycling, scalping.
Are they old enough?
Ask over 18, over 21, or any threshold you set. You get back yes or no. You do not learn their birthday, their age, or their name.
Use cases
Human-only experiences, on top of the site you already run.
You do not gate the whole site. You open specific experiences to verified humans and leave the normal path for everyone else.
A badge that means human.
Members sign in with not.bot and wear a verified-human mark, so the room can see who is real.
Reviews you can trust.
Each rating comes from one unique verified person, so a rating means what it used to.
Tickets that reach fans.
Verified humans get first access before scalper bots can grab the best seats.
Spaces a ban can hold.
A removed person cannot walk back in under a fresh account, because you can see the human behind the alias.
A head start for humans.
Put a news drop or earnings release behind a verified-human window for its first hours, so people read it before bots trade on it.
Honest ad metrics.
Pay for confidence your ads reached real people in the age group you wanted, not a bot farm inflating the count.
How it works
It runs in your infrastructure, not ours.
not.bot Verify is software you host. It installs into your own cloud and sits behind your existing security, so not.bot is never in the path of your traffic and your data never leaves your infrastructure.
-
Your site shows a tap-to-verify link on a phone, or a QR code on a desktop.
-
The link opens the not.bot app. It shows your site’s name and what you asked for, and the user approves or declines.
-
Approval takes a Face ID, Touch ID, or passcode check. Your site gets back a signed answer to exactly what it asked.
The deploy step is the point. Because Verify runs in your own cloud, your users’ data never leaves your infrastructure, which is what regulated buyers need and what shortens a security review. An engineer, or a coding agent, can have it live in about half a day.
Built by Julia Social
Audit it before you trust it.
not.bot Verify is built to be inspected, not taken on faith. The proof is published, the code is open, and the security work is certified.
Open-source SDK.
The SDK your team integrates is open source, so your engineers can read every line before it ships.
Certified foundations.
The identity checks behind a not.bot human run through certified partners, with the architecture, privacy, and security model published in full.
No token. Not crypto.
No wallet, no token, no fees in anything but dollars. The cryptography is plumbing you and your users never touch.
No forced enrollment.
You open human-only features to the people who want them. Everyone else uses your site the way they do today.
Pricing
Pick a plan. Pay for the humans you verify.
Every plan is the same software, self-hosted, with the same open SDK. Plans differ in how many monthly active users they include and the support you get. A MAU is one unique not.bot alias that interacts with your deployment during the month, counted the same way whether or not you use Site Passes.
Sandbox
$9.99/month
For kicking the tires. Wire up not.bot Verify and test it before you go live. Not built for production traffic.
- 10 MAUs included
- $0.99 per additional MAU
- Community support (Discord)
Most popular
Basic
$249/month
The usual starting point for a live site.
- 1,000 MAUs included
- $0.40 per additional MAU
- Standard support (email, next business day)
Advanced
$1,750/month
For high volume, where the lowest per-MAU rate pays off. Every MAU is metered at the same low rate, the way large deployments expect.
- 0 MAUs included
- $0.20 per MAU
- Priority support (email, priority response)
Enterprise
Let’s talk
Custom terms, scale, and a dedicated contact.
- Volume pricing
- Dedicated support
- Deployment and procurement support
Checkout opens at Stripe; you’ll be redirected and returned here. Monthly billing. You pay your plan price plus any MAUs above what it includes, at your plan’s rate. You are never billed for the servers or blockchain nodes you run, only for the humans you verify.
| Sandbox | Basic | Advanced | Enterprise | |
|---|---|---|---|---|
| Monthly | $9.99 | $249 | $1,750 | Custom |
| Included MAUs | 10 | 1,000 | 0 | Custom |
| Per additional MAU | $0.99 | $0.40 | $0.20 | Volume |
| Support | Community | Standard | Priority | Dedicated |
| Best for | Evaluation | Most sites | High volume | Scale & custom |
Questions, answered
The questions buyers ask.
What counts as a MAU, and could my bill spike?
A MAU is one unique not.bot alias that interacts with your deployment in a calendar month, counted the same way whether or not you use Site Passes. You pay your plan price plus any MAUs above what the plan includes, at your plan’s per-MAU rate. There are no hidden multipliers.
What do I need to deploy it, and how long does it take?
You host it in your own Kubernetes cluster, with PostgreSQL 14+ and Keycloak 22+. An operator comfortable with Kubernetes, or a coding agent, can have it running in about half a day.
Which users can enroll today?
Anyone in the US with a passport can enroll now, and more countries are on the way. Anyone, anywhere, can verify.
What happens if not.bot’s servers go down?
Your verifications keep working. Verify runs in your own infrastructure and stays out of your traffic path; a running deployment does not depend on not.bot for day-to-day operation.
Is the Sandbox for production?
No. Sandbox is for evaluating and integrating Verify before you go live. Basic is the usual starting point for production traffic.
Can I cancel anytime?
Yes. Billing is monthly, and you can cancel at any time.
How do I move from Sandbox to production?
Change your plan from the admin service; the same deployment carries over. Higher tiers add MAU allotment and support, not different software.