For the person who knows the business — not the framework
Describe your business.
Get a codebase that's correct by construction.
unfold turns a plain-language description of how your operation actually works into a working, maintainable software system — on one opinionated, proven architecture. You own the code. You never have to see the architecture.
No sign-in needed to try it — you'll get a downloadable codebase. Sign in with GitHub to push it straight to your own repo and iterate on it later.
We don't make the AI smart. We make the problem small — so a wrong answer is cheap to catch, and the code is verified three independent ways before you ever accept it.
Who it's for
You run something with rules that must always hold — where "this must never happen" actually matters. If you can explain it to a new hire in a paragraph, unfold can build it.
Bookings & ticketing
Sell seats, slots, or appointments — and never oversell a venue, even under a rush.
Inventory & fulfillment
Track stock, reservations, and orders without two customers claiming the last unit.
Subscriptions & billing
Plans, renewals, lapses, refunds — lifecycles that have to be auditable and consistent.
Scheduling & dispatch
Assign people, vehicles, or rooms against capacity and rules that can't be broken.
How it works
- 1
Describe it in your own words
Write a paragraph the way you'd explain the business to a new hire. No jargon, no diagrams.
- 2
unfold shows you a plain-language map
It reflects your business back as a simple map — the things you manage, what happens, the rules that must hold. You correct a draft instead of authoring from a blank page.
- 3
You confirm the few decisions that matter
A short stack of yes/no cards in your own words, each with a strong, pre-selected default and a plain reason. The architecture is never one of the questions — that part is dictated.
- 4
It builds a verified codebase into your repo
unfold scaffolds the system and a small local model fills the gaps — checked three ways (it compiles, it obeys every rule, the scenarios pass) before anything is accepted.
Why the code stays solid
One opinionated path
Domain-driven, event-sourced, vertically sliced .NET. By refusing breadth, correctness becomes mechanical — and the system can drive instead of just ask.
Rules are enforced, not hoped for
Every decision is compiled into types, analyzers, and tests that travel with the repo — so a later change (by you, a developer, or another AI) can't silently break it.
No lock-in, ever
The generated code references zero unfold packages and lives in your own git repository. Stop using unfold whenever you like and keep a clean, idiomatic codebase.
What unfold is not for
Being honest about the blast radius is part of the opinion. unfold refuses what it can't build correctly rather than mis-building it. It is not the right tool if:
- It's just a list of things (CRUD) with no real rules. A contact list, a simple form, a content site — a spreadsheet or a no-code form builder will serve you better and cost less. unfold's value only shows up when invariants matter.
- You want "any language, any architecture." There is exactly one path: .NET, domain-driven, event-sourced. unfold will not generate a React app, a Python service, or a database-first CRUD layer.
- You expect magic with no judgment. unfold proposes; you still confirm the handful of decisions only someone who knows the business can make. It makes a wrong answer cheap to catch — it does not remove the responsibility.
- You're a developer looking for a quick scaffold-and-go. You're welcome to use it, but it's built for the person who understands the operation, not the framework. If you want full control of every architectural choice, this isn't that.
If your need sits outside this, unfold tells you so up front — rather than hand you a confident, wrong system.
Have something with real rules to build?
Start by describing it. unfold will show you whether it's a fit.
No sign-in needed to try it. Currently in preview.