Describe
Explain the business, actors, rules, and constraints in language your team already uses.
Private alpha
Your business idea,
forged into software.
DomainAnvil turns plain-language requirements into a validated domain, validated architecture, API contracts, and runnable source for supported project shapes.
◈ Requirements-first◈ Traceable◈ Your source code
BUSINESS REQUIREMENT
A marketplace where fleet owners list vehicles and customers book available dates without overlaps.
01UNDERSTANDcomplete
02VALIDATEcomplete
03GENERATEcomplete
↳ domain/entities.ts↳ contracts/openapi.json↳ migrations/001_init.sql↳ deployment/docker-compose.ymlALPHA / 01
The forge opens soon.
Join the first builders shaping a more rigorous way to create software.
--days
--hours
--minutes
--seconds
PROCESS / 02From intent to implementation.
From intent to implementation.
One continuous system.
Clarify
The Studio asks only the questions needed to resolve meaningful ambiguity.
Compile
Every requirement passes validation before architecture and code generation.
Own it
Download source with contracts, migrations, deployment, and an evidence trail.
OUTPUT / 03
More than generated code.
A coherent software system whose parts agree with each other.
domain/contracts/services/migrations/deployment/evidence/
6 ARTIFACT CLASSES
Domain model
Entities, relationships, invariants, permissions, and business rules.
API contracts
Typed endpoints and OpenAPI definitions grounded in the same specification.
Runnable backend
TypeScript/Fastify or Go/Chi services on PostgreSQL, with migrations and tests.
Architecture
A modular monolith or microservices topology with explicit event routes.
Deployment
Docker and Kubernetes assets for AWS EKS, Azure AKS, GCP GKE, or a generic cluster.
Evidence trail
Traceability from each requirement to the generated implementation.
EXAMPLE FILE PATHS
EVIDENCE / 04
Every requirement, traceable to the line that holds it.
Pick one. Follow it from the sentence you wrote to the test that keeps it true. EXAMPLE RUN
- 01 · REQUIREMENT
A vehicle is owned by exactly one fleet owner account.
- 02 · RULE
exclusiveVehicleOwnership
- 03 · IMPLEMENTED IN
domain/entities.ts:14migrations/001_init.sql:22
- 04 · HELD BY
tests/vehicle.ownership.spec.ts
REFUSAL / 05
When it cannot be built, you are told.
A generator that always produces something will sometimes produce something wrong and say nothing. Where no supported operation can express a requirement, DomainAnvil declines it by name and explains what it would take.
- No silent stub in place of the behaviour.
- No invented integration that compiles and does nothing.
- No approximation presented as the requirement you wrote.
Two honest outcomes. When every capability has an executable handler and every required rule has an enforcement strategy, the result is marked implementable. When a business decision, a handler or an enforcement strategy is still missing, it is marked a validated application scaffold: it compiles and gives you a starting point, and each unresolved item is listed with a stable identifier instead of being quietly filled in. Neither is a claim that the output is ready for production.
VALIDATION REPORTEXAMPLE
AS WRITTEN ● DECLINED · REQ-037
When a booking is confirmed, run our in-house pricing model on the on-premise GPU cluster and write the result back before the customer sees the confirmation.
WHY IT WAS DECLINED
No supported operation can call external on-premise compute inside a synchronous confirmation path. Generating one would mean inventing a network contract, a timeout policy, and a failure mode that you did not specify.
THREE WAYS FORWARD
- A · SUPPORTED
- Make pricing asynchronous. The generated system emits booking.confirmed and applies the price when your service answers.
- B · SUPPORTED
- Keep the confirmation path generated and implement the pricing call yourself against the generated contract. The trace records the boundary.
- C · NARROW IT
- Restate the requirement so pricing is a value the system stores rather than a computation it performs.
Example run — 40 of 41 requirements generated1 declined · 0 approximated
SCOPE / 06
What the alpha does today.
The current capabilities, and the limits that come with them.
Check a shape before you request access
● SUPPORTEDTypeScript / Fastify with modular monolith is generated today, end to end.
Available now
- Describe your system in plain language — no modelling notation to learn.
- Clarifying questions, asked only where the description leaves something genuinely undetermined.
- A validated specification: the pipeline refuses to generate from one that does not hold together.
- Backend targets: TypeScript/Fastify/PostgreSQL and Go/Chi/PostgreSQL.
- Architecture options: modular monolith or microservices.
- Docker images, database migrations, OpenAPI contracts, generated tests, and Kubernetes manifests.
- Download the full source. It is yours, with no runtime dependency on us.
Current limitations
- Private alpha
- Access is by invitation while we work directly with each early builder. Requesting access does not create an account.
- Supported shapes only
- Generation covers the targets, architectures, and deployment targets listed above. Anything outside them is not generated.
- Some requirements are declined
- Where no supported operation can express a requirement, the pipeline says so instead of inventing an approximation.
- Engineering review required
- Generated applications are a reviewed starting point, not a production deployment. Read the code before you ship it.
- Staged analysis is experimental
- The staged analyzer is still under evaluation. The legacy pipeline remains the default.
EARLY ACCESS / 07Bring the idea.
Bring the idea.
Leave with the system.
Places are limited while we work directly with every early builder. Questions or a deletion request: admin@domainanvil.com.
Already invited?