Blueprint vs prompt vs template
| Approach | What you get | Deployable? | |---|---|---| | Prompt → files (Bolt, Lovable) | Session-shaped codebase | Sometimes — review auth, migrations, secrets | | Static boilerplate (ShipFast, T3) | Generic starter | After weeks of customization | | Blueprint → genome → render (Archiet) | Product-specific production ZIP | Gated: quality ≥80, no placeholder secrets, shippability audit |
The three-step pipeline
1. Blueprint (architecture specification)
Describe entities, user stories, integrations, compliance overlays, and stack preference in the Blueprint Wizard. Output: a scored ArchiMate-aligned model you can review before codegen.
2. Genome (stack-agnostic IR)
The blueprint compiles to a genome — entities, capabilities, screens, NFRs, and integration contracts in a representation every stack renderer reads identically.
3. Deployable artifact
render_genome emits your target stack. delivery_gate blocks shipment if:
- Quality score below threshold
- Placeholder secrets (
change-me, etc.) anywhere in the ZIP - Missing required pages (auth flow, settings, onboarding)
- Tenant isolation or httpOnly auth patterns violated
Expected time from download to running stack: under 30 minutes with docker-compose up.
What "deployable" includes
Backend API # Your chosen stack — routes match openapi.yaml
Database # PostgreSQL + migrations (Alembic or equivalent)
Frontend # Next.js + shadcn — all screens from manifest
Mobile (optional) # Expo — App Store compliance files included
docker-compose.yml # Boots locally without manual wiring
openapi.yaml # Authoritative contract — frontend and tests align
docs/decisions/ # ADRs for every material technical choice
ARCHITECTURE.md # Headline architecture document
README.md # Setup with seeded admin credentials (one source of truth)
Who needs blueprint-to-code (not prompt-to-code)
- Agencies delivering the same archetype (CRM, marketplace, booking) on different stacks per client
- CTOs who need reproducible output for board or audit questions
- Enterprise architects bridging EA tooling and engineering delivery
CTA
Start with a blueprint, not a blank repo. archiet.com/register — free plan, no credit card.
FAQ
What is an Archiet blueprint?
A structured architecture specification: entities, relationships, screens, integrations, compliance flags, and stack selection — validated against ArchiMate 3.2 conventions before codegen.
Can I regenerate after editing the blueprint?
Yes. The genome is the contract. Edit the blueprint, regenerate — deterministic lowering produces an updated ZIP traceable to the new spec.
How is this different from a GitHub template?
Templates are generic. A blueprint encodes your product. The generated code is specific to your entities, auth model, billing rules, and compliance overlays.