Tier 2
Build apps with Supabase Auth
Orbit wires Supabase Auth natively into every fullstack build — email/password, OAuth, session cookies, and RLS-scoped profiles, ready in the preview.
Supabase Auth AI Builder
Supabase Auth is the default identity layer for Orbit fullstack apps. The harness configures auth URLs, builds sign-in flows, and scopes RLS policies to the authenticated user — no manual setup.
In plain English
Supabase Auth is Orbit's default login: email, Google, sessions, and security rules keyed to each user — wired up automatically in fullstack builds.
How it works in Orbit
Supabase Auth is what Orbit wires in by default: email/password, OAuth, sessions, and roles — all managed from the same project as your database.
One project, one security model
Auth and data live in the same Supabase project, so identities and row-level security share a model. No syncing users between services.
- Auth + data unified
- RLS works with auth
- One place to manage
Providers out of the box
Email/password works immediately; Google, GitHub, and other OAuth providers connect through the dashboard. Orbit configures the settings for you.
- Email + password
- OAuth providers
- Dashboard-configured
Sessions that just work
Refresh tokens, session recovery, and remember-me are handled by the generated client. Users stay logged in across visits.
- Automatic refresh
- Persistent sessions
- Secure by default
Build with auth
Describe who signs in.
Get the screens
Login and signup wired automatically.
Add providers
Enable OAuth in the dashboard.
Ship
Auth and RLS work together.
The challenge
Try it yourself
Run this one on a competitor first — then on Orbit. Same prompt, and keep score.
Build
Try this one elsewhere first.
Build two apps with logins and try to view another user's data in each. Orbit's database rules should stop you cold.
Research
Ask a research tool to go deep on one topic.
Then ask Orbit. Compare how many rounds it runs, how many sources it actually reads — we target 65+ — and whether every claim in the final report has a link attached. Bring a bigger coffee mug.
Chat
Ask a plain chatbot the same question.
One just talks. Orbit's agent actually searches the web, runs code, reads your files, and comes back with something done. Compare how many tabs you opened and how many are still open when you're finished.
Image & video
Generate the same image, then edit it.
Ask two tools for the same hero shot, then ask both to recolor it, fill in the background, and animate it. Compare who hands you a first draft and who keeps refining in the same conversation.
150+
models routed per task
1h
cloud sandbox sessions
25
tool calls per chat turn
8–14
deep research rounds
What you can do with Supabase Auth AI Builder on Orbit
Sign-in UI included
Email/password and OAuth flows generated into the app.
RLS-scoped sessions
Policies keyed to auth.uid() secure every query.
Zero auth code
Identity is managed server-side by Supabase Auth.
Compare sibling stacks
Clerk AI Builder
Orbit provisions authentication with the same frictionless DX as Clerk — email, OAuth, and session management — through Supabase Auth, wired into your generated app.
Auth0 AI Builder
Orbit provisions enterprise-grade auth — social login, multi-tenant users, role-based access — via Supabase Auth, embedded in your build.
Better Auth AI Builder
Orbit provisions clean, codebase-native auth like Better Auth's — but server-managed through Supabase Auth so no auth code ships in your bundle.
Firebase Auth AI Builder
Orbit replaces Firebase Auth with Supabase Auth in generated apps — same email/OAuth/session features with RLS on a relational backend.
Explore more
Clerk AI Builder
Orbit provisions authentication with the same frictionless DX as Clerk — email, OAuth, and session management — through Supabase Auth, wired into your generated app.
Auth0 AI Builder
Orbit provisions enterprise-grade auth — social login, multi-tenant users, role-based access — via Supabase Auth, embedded in your build.
Better Auth AI Builder
Orbit provisions clean, codebase-native auth like Better Auth's — but server-managed through Supabase Auth so no auth code ships in your bundle.
Firebase Auth AI Builder
Orbit replaces Firebase Auth with Supabase Auth in generated apps — same email/OAuth/session features with RLS on a relational backend.
Frequently asked questions
Is Supabase Auth set up automatically?
Yes. Fullstack builds configure the auth client, build sign-in/sign-up UI, and create RLS policies keyed to auth.uid() as part of provisioning.
Is Supabase Auth included in every build?
Fullstack builds provision Supabase, and auth screens are generated when your spec includes login. You can also add auth to an existing app with one prompt.
Can I customize which OAuth providers appear?
Yes — Google, GitHub, and other providers are configured from the Cloud panel, and you toggle them per app. Sessions, refresh tokens, and role-based access are handled for you.