Loading…
Loading…
Enterprise architecture teams design systems that development teams rebuild from scratch, introducing drift within weeks. Archiet uses your ArchiMate model, TOGAF deliverables, and EA documentation as the source of truth for code generation — the architecture is the specification, and the code is the proof.
Enterprise architecture engagements produce high-quality ArchiMate models, TOGAF Architecture Definition Documents, and Architecture Decision Records — and then watch development teams ignore them. The architecture is 'too abstract.' The developers start from a framework template and build toward the architecture retrospectively, if at all. Archiet changes this by making the EA model executable: upload the ArchiMate model and receive a running application whose module structure, data model, and security controls match the architecture. The architecture IS the specification.
Archiet implements a formal Model-to-Text (M2T) transformation from ArchiMate 3.2 elements to code constructs. Business Layer: BusinessProcess → service class, BusinessRole → RBAC role, BusinessObject → domain model. Application Layer: ApplicationComponent → module/controller, ApplicationService → API endpoint, DataObject → ORM entity. Technology Layer: TechnologyService → infrastructure service (database, cache, queue), Node → deployment target, Artifact → generated file. Relationship types drive structure: Serving → API dependency, Realization → interface implementation, Assignment → component ownership, Composition → nested structure.
The Archiet governance pack generates TOGAF-aligned deliverables from the ArchiMate model: Architecture Definition Document (ADD) from the genome structure, Architecture Requirements Specification (ARS) from extracted requirements, Architecture Roadmap from the capability gaps, and Statement of Architecture Work (SAW) from the generation configuration. These are not templates filled with placeholder text — they reference specific elements from your architecture model with traceability to the generated code.
Enterprise architecture already encodes the information needed for compliance documentation. Application boundaries define audit scope. Data classifications define PHI/PII/financial data handling. Security services define controls. The Archiet compliance layer reads these from the ArchiMate model and generates: SOC 2 Trust Services Criteria mapping, ISO 27001 Annex A control mapping, EU AI Act risk classification for high-risk AI systems, and data flow diagrams required under GDPR Article 30. What used to require a parallel compliance engagement is derived from the architecture in the same generation pass.
Enterprise architecture increasingly includes AI-enabled workflows — and enterprise governance teams increasingly require those agents to be auditable. If your EA model includes approval workflows, routing decisions, or policy-governed processes, Archiet generates governed AI agents (BPMN + DMN + bounded LLM) that satisfy EU AI Act Article 9 (risk management) and Article 14 (human oversight) requirements. The agent architecture is derived from the formal model, not prompt-engineered — every decision is traceable to a named policy rule.
Yes. Export from Enterprise Architect as ArchiMate Exchange Format (.xml) and import into Archiet. The element types, property definitions, and relationships are preserved in the transformation. Archiet's /vs/sparx-ea page covers the integration in detail.
No. Archiet is a code generation layer that consumes the output of EA tools. BiZZdesign, Archi, Enterprise Architect, and iServer produce the architecture models; Archiet transforms those models into production code and compliance documentation. The tools are complementary, not competitive.
The ArchiMate importer maps standard ArchiMate 3.2 elements to code constructs. Proprietary extensions (custom element types or relationship labels) are preserved in the genome's _custom_elements field and documented in the generated ARCHITECTURE.md, but do not drive code generation unless they map to standard ArchiMate types. The generation is based on the OMG standard, not vendor-specific extensions.
Enterprise application development typically costs £500–£2,000 per day per developer. Archiet generates the foundation (auth, tenancy, compliance, architecture documentation) that takes a team 4–8 weeks to build by hand. At a 5-developer team × 6 weeks × £750/day, the saving is £22,500–£45,000 per project — before counting the ongoing benefit of architecture-code traceability for maintenance and audit.
Describe your product once. Archiet generates a complete Flask + Next.js application — auth with httpOnly cookies, RBAC, multi-tenant workspace isolation, Alembic migrations, Celery workers, and a full OpenAPI 3.1 spec — without writing a single line of boilerplate.
Upload your product requirements document and Archiet generates a NestJS application with JWT authentication guards, TypeORM entities and migrations, workspace-scoped multi-tenancy, Swagger/OpenAPI 3.1 documentation, and a typed API client for your Next.js frontend — zero boilerplate written by hand.
Describe your product requirements and Archiet generates a complete FastAPI + Next.js application: Pydantic v2 request/response models, SQLAlchemy 2 ORM with async support, Alembic migrations, JWT auth, workspace isolation, Celery workers, and auto-generated OpenAPI 3.1 documentation.
free plan. No credit card required. Generate your first compliant architecture blueprint in under 10 minutes.