A comprehensive, open-source framework for enterprise architects, solutions architects, and technology leaders. Built for practitioners — from CTO to developer.
Every agent, tool, and workflow defined declaratively through the metamodel — generated, not hand-coded. Business users work with structured definitions, not prompts.
Explore the MetamodelAuthentication, authorisation, audit trails, and assured execution — enforced at the model level, not bolted on after deployment. Zero Trust architecture baked into every agent.
Agent FoundryMeasured agent performance, governance audit trails, and rollback SLAs — all governed by the framework. Monitor, govern, and improve with metrics baked into every layer.
View MetricsSolution archetypes, sprint-by-sprint delivery templates, and IaC accelerators. Ship faster with governed patterns and reusable building blocks from the Solution Hub.
Solution HubTechNeHub Labs is an open ecosystem of frameworks, catalogs, methodologies, and tools for Digital Enterprise Architecture. It exists to serve the full spectrum of architecture practitioners — from Chief Architects setting standards to developers building on them.
Versioned repositories of Principles, Architecture Patterns, Standards, Reference Models, Metrics, and Glossaries — all structured against a common metamodel.
A versioned entity-relationship metamodel expressed in JSON Schema, OWL/RDF, SQLite, TypeScript, and Pydantic — machine-readable and tooling-friendly.
Generate targeted views of the architecture for CTO, Chief Architect, Solutions Architect, Business Architect, and Developer audiences.
Work in Excel/CSV, Markdown, SQLite, OWL/RDF — convert freely between formats and generate architecture artifacts: ADRs, component specs, API contracts.
Every entity in the framework links to others through typed relationships. The metamodel governs these links, ensuring consistency and traceability across the architecture.
From CTO conducting quarterly health reviews, to architects defining patterns, to developers generating component specs — the framework meets each practitioner where they are.
The DEA framework is organized into four layers, each building on the previous. Every layer references the canonical metamodel — the single source of truth for all entities.
The foundation. Defines every entity type, relationship, and attribute used across all other layers. Expressed in JSON Schema, OWL/RDF TTL, SQLite, TypeScript, and Pydantic.
Structured repositories of architectural knowledge. Each catalog is versioned against the metamodel, containing Principles, Patterns, Standards, Reference Models, Metrics, Ontologies, Taxonomies, Glossaries, DERA, DBSF, Agent Foundry, and Solution Hub.
Scripts and applications that consume the metamodel and catalogs to generate artifacts: architecture viewpoints, ADRs, component specs, API contracts, and glossary documents. Built in TypeScript, Python, and web technologies.
Cross-repo governance, contribution workflows, and the public documentation hub. Includes the DEA Roadmap project, PR templates, CODEOWNERS, contribution guidelines, and this GitHub Pages site.
Assessment tools and maturity models for architecture modernization, technology, operations and services delivery — your toolkit for evidence-based EA improvement.
Enterprise Architecture assessment instruments covering architecture modernization, technology, operations and services delivery. Each assessment captures baseline state, identifies gaps, and tracks improvement over time. Designed for self-assessment, facilitated workshops, and automated tooling integration.
View Repository L1 · Maturity ModelsMaturity model framework for assessing and advancing Enterprise Architecture capability across domains. Five-level progression from Ad Hoc to Optimising, with defined exit criteria per level.
View RepositoryEach repository is a self-contained unit of the framework. All catalog repos declare a version pin to the metamodel.
Canonical entity definitions, relationships, and schemas. JSON Schema, OWL/RDF TTL, SQLite runtime, TypeScript interfaces, Pydantic models.
Reusable architecture patterns: API Gateway, CQRS, Event Sourcing, Saga, Strangler Fig, and more — with forces, consequences, and applicability.
Reference architectures: Digital Platform, Integration Hub, Data Mesh, and domain-specific models at conceptual, logical, and physical abstraction levels.
EA KPIs and measurements: API adoption rates, capability maturity scores, technical debt ratios, and compliance metrics with thresholds and measurement methods.
Canonical delivery blueprint assembling all DEA framework layers into a practical adoption programme. Defines four sequential phases: Foundation, Catalog Seeding, Tooling Enablement, Governance.
Enterprise business service definitions, capability decompositions, and solution component mappings. Six domains: Customer, Finance, Product, Order, Supply Chain, HR — each with governance contracts and SLA tiers.
Autonomous agent patterns (ReAct, Plan-and-Execute, Supervisor-Worker, Debate, Reflect), agent platform specifications, multi-agent orchestration frameworks, and operational governance policies for enterprise AI.
Solution archetypes, sprint-by-sprint delivery templates, and implementation accelerators (IaC, docker-compose, Kong configs) for CDP, API Gateway, Event Streaming, Identity, Workflow, and Analytics Platform.
Digital Enterprise Reference Architecture (DERA) — canonical delivery blueprint assembling all L1 catalogs into a four-phase adoption programme: Foundation, Catalog Seeding, Tooling Enablement, Governance Activation.
Enterprise Architecture assessment instruments: architecture modernization, technology, operations and services delivery — self-assess, facilitate workshops, integrate with tooling.
EA capability maturity models — five-level progression from Ad Hoc to Optimising, with exit criteria per level. Evidence-based advancement tracking.
TypeScript CLI for the DEA ecosystem. Query catalogs, validate entries against the metamodel, generate stakeholder viewpoints, and produce ADRs and component specs.
React + Vite web UI for browsing DEA catalogs and visualizing viewpoints. Browse by entity type, filter by tag, and explore the relationship graph.
Python automation library: CSV ↔ SQLite ↔ YAML conversion, RDFLib validation against the metamodel TTL, viewpoint generation in Markdown and PlantUML formats.
Five active GitHub Projects tracking the full framework roadmap across Foundation Core, Catalog Ecosystem, Developer Tooling, Web Viewer & Packaging, and Governance & Standards.
The framework is designed to be tooling-friendly. Every artifact is machine-readable. Generate viewpoints, validate entries, and produce architecture documents — all from the CLI.
$ dea viewpoint -s SolutionsArchitect # ─── DEA Viewpoint — SolutionsArchitect ─── # Concern: Solution design and pattern selection Architecture Patterns (6): dea:pattern-api-gateway API Gateway dea:pattern-cqrs CQRS dea:pattern-event-sourcing Event Sourcing dea:pattern-saga Saga dea:pattern-strangler-fig Strangler Fig dea:pattern-circuit-breaker Circuit Breaker Solution Components (3): dea:component-api-gateway-svc dea:component-identity-svc dea:component-order-svc ✓ Viewpoint generated in 1.2s
Validate any catalog entry against the metamodel JSON Schemas. Catch structural errors before publishing.
dea validate ./catalogs --strict
Generate architecture artifacts from catalog entries: ADRs, component specs, API contracts, glossary entries.
dea generate -t adr -i dea:pattern-cqrs
Search and browse all catalogs by type, tag, or exact ID. Pipe output to other tools.
dea query --type Principle --tag api
The same catalog serves different audiences through viewpoint generation. Each role sees only the entities and relationships relevant to their concern.
Cross-domain coherence, standards compliance, and architecture governance across all solution layers.
Quarterly architecture health reviews, strategic alignment, technology radar, and investment prioritization.
Pattern selection, solution design, component decomposition, and integration architecture.
Business capability mapping, process alignment, and service orchestration across business domains.
Component specs, API contracts, integration patterns, and implementation hints for direct use.
The DEA framework grows through contribution. Whether you're adding patterns, refining principles, writing tooling, or improving documentation — every contribution shapes the framework.
Propose new patterns, principles, standards, or reference models via pull request. Each catalog has contribution guidelines and a PR template.
Read contribution guide →Ask questions, propose framework changes, and share how you're using the DEA framework in your organization via GitHub Discussions.
Join the conversation →Follow the DEA Roadmap project for sprint planning, backlog prioritization, and release milestones across all framework repositories.
View the roadmap →Watch repositories for changes. Star the repos you use most to track releases and major updates.
Browse all repos →