Now in beta

Start with architecture.
Not boilerplate.

Build the product with AI. RepoWerk gives developers and small teams production-ready architectures for web, mobile or both, with the context your coding agent needs to keep building in the right places.

Start with GitHub Explore the catalog

Web + mobileNext.js and Flutter

< 1 minfrom choice to repository

01 · Where RepoWerk fits

The layer between a GitHub template and your AI agent.

A template gives you files. An agent writes code. Neither decides the architecture. RepoWerk does it once, correctly, in a form your agent can continue.

01
GitHub template
An empty structure. Every decision is still yours to make.
02
RepoWerk
Architecture, domain and conventions already decided and documented.
03
AI coding agent
Builds the product on top, without inventing the foundations.

What your agent reads

AGENTS.mdCommands and rules for the agent
ARCHITECTURE.mdApps, packages and main flows
PRODUCT.mdDomain, roles and workflows
DATABASE.mdTables, relations and RLS policies
API.mdContract, endpoints and generated clients
CONVENTIONS.mdNaming, patterns and where things go

The full set ships with the launch templates. Repositories created today include AGENTS.md or CLAUDE.md.

02 · Why RepoWerk

Four things no other starter combines.

Flutter, production-ready

Not a UI kit: the base for a commercial iOS and Android app. Riverpod, GoRouter, Supabase, auth, subscriptions, push, deep links, crash reporting, i18n, CI/CD and store setup.

Web and mobile, one contract

Next.js and Flutter in one monorepo. Database, API, auth, permissions and billing state are defined once, and the Dart clients are generated from the contract.

Product first, stack second

Start from what you want to build. Product templates ship the domain: data model, workflows, permissions and the edge cases that take weeks to get right.

Agent-ready by design

Every repository documents its own architecture, so Claude Code, Codex or Cursor add features in the right places instead of inventing the structure.

03 · What do you want to build?

Start from the product. Then pick the stack.

The launch catalog: three foundations and the first product templates. Templates in development take sign-ups, so we build the most requested first.

Foundations

Stack, structure and toolchain at production quality.

Foundations

Next.js SaaS Foundation

Available

The web foundation: auth, Postgres, dashboard and API routes on Next.js and Supabase. Also the base reused by the web product templates.

Next.js 16SupabaseTailwind CSSTypeScript

What's inside

Supabase auth and route protection
Dashboard layout with sidebar
Server and browser Supabase clients

Foundations

Flutter Production App

Available

The base for a commercial iOS and Android app, not a UI kit.

FlutterRiverpodGoRouterSupabaseRevenueCat

What's inside

Riverpod and GoRouter
Supabase auth and storage
Push notifications and deep links

Foundations

Next.js + Flutter Monorepo

Available

Next.js web and admin apps plus a Flutter app, sharing one product contract instead of UI code.

Next.jsFlutterSupabaseOpenAPI

What's inside

Web and admin in Next.js, mobile in Flutter
OpenAPI contract with generated Dart clients
Shared database types and domain schemas

Product templates

A complete product domain, ready to extend.

Product templates

Consumer Subscription App

Available

A consumer mobile app with paid subscriptions, from paywall to entitlements.

FlutterRevenueCatSupabase

What's inside

RevenueCat paywall and entitlements
Free trials and restore purchases
Onboarding flow

Product templates

Booking Platform

Coming soon

A booking product with the domain already in place: availability, slots, payments and the edge cases.

Next.jsSupabaseStripe

What's inside

Providers, services, locations and working hours
Availability, slots and time zones
Rescheduling, cancellations and refunds

Explore the full catalog

04 · Workflow

Three steps.
From product to first feature.

A short, predictable path from the idea to an agent building on a sound base.

Choose what to build

Pick a product template or a foundation. The stack comes second.

Create the repository

Web, mobile or both. Name it and RepoWerk creates it on your GitHub.

Build with your agent

Clone it and ask Claude Code, Codex or Cursor for the next feature.

05 · FAQ

Questions, answered.

Why not just ask Claude to generate a boilerplate?

An agent will happily generate one, and make different architectural choices every time. RepoWerk starts from decisions that are already made and tested, and documents them so the agent spends its effort on your product instead of the foundations.

Is RepoWerk a no-code tool?

No. You get real code in your own repository and you stay in control of it. RepoWerk is for people who want to own the code without rebuilding the same infrastructure for every project.

Why Flutter and not React Native?

Flutter production apps are the least served part of the market, and one Flutter codebase covers iOS and Android with a consistent UI. Web and mobile share a product contract (database, API, permissions) rather than UI code.

When will the templates marked coming soon be ready?

We build them in order of demand. Leave your email on a template in the catalog and we'll write to you once, when it's available.

What does RepoWerk need access to on GitHub?

RepoWerk uses a GitHub App with only the permissions required to create a repository and push the initial files: repository administration, contents and metadata.

Who owns the generated code?

You do. The repository lives on your GitHub account or organization, and you can keep working on it with or without RepoWerk.

Can I use RepoWerk with my team or agency?

Yes. Create a workspace, link your GitHub organization and new projects are created there, shared with the members of the workspace.