Try local auth in about a minute

Start a project-local Zitadel runtime, scaffold a Next.js auth flow, and prove registration and login in your browser before touching Cloud or a dashboard.

Local preview quickstart

Run these in your app, then open /login.

$npx @zitadel/cli@alpha doctor

$npx @zitadel/cli@alpha start

$npx @zitadel/cli@alpha setup --framework next --server local

$npm run dev

Alpha setup paths

Next.js, React, Vue, Angular, Nuxt, Spring Boot, Django, Laravel, Go, Rails, .NET - broader framework support comes later.

How it works

From empty directory to browser proof

This preview is local-first. Cloud setup, claim, and production handoff are coming later.

1. Check your environment and start local Zitadel

Run npx @zitadel/cli@alpha doctor, then npx @zitadel/cli@alpha start. The runtime stays project-local in .zitadel/local, including metadata and data files.

$npx @zitadel/cli@alpha doctor

$npx @zitadel/cli@alpha start

Local Zitadel runtime is ready.

(server: localhost:8080)

2. Wire the app

Run npx @zitadel/cli@alpha setup --framework next --server local. Next.js is the golden path today, with React, Vue, Angular, and Nuxt adapters available as alpha setup paths.

~ % npx @zitadel/cli@alpha setup --framework next --server local

╭──────────────────────Zitadel is ready────────────────────────╮
││
│ DETECTED │
│✓ Framework Next.js 16.2.9 · TypeScript · npm│
││
│ INSTALLED │
│✓ Package @zitadel/sdk-next → package.json│
│✓ Login page app/login/page.tsx│
│✓ Register page app/register/page.tsx│
│✓ Profile page app/profile/page.tsx│
│✓ Request proxy proxy.ts│
│✓ Env vars .env.local│
││
│ PROJECT │
│✓ Project id proj_01KV511FDJTW0TFAZMQBFNJSE3│
│✓ Server http://localhost:8080│
│✓ App will run http://localhost:3000│
││
│ Start your project: │
│ npm run dev (then open http://localhost:3000/login) │
││
╰──────────────────────────────────────────────────────────────╯

3. Prove it in the browser

Start the app with npm run dev, open /login, register, log out, and log in again. Username/password and passkeys work in the local preview.

localhost:3000/register

No users yet — you'll be the first. Register to test your auth flow.

Create your account

• Email
• Password

Register

Already have an account? Log in

What's included

What is actually in this preview

This alpha is intentionally narrow: a runnable local runtime, a Next.js-first setup flow, early framework adapters, and browser-verifiable authentication.

Available in this release

Local runtime

Spin up a full Zitadel instance on your machine: no Docker, no source checkout, no Cloud account.

Framework setup

One CLI command wires auth into Next.js, React, Vue, Angular, or Nuxt apps.

CLI

doctor, start, setup, stop, and reset manage the local runtime; add --json to script or automate any of them.

Password and passkey auth

Register, log out, and log back in through the generated /login flow.

User schemas

Define how your users look so identity management adapts to your use case, not the other way around.

Coming next

• Auth standards: OIDC hardening and SAML support for connecting existing enterprise stacks.
• Identity providers: Sign in with social and enterprise identity providers instead of only password and passkey.
• Custom templates: Restyle login screens and emails with LiquidJS templates instead of the generated defaults.
• Flow files: Author flow and action configuration locally alongside the rest of your setup.
• Broader stacks: Spring Boot, Django, Laravel, Go, Rails, and .NET join the current framework adapters.
• Agent delegation: Delegated auth flows for human, machine, and AI agent use cases.

See exactly what ships in this release and what's on deck Read the full announcement →

Cloud handoff

Local first now, managed path next.

The current preview does not connect to Zitadel Cloud and does not include a claim command. Join the waitlist if you want to test Cloud setup, ownership handoff, and production workflows as they land.

Does the local preview hold up?

We built this for the community to test. It is deliberately early: local runtime, framework setup, passkeys, username/password, and user schemas. Cloud claim, auth standards, identity providers, custom templates, flow files, broader stacks, and agent delegation are coming next.