Ship fast. Stay neat.
Sign-in, teams, billing, a design system, strict code rules and a production setup are already done. You and your AI assistant build the product; the guardrails keep the code clean.
- One-time payment
- Private GitHub repository
- All future updates
- UI components
- 70
- icons
- 466
- custom lint rules
- 17
- automated tests
- 2,500+
From Friday night to your first payment
Sign-in, teams, billing and the design system are already built, so your weekend goes into your product.
- Friday, 7 pmClone the repository. The app runs on your machine.
- Friday, 9 pmSign-in works, with Google and two-step verification.
- Saturday, 10 amYour team joins its own workspace.
- Saturday, 4 pmYour first feature fills the screen.
- Sunday, 11 amPress ⌘K: every action is one shortcut away.
- Sunday, 8 pmYour first customer pays.
- Friday evening
- Saturday
- Sunday
The app is the easy part
An AI assistant can write your features in a weekend. What slows you down is everything around them: sign-in, billing, security, and code that slowly turns into a mess.
The problem
Sign-in, teams and invitations take weeks to get right.
With Neatship
Clerk handles sign-in, Google sign-in, two-step verification, teams and invitations. It's already wired in.
The problem
Billing is full of edge cases: renewals, cancellations, failed payments.
With Neatship
Stripe subscriptions, the customer portal and signed webhooks are connected, and access follows what Stripe confirms.
The problem
AI-written code drifts into a mess, one shortcut at a time.
With Neatship
Your assistant follows a written rulebook and checks its own work with yarn verify; 17 lint rules and strict TypeScript block what slips through.
Built for AI-assisted coding
Your assistant reads the rulebook before it writes a line, and checks its own work with yarn verify before it says it's done. CI blocks whatever still slips through, before it is merged.
A rulebook your assistant reads
Conventions for code, design and security live in docs/conventions, and AGENTS.md and CLAUDE.md point to them. Assistants that read these files follow them on their own.
Checks that block what slips through
17 custom lint rules, strict TypeScript and more than 2,500 tests. One command, yarn verify, runs the checks a change needs; in Claude Code, hooks make the assistant run them.
Errors that explain the fix
Each rule says what to change and why, so your assistant can correct its own code.
What's done for you
Everything a SaaS needs before its first feature, built to the same standard and documented.
Sign-in and teams
Email and Google sign-in, two-step verification, and teams with roles and invitations, powered by Clerk.
Payments
Stripe subscriptions, monthly or yearly, a customer portal and verified webhooks. Disputes and refunds alert you. The example plans live in one file.
AI guardrails
A rulebook your assistant reads automatically, 17 custom lint rules, strict TypeScript, and yarn verify to check its own work.
Design system
70 components, 466 icons, light and dark mode, and a ⌘K command menu with keyboard shortcuts.
English and French
Every screen is translated with Lingui. Add more languages when you need them.
Secure by default
Every API endpoint declares who can call it, each customer's data stays in its own workspace, and sensitive actions are rate-limited.
Tested and checked
More than 2,500 automated tests, plus type and lint checks that run in CI on every pull request.
Landing page included
This page comes with it: prerendered for search engines, in two languages, ready to make your own.
Ready for production
One server with Docker: automatic HTTPS, nightly backups, logs and error alerts. One checklist takes you live.
A complete stack, already wired together
Every piece is chosen, connected and documented, so you don't spend a week comparing tools.
- React 19
- TypeScript
- Vite
- Linaria
- Jotai
- Apollo Client
- GraphQL
- NestJS
- PostgreSQL
- TypeORM
- Redis
- BullMQ
- Clerk
- Stripe
- Docker
- Caddy
- Sentry
- Nx
- oxlint
- oxfmt
- Jest
- Vitest
- Playwright
Frontend
Fast builds, typed data and styles that cost nothing at runtime.
React 19, TypeScript, Vite, Linaria, Jotai, Apollo Client, GraphQL
Backend
A structured API, a relational database and background jobs.
NestJS, GraphQL, PostgreSQL, TypeORM, Redis, BullMQ
Services
Sign-in and payments run on specialists; production runs on containers, with automatic HTTPS and error alerts.
Clerk, Stripe, Docker, Caddy, Sentry
Tooling
One repository, fast checks and tests at every level.
Nx, oxlint, oxfmt, Jest, Vitest, Playwright
From purchase to your first feature
No setup call and no configuration marathon. Four steps and you're building.
Buy Neatship
Pay once. There is no subscription.
Get access on GitHub
You receive an invitation to the private repository, where every update lands.
Run two commands
The first starts the database and services in Docker, the second runs the app on your machine.
yarn setupyarn startBuild and deploy
Build your product with your AI assistant, then put it on your server with Docker, following the deploy guide and its checklist.
Pay once. Keep every update.
One payment gives you the full source code and every future update, for as many projects as you like.
What you get
- Full source code
- Unlimited projects
- All future updates
- Private GitHub repository
- Sign-in, teams and billing already wired
- Ready for production: HTTPS, backups, alerts
- Design system with 70 components
- 17 custom lint rules and 2,500+ tests
Frequently asked questions
Can't find your answer? Write to us
Do I need to be a developer?
You need to be comfortable running a few commands in a terminal. Your AI assistant does most of the typing, and the rules and checks keep the code clean.
Which AI assistants work with it?
Tools that read AGENTS.md or CLAUDE.md, such as Claude Code, Codex or Cursor. These files point your assistant to the rulebook and tell it to run yarn verify before it says it's done; in Claude Code, hooks make sure it does.
Is it ready for production?
Yes. Rate limits, nightly backups, logs, error alerts, security headers and automatic HTTPS are built in. Follow the deploy guide, then the checklist "Before your first real customer": your production keys, your domains, Clerk's production instance and its bot protection, Stripe in live mode, backups copied off the server.
What else will I pay for?
Clerk is free up to 50,000 monthly users, Stripe charges a fee per transaction, and you pay for your own hosting. Check their websites for current prices.
How do I get the code?
After payment, you receive an invitation to the private GitHub repository. Accept it and clone the repository. Then type /start-here in Claude Code: it explains the project and sets it up with you. Or follow the getting started guide.
Can I build several apps?
Yes, as many as you like, for yourself or for your clients. The license only forbids reselling or sharing the starter itself.
Do I get updates?
Yes. Updates land in the private repository, and you pull them into your projects when you choose.
Can I change the stack?
Yes, it's your code. The rulebook explains every convention, so you and your assistant know what each part expects before you change it.
Start your next app from a clean base
Pay once and get the full source code, with every future update.