What gets generated for the Next.js frontend
App Router pages (Next.js 14+)
- Auth pages: login, register, forgot password, reset password, verify email
- Onboarding flow (multi-step, configurable)
- Dashboard shell with navigation
- Settings: profile, workspace, billing, notifications, integrations
- One list page + one detail/edit page per entity in your PRD
- Pricing page (wired to your Stripe plans if billing is in the genome)
- Error pages: 404, 500, maintenance mode
Middleware and route protection
middleware.tsguards all/dashboard/**and/app/**routes- Redirects unauthenticated users to
/login?next=... - Redirects unverified users to the verify-email page
- Role-based UI rendering (admin-only sections)
Typed API client
- Auto-generated client matching the OpenAPI 3.1 spec from the backend
- Type-safe request/response objects — no manual fetch calls
- Error handling: 401 → redirect to login, 403 → permission error UI, 422 → form validation errors surfaced correctly
UI components
- Tailwind CSS + shadcn/ui component library
- Dark/light mode with
next-themes - Toast notifications for async operations
- Loading states and skeleton screens on data-fetching routes
- Responsive layout: works on mobile, tablet, and desktop
Auth in the frontend (security-correct by default)
- JWT stored in httpOnly cookies — never
localStorage.setItemorsessionStorage - No token in the URL, no token in
window.* - CSRF protection on state-changing requests
The backend that ships with it
Archiet generates the Next.js frontend alongside a complete backend in your chosen stack:
| Backend | What you get | |---|---| | Flask (Python) | SQLAlchemy models, Alembic migrations, Blueprint routes, Celery tasks | | FastAPI (Python) | Async SQLAlchemy, Pydantic schemas, native OpenAPI docs | | Django (Python) | Django ORM, REST Framework, built-in admin | | NestJS (TypeScript) | TypeORM, guards, decorators, Swagger | | Laravel (PHP) | Eloquent ORM, Artisan, Laravel Sanctum auth | | Go + Chi | GORM, middleware, clean architecture | | Java Spring Boot | JPA, Spring Security, Maven |
The Next.js frontend's API client is generated to match the backend's routes exactly.
vs next-create-app and open-source boilerplates
create-next-app and popular boilerplates (create-t3-app, next-enterprise, Taxonomy, Precedent) solve the framework setup problem. They're excellent starting points for the Next.js-specific configuration.
The difference: they're generic. They give you a working Next.js setup; you still build every page, every data model, every API route for your specific product.
Archiet generates the product-specific parts: your entities, your pages, your API, your integrations, your documentation. The Next.js configuration is just part of the output.
| What you need | create-next-app / t3 | Archiet | |---|---|---| | Next.js App Router setup | Yes | Yes | | Tailwind + shadcn/ui | Yes (with t3/similar) | Yes | | Your specific data models | You write them | Generated from your PRD | | Your API routes | You write them | Generated, matching OpenAPI spec | | Auth (really working, not just a demo) | Demo-level or you integrate an auth service | Full auth: JWT, password reset, email verify, route guards | | Stripe billing wired to your pricing | You write it | Generated when billing is in your genome | | Mobile app | No | React Native (Expo) generated alongside | | Architecture documentation | None | ADRs, traceability matrix, security posture | | Time to working app | Days to weeks | 90 seconds |
CTA
Generate a complete Next.js full-stack application from your requirements — free plan, no credit card.
Upload your PRD or describe your product, pick Next.js + your chosen backend, and have a working application in 90 seconds.
Start free at archiet.com.