DomainCraft
Turn one domain.yaml into a production backend
2 followers
Turn one domain.yaml into a production backend
2 followers
DomainCraft is a domain-driven code generator. Define your domain in a single domain.yaml and get a production-ready backend — CRUD, auth, permissions, migrations, admin — in any language, regenerated safely.
Free
Launch Team / Built With
Floot MCPBuild and ship web and mobile apps inside Claude or ChatGPT
Promoted
Hi Product Hunt! 👋 I'm Nikita, and I built DomainCraft out of two frustrations:
writing the same CRUD boilerplate for every project, and betting my product's core
on a platform I don't control.
DomainCraft is a different kind of code generator:
1. You get real code you own. One domain.yaml → a complete ASP.NET Core project: EF Core, PostgreSQL, JWT auth, validation, Docker, tests, admin panel. No hidden runtime, no lock-in — if we disappeared tomorrow, your code keeps working.
2. It survives Day 2. Scaffolders generate and run away. Here, generated code (*.g.cs) and your business logic are separate files. I added a stock-check rule (order 5 items, only 3 in stock → clean HTTP 400), regenerated — and my file was untouched.
3. The model is the single source of truth. Rename a field and DomainCraft renames the DB column instead of dropping it — your data stays intact. Same for entities, and it even rewrites references in your custom code.
4. Language-agnostic core, "dumb" bridges. The smart part — parsing your domain, resolving relations, the query grammar (filter/sort/pagination), validation rules, permissions — lives once in the language-agnostic core. A bridge is just a thin serializer that prints it in your language's syntax. .NET is simply the first bridge; a Python, TypeScript, or Go bridge reuses the same brain instead of re-implementing it.
5. Every bridge is certified, not just generated. A hand-written compliance suite (100+ automated checks against the running generated app) verifies each bridge implements the contract — permissions, validation, optimistic locking, seed data, the exact HTTP behavior. It's written independently of the generator, so a bridge bug can't silently pass; if it's green, you can trust the output.
Honest scope note: today the production-ready bridge generates .NET (ASP.NET Core + EF Core + PostgreSQL). The core and the bridge system are fully agnostic and pluggable, so more languages are on the roadmap.
How to try it — pick any of three:
1. In the browser: the free studio (WASM) composes and validates your
domain.yaml visually, with two-way sync — no install. Note: it covers the
model; generation runs on your machine.
2. Install the CLI in one command: go install
github.com/DomainCraft/DomainCraft/cmd/domaincraft@latest
3. No Go installed? Grab a prebuilt binary from GitHub Releases:
https://github.com/DomainCraft/D...
Everything is free and open source (MIT): the core, the C# bridge, the admin
bridge, the studio, and the compliance test suite.
🔗 Site: https://domaincraft.github.io/do... · GitHub:
https://github.com/DomainCraft/D... · Studio:
https://domaincraft.github.io/do...
I'd love your feedback — especially from .NET devs and anyone who's been burned by
scaffolders before. What stack would you want a bridge for next?