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.
Now in beta
Flutter, production-ready.
Web on the same contract.
Start your iOS, Android and web product from an architecture that already handles the hard parts: subscriptions, account deletion, row-level security and one API contract for Flutter and Next.js. Your AI coding agent builds features, not foundations.
01 · Where RepoWerk fits
The layer between a GitHub template and your AI agent.
A template gives you files. An agent writes code. Neither knows that subscription webhooks can arrive twice or out of order, or what the stores expect when a user deletes their account. RepoWerk ships those decisions, tested, 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 agentARCHITECTURE.mdApps, packages and main flowsPRODUCT.mdDomain, roles and workflowsDATABASE.mdTables, relations and RLS policiesAPI.mdContract, endpoints and generated clientsCONVENTIONS.mdNaming, patterns and where things go
Included in every Flutter and Next.js + Flutter repository.
02 · Why RepoWerk
Four things no other starter combines.
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.
The edge cases, already handled
Trials, grace periods and restore for subscriptions; account deletion that reaches every table; row-level security tested in the database. The parts that take weeks to get right, and that an agent tends to get wrong.
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 · The catalog
For products with an app and a web side.
Start from the Flutter app, add the Next.js web and admin on the same contract, or begin from a complete subscription app.
Flutter + web
iOS, Android and web on one contract. This is where RepoWerk focuses.
Foundations
Flutter Production App
AvailableThe 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
AvailableNext.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
Consumer Subscription App
AvailableA 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
Also available
Web starters built to the same standard.
Foundations
Next.js SaaS Foundation
AvailableThe 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
Product templates
Booking Platform
AvailableA 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
04 · WorkflowThree steps.
Three steps.
From product to first feature.
A short, predictable path from the idea to an agent building on a sound base.
01
Pick your starting point
The Flutter app, Flutter with web and admin, or a complete subscription app.
02
Create the repository
App, web or both. Name it and RepoWerk creates it on your GitHub.
03
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.
Do I need both the app and the web side?
No. Flutter Production App works on its own, with Supabase as the backend. Choose the Next.js + Flutter monorepo when the product also needs a website, a customer area or an admin: web and mobile then share one API contract.
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.
Build the app, not the setup.
Sign in with GitHub and create your Flutter or Next.js + Flutter repository in under a minute.