Merged

#247

feat: migrate auth to Supabase magic links

feat/auth-flow→main

src/lib/auth.ts

+4−1

@@ -12,7 +12,9 @@ export function AuthProvider

const signIn = async (email) => {

− return fetch('/api/login', { body: email })

+ const { data, error } = await supabase.auth

+ .signInWithOtp({ email })

+ if (error) throw error

+ return data

}

All checks passed

2m ago

Agent

Analyzing repo structure...

Tests

passing

auth.spec.ts12✓

api.spec.ts18✓

db.spec.ts17✓

Total47/47

Pipeline

● RUNNING

Build

Test

Deploy

swarmz.app2.1s

For Engineers

Ship fasterwith
AI-poweredagents

Scaffold projects, refactor code, and iterate with autonomous agents. Focus on architecture decisions while AI handles the boilerplate.

For engineers

Skip the part of every project you've already built ten times

Stand up auth, a database, a deploy target, and a working dev environment in the time it takes to argue about which ORM to pick.

Get past the boilerplate, on to the actual code

Every new project eats the same first day. Auth wiring, a Postgres schema, a session cookie, an .env file, a deploy target. Swarmz spins all of that up so you start at the part of the codebase you actually care about. The output is plain TypeScript and SQL you can read end to end and rewrite if you don't like it.

A code editor showing working auth boilerplate

Settle a technical debate in an afternoon

You think the new approach will work. The team isn't sure. Build a real version of it before lunch instead of arguing in Slack. Swarmz gives you a running app on a public URL with a working backend in minutes, so the prototype is something people can click on instead of a whiteboard sketch.

A live prototype running at a swarmz.cloud subdomain

Build the internal tools you keep putting off

Nobody on the team wants to spend a sprint on the admin panel. So nobody does, and you're still grepping production logs for refunds six months later. Hand the boring CRUD UI to the agent. You get an admin lookup, a billing-reconciliation panel, or a debug-query tool without burning a real engineer on it.

Reads your existing Supabase schema and writes a CRUD UI on top
Auth and role checks wired in, not stubbed out as TODOs
You own the code, so extending it later doesn't require a vendor ticket

An admin lookup panel with user rows and inline actions

A real workspace, not a sandbox toy

Every Swarmz project runs in a Linux container with a file tree and a working terminal. Open it. Run pnpm test. Drop into a shell, edit a migration by hand, push to GitHub. The agent works on the same files you do. Nothing is hidden behind a generator.

Full terminal in the browser with pnpm, git, curl, and anything else you'd apt install
Two-way GitHub sync so the canonical repo stays yours
Open the same container from your IDE over MCP

A workspace terminal running tests in the browser

AI pair on the parts you don't enjoy

You like writing the architecture. You don't like writing the seventh form component this month, or the fifth admin CRUD page after that. Hand the agent the muscle work. You stay in the driver's seat for the API design and the data model. The output lands in your repo as code you can review before it ships.

A Git diff for a newly generated component

Frequently asked questions

What engineers usually ask before opening the editor.