The Next.js starter kit for internal tools, built for agentic coding.
Structured so coding agents always know where the next feature goes.
Clients, roles, filters, comments, uploads, permissions, already structured.
Why Straktur exists
Extracted from a working company
AI coding agents write features fast. They don't hold an architecture together. Past a certain size, the agent forgets how the schema fits, patches auth in three different styles, and every new screen drifts a little further from the last one. You stop shipping features and start debugging structure.
Straktur is the codebase behind the internal tools at Mroomy. You buy the same code we run the company on, extracted and documented, with a public changelog.
- 7+ years
- running the company on its own internal tools
- 3 systems
- order management, product catalog, project tracking
- 2 years
- of development done almost entirely by AI agents
How it works
From zero to a working internal tool in three steps.
Clone and run
A complete project with auth, database, 100+ UI components, and a working reference feature. About five minutes to run locally, two with Docker.
Describe your feature
Tell your agent what to build. It reads CLAUDE.md and .cursorrules, studies the reference feature, and follows the same pattern instead of inventing a new one.
Review and ship
Ask the agent to check its own work against Straktur's golden rules. Files land where the reference feature put them: feature module, router, pages. Filters, search, and views match the screens that came before.
What people build with it
If it's a back-office tool with tables, roles, and a database behind it, it fits.
Order management
statuses, deadlines, files, and full history per order
Mini-CRMs and client portals
contacts, activities, notes, and role-based access
Inventory and warehouse tools
stock levels, suppliers, and movement history
Product catalogs (PIM)
attributes, variants, images, and exports
Project trackers
stages, owners, deadlines, and files in one place
Ops dashboards
stat cards, charts, and activity feeds from your own data
See what you're buying
The documentation is public, so you can check the architecture before you pay. This is the shape of the codebase you get.
src/
├── app/
│ ├── (auth)/ login, register, reset
│ ├── (dashboard)/ your app lives here
│ │ └── examples/clients/ list · detail · create
│ └── api/rpc/ single oRPC endpoint
├── features/
│ ├── examples/clients/ golden-path reference
│ │ ├── queries.ts database reads
│ │ ├── actions.ts database writes
│ │ ├── validation.ts zod schemas
│ │ └── ui/ feature components
│ ├── organizations/
│ ├── invitations/
│ └── users/
├── server/routers/ API layer
├── components/
│ ├── data-table/ server-side tables
│ ├── detail-page/ detail layouts
│ └── inline-edit/ editable fields
└── lib/
├── auth/ Better Auth + RBAC
├── db/schema/ Drizzle + Postgres
└── storage/ S3 · R2 · SupabaseFeature-first: everything for a feature lives in one place, and the examples/ directory is the pattern agents copy.
- Multi-tenancyorganizations, invitations, role-based access (owner, admin, member, viewer)
- DataTableserver-side sorting, filtering, pagination, bulk actions, and export
- CRUD building blocksdetail pages, side-panel forms, inline editing
- File storagepresigned URLs for AWS S3, Cloudflare R2, or Supabase Storage
- EmailReact Email templates with Resend, SMTP, or console in development
- i18nnext-intl with ICU messages, English and Polish included
- Agent contextCLAUDE.md and .cursorrules, so agents know the rules before your first prompt
Fixed core, swappable edges
The core is rigid, so agents always know where things go. The edges are adapters, so you can change providers without rewriting features.
- Next.js 16 + React 19app framework, App Router
- TanStack Query + Tabledata fetching and tables
- oRPCone typed API endpoint
- Drizzle ORMschema and migrations
- PostgreSQLthe only database it needs
- AuthBetter AuthincludedClerkSupabase Auth
- File storageAWS S3Cloudflare R2Supabase Storage
- EmailResendSMTPconsole (dev)
- Postgres hostingSupabaseNeonRailwayself-hosted
- DeployVercelRailwayFly.ioDocker / VPS
A provider swap is an adapter change plus new environment variables.
What the alternatives cost
Three ways to get an internal tool built, and what each one costs.
List price for 15 builder seats and 150 end users on the Business plan. Check it at retool.com/pricing.
Before the first line of business logic. And AI without a pattern to copy builds every screen its own way.
Plus your own infrastructure (a managed Postgres and hosting, $10–30 a month) and your own build time. Straktur removes the setup, not the work.
Where no-code still wins: if nobody on your team is comfortable running a dev environment and driving coding agents, a drag-and-drop tool is the right call.
Who it's for, and who it isn't
A $499 purchase with no refunds deserves a straight answer on fit.
Straktur is for you if…
- You build with AI coding agents like Claude Code, Cursor, or Codex, and want them on rails instead of improvising.
- You've outgrown Airtable or shared spreadsheets and need a real database with roles and history.
- You're a freelancer or agency and want one repeatable foundation for client work.
- You want to own the code and stop paying per seat.
It's not for you if…
- You want no-code. If nobody on your team will run a dev environment and drive coding agents, stay with Retool or Airtable.
- You're building a public SaaS or a marketing site. ShipFast or Supastarter fit that better.
- You need SOC2, SAML, or Active Directory out of the box. Straktur doesn't have them.
- Your project is a someday side project. Bookmark this and come back when you have a real deadline.
From the founder
Marcin Perlak
Founder of Straktur & Mroomy
I built a software house to 200+ people and sold it. I started qcadoo, an open-source MES that still lives on GitHub with 500+ stars. For the last seven years I've been running Mroomy.
Two years ago I moved nearly all of our internal development to AI agents. At first it was fast. Then, past a certain size, every session started with re-explaining the app to the model, and every feature came back in a slightly different style. The models were fine. They had nothing to hold on to.
So we gave them structure: one way to fetch data, one way to write it, one reference feature to copy. That codebase became Straktur. My team and my agents work in it every day.
Agents still do something dumb from time to time, and I don't catch it by reading code. I don't read code at all. I ask the model whether what it just built follows Straktur's golden rules or is a weird hack, and because there's exactly one right pattern, that question gets a straight answer.
If you want that kind of boring reliability under your AI, Straktur is for you. If you have a question before buying, email me at hello@straktur.com. I answer every pre-sales email.
— Marcin
Choose your starting point
Buy the codebase only, or get founder-led onboarding to shorten the path to your first production use case.
Straktur Core
Everything you need to start building and shipping internal tools with your own team.
- Full Straktur source code
- Lifetime updates, every release forever
- Documentation and implementation guides
- Production-ready architecture for internal tools
- Use on unlimited projects, for your company or your clients
- No per-seat fees
Straktur Sprint
Ship your first internal tool fast, built live with Marcin over 2–3 weeks.
- Everything in Core
- 16 hours of co-build with Marcin (4 × 4h sessions)
- Sprint completed in 2–3 weeks
- The sessions build your real internal tool, from the first hour
- Architecture and stack decisions made together
- 30 days of priority email support after sprint
One-time purchase. No subscription. No per-user pricing. Lifetime updates included.
The same codebase runs Mroomy's order management, product catalog, and project tracking today.
It's source code, so there are no refunds. Read the FAQ and the docs first, or email hello@straktur.com with questions.
Frequently Asked Questions
Everything you need to know about Straktur and how it works.
