Enterprise Architecture models without vendor lock-in. Publish your ArchiMate models and explore, analyze and navigate them from a self-hosted web platform. Or skip the modeling tool — describe your system to an AI agent and let it build the model for you.
Built on ArchiMate · Powered by Go · PostgreSQL · Open Source
Live Demo · Getting Started · Features · How It Works · Roadmap · Contributing · Support
Try it: demo.archipulse.org — pre-loaded with ArchiSurance and ArchiMetal example models. One click, no sign-up required.
ArchiPulse is an open-source platform for storing, visualizing, navigating, and analyzing ArchiMate-based Enterprise Architecture models through a collaborative web platform.
Most EA tools today fall into one of two traps: too academic (OWL ontologies, Protégé, SPARQL) or too proprietary (vendor lock-in, closed formats, expensive licenses). ArchiPulse takes a different approach — it maps the ArchiMate Open Exchange Format (AOEF) directly to PostgreSQL tables, making the standard itself the data model.
The result: your architecture is not a static file but living, collaborative data — queryable, enrichable, versioned by baseline, and always exportable back to any AOEF-compliant tool.
ArchiPulse works alongside the tools architects already use — Archi, archimate-editor, or any AOEF-compatible tool. It adds the collaborative repository, the analytical layer, and the enrichment pipeline on top.
It also ships an MCP server (archipulse mcp) that lets any MCP-compatible AI agent — Claude, or others — operate the repository directly: create workspaces, model elements and relationships, query analytical views, and export AOEF, all through natural language. No file uploads, no manual modeling required.
- Features
- How It Works
- Screenshots
- Getting Started
- Supported Formats
- Architecture
- Roadmap
- Contributing
- Support
- License
Collaborative Repository
- AOEF-as-tables: the ArchiMate Open Exchange Format mapped directly to PostgreSQL — no custom metamodel
- Multiple architects edit the same workspace simultaneously — changes visible on refresh
- Optimistic locking prevents silent overwrites — conflicts shown with author and timestamp
- Semantic diff on AOEF upload — review element-by-element what changed and who changed it
- One workspace per baseline (
Q1-2026-AS-IS,Q1-2026-TO-BE,initiative-payment-modernization)
Viewer & Navigation
- Static viewer — faithful reproduction of ArchiMate views as designed
- EAM views — pre-defined analytical views (capability maps, application landscapes, technology radars) generated from SQL
- Graph explorer — interactive graph with visual filters for ad-hoc dependency analysis
Enrichment Pipeline
- Connect real-world resource catalogs (AWS, Confluence, Excel, custom sources) to your ArchiMate workspace
- Two-stage ETL: extractors collect raw data, mappers translate it to ArchiMate element types
- Mapping rules execute against the same CRUD API used by the web interface — no special internal paths
- Community-contributed extractor library — one extractor works across all organizations
Open & Integrable
- Import and export any workspace as valid AOEF XML — round-trip compatible with any AOEF-compliant tool
- Full REST API — every operation available programmatically
- Self-hosted — your data stays in your infrastructure
- Compatible with Archi, archimate-editor, BiZZdesign, Sparx EA, and any AOEF-compliant tool
CLI & AI Integration
archipulseCLI — manage workspaces, elements, relationships, diagrams, and import/export from the terminal- MCP server (
archipulse mcp) — connect ArchiPulse directly to Claude or any MCP-compatible AI agent; query models, run EAM views, and create or update elements through natural language
flowchart TD
Tools["ArchiMate editors\nArchi · archimate-editor · any AOEF tool"]
-->|"AOEF upload"| AP["ArchiPulse\nWorkspace Manager"]
AP --> PG[(PostgreSQL\nAOEF as tables)]
CLI["archipulse CLI\nimport · export · workspace · element"]
--> AP
AI["AI agents · Claude\narchipulse mcp"]
--> AP
Src["External sources\nAWS · Confluence · Excel"]
--> Ext["Extraction Engine\nExtractor → Mapper"]
--> AP
PG --> SV["Static viewer\nmodel as designed"]
PG --> EAM["EAM views\nSQL analytical queries"]
PG --> GE["Graph explorer\nCytoscape.js"]
PG -->|"AOEF export"| Tools
- Architects model in their preferred tool and upload AOEF to ArchiPulse
- ArchiPulse parses the model and stores it in PostgreSQL — one row per element, relationship, and diagram
- Multiple architects can edit the workspace directly via the web interface or API — all changes are immediately visible
- The enrichment pipeline pulls from external sources and maps resources to ArchiMate elements in the workspace
- The viewer renders static diagrams, generates EAM analytical views, and provides an interactive graph explorer
- Any workspace can be exported back to AOEF — importable into any compliant tool at any time
Demo video coming soon. In the meantime, try the live demo — one click, no sign-up required.
Application Dashboard — lifecycle and criticality breakdown across your application portfolio.
Application Landscape Map — applications mapped to business capabilities with overlay filters.
Application Dependency Graph — interactive graph of application integrations.
Capability Tree — hierarchical capability model with collapsible levels.
- Docker and Docker Compose — recommended
- Or: Go 1.24+, Node.js 22+, PostgreSQL 17+
git clone https://github.com/DisruptiveWorks/archipulse.git
cd archipulse
docker compose upThe web interface will be available at http://localhost:8080.
# Clone the repository
git clone https://github.com/DisruptiveWorks/archipulse.git
cd archipulse
# Build the frontend
cd cmd/archipulse/ui && npm install && npm run build && cd ../../..
# Configure environment
cp .env.example .env
# Edit .env — set DATABASE_URL
# Run database migrations
go run ./cmd/archipulse migrate
# Build and run
go build -o archipulse ./cmd/archipulse
./archipulse serve# Create a workspace
curl -X POST http://localhost:8080/api/v1/workspaces \
-H "Content-Type: application/json" \
-d '{"name": "Q1-2026-AS-IS", "purpose": "as-is"}'
# Import an ArchiMate model
curl -X POST http://localhost:8080/api/v1/workspaces/{id}/import \
-F "file=@examples/archisurance.xml"
# Open the viewer
open http://localhost:8080ArchiPulse ships with the ArchiSurance example model from The Open Group so you can explore the viewer immediately.
| Format | Import | Export | Notes |
|---|---|---|---|
| ArchiMate Open Exchange Format (AOEF) | ✅ | ✅ | Official Open Group standard · XSD validated |
| CSV | 🔜 | ✅ | Catalog export for manual workflows |
Archi native (.archimate) |
📋 Backlog | — | Via community contribution |
ArchiPulse is built around a single core insight: the ArchiMate Open Exchange Format already defines what entities exist — map them directly to PostgreSQL tables.
This means export is a SELECT, import is an INSERT, and collaboration is database-native. No custom metamodel, no graph database, no vendor lock-in.
Repository structure:
archipulse/
├── cmd/
│ └── archipulse/
│ ├── ui/ # Svelte 5 + Vite 6 frontend
│ │ └── src/ # Components, routes, lib
│ ├── embed.go # //go:embed ui/dist
│ └── main.go # serve · migrate · seed · CLI · MCP entry points
├── internal/
│ ├── parser/ # AOEF parser with ArchiMate structural validation
│ ├── exporter/ # AOEF export (SELECT → XML)
│ ├── workspace/ # Workspace CRUD
│ ├── element/ # Element CRUD
│ ├── relationship/ # Relationship CRUD
│ ├── diagram/ # Diagram CRUD
│ ├── viewer/ # EAM view generation (SQL queries)
│ │ └── views/ # Individual view implementations
│ ├── api/ # REST API handlers
│ ├── auth/ # JWT + OIDC authentication
│ ├── audit/ # Audit log / workspace events
│ ├── cli/ # archipulse CLI commands
│ ├── mcpserver/ # MCP server (AI agent integration)
│ ├── savedviews/ # Saved views with filter state
│ └── snapshot/ # Workspace snapshots / baselines
├── migrations/ # PostgreSQL migrations
└── examples/ # Sample ArchiMate models (ArchiSurance, ArchiMetal)
- AOEF parser with ArchiMate structural validation
- PostgreSQL schema (AOEF as tables)
- Workspace, element, relationship, diagram CRUD API
- Optimistic locking on all editable resources
- AOEF export (round-trip compatible)
- CI pipeline and test suite
- Embedded SPA frontend (single binary, no runtime deps)
- Static AOEF viewer — faithful reproduction of ArchiMate diagrams
- EAM views: Element Catalogue, Application Catalogue, Application Landscape, Technology Catalogue
- Application Dependency Graph
- Capability Tree view
- Docker Compose setup
- Integration Map (application integration topology)
- Process–Application matrix
- Capability Landscape
- Technology Catalogue
- Svelte 5 + Vite 6 component-based frontend
- Corporate Light theme — professional enterprise UI
- Application Dashboard with lifecycle/criticality charts
- Application Dependency Graph (interactive, filterable)
- Import preview — two-step semantic diff before confirming any import
- Model Editor — create and update elements and relationships from the web UI
- Saved views — bookmark analytical views with filter state
- Audit log — per-workspace event history
- Stable, paginated REST API
- Multi-user authentication (JWT + OIDC)
-
archipulseCLI — workspaces, elements, relationships, diagrams, import/export - MCP server — AI agent integration via stdio (
archipulse mcp) - Technology Stack view (app → infrastructure matrix)
- Capability Gap Analysis (capability coverage heatmap)
- Interface Catalogue
- User management UI (invitations, roles, password reset)
- Helm chart for Kubernetes deployment
- Full documentation site at archipulse.org
- Extractor library (AWS, Azure, Confluence, ServiceNow, Jira)
- Hosted SaaS and enterprise support
The roadmap is managed publicly via GitHub Milestones. Community input is welcome in Discussions.
Contributions of all kinds are welcome.
Especially impactful right now:
- Extractors — connectors for data sources your organization uses (AWS, Azure, Jira, Confluence, ServiceNow...)
- EAM view queries — SQL queries that generate meaningful analytical views from ArchiMate models
- Web frontend — new views, UX improvements, accessibility
- Documentation — deployment guides, usage tutorials, worked examples
Please read CONTRIBUTING.md to get started.
Good entry points: good first issue · help wanted · extractor
ArchiPulse is developed and maintained by Disruptive Works and released free and open source under the Apache 2.0 license.
Self-hosted — free forever. Clone the repo, run Docker Compose, and own your data completely.
Hosted SaaS (coming soon) — a fully managed ArchiPulse instance with no infrastructure to manage. Join the waitlist at archipulse.org.
Enterprise support (coming soon) — dedicated onboarding, private deployments, SLA-backed support, and custom extractor development. If you're interested, reach out early at hello@disruptive-works.com.
Other ways to support the project:
- Star the repository — helps with visibility
- Report issues and suggest features — your feedback shapes the roadmap
- Contribute code, documentation, or extractors — see CONTRIBUTING.md
ArchiPulse is licensed under the Apache License 2.0.
ArchiMate® is a registered trademark of The Open Group. ArchiPulse is an independent project and is not affiliated with or endorsed by The Open Group.