From 1f64ede18a99f8b7b8776074783f4a5430cd78a8 Mon Sep 17 00:00:00 2001 From: Victor Soria Date: Sun, 3 May 2026 18:34:29 -0500 Subject: [PATCH] docs(website): reposition around AI-native EA and interoperability MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit - Hero: new headline 'Describe your architecture. AI builds the model.' - Problem section: remove OWL/ontology framing, lead with proprietary lock-in - Features: AI-Native via MCP and AOEF Interoperability moved to top; remove Enrichment Pipeline (not built); add Model Editor; fix copy - How it works: restructure as 'two ways in, one model out' — upload AOEF or describe to AI agent via MCP; emphasize roundtrip export - CTA: updated to match AI-native positioning - Footer: add Victor Soria CTO credit, disruptive-works.com link, contact email --- website/index.html | 92 ++++++++++++++++++++++------------------------ 1 file changed, 43 insertions(+), 49 deletions(-) diff --git a/website/index.html b/website/index.html index 36b72dd..367d603 100644 --- a/website/index.html +++ b/website/index.html @@ -544,23 +544,22 @@

- Enterprise Architecture
- without lock-in. + Describe your architecture.
+ AI builds the model.

- ArchiPulse stores, visualizes, and analyzes your ArchiMate models in a self-hosted web platform. - Your architecture is not a static file — it's living, collaborative data. + ArchiPulse is an AI-native Enterprise Architecture platform — connect your AI agent via MCP and let it create, query, and manage ArchiMate models. Every model is stored relationally, exportable as AOEF, and fully interoperable with Archi, BiZZdesign, and Sparx EA.

- + + Live Demo → + + View on GitHub - - Live Demo → -
@@ -629,19 +628,19 @@

See it in action.

The problem
-

EA tools are either academic or proprietary.

-

Most tools force you to choose between an obtuse ontology stack or an expensive closed platform. ArchiPulse takes a third path.

+

EA tools are expensive, closed, and manual.

+

Most platforms lock your data in proprietary formats, charge per seat, and still require architects to model everything by hand. ArchiPulse takes a different path.

The old way
-

Vendor lock-in or academic overkill

-

Proprietary formats, expensive licenses, and data you can't query. Or the other extreme: OWL ontologies, Protégé, and SPARQL queries that only academics can read.

+

Proprietary, expensive, and static

+

Vendor lock-in, six-figure licenses, and architecture data you can't query or export freely. Models that live in a single tool and die when the license expires.

ArchiPulse
-

AOEF directly as PostgreSQL tables

-

The ArchiMate Open Exchange Format becomes the data model itself. Export is a SELECT. Import is an INSERT. Collaboration is database-native. No custom metamodel, no vendor dependency.

+

Open, relational, AI-operable

+

AOEF mapped directly to PostgreSQL — export is a SELECT, import is an INSERT. Connect an AI agent via MCP and let it build and query models for you. Your data stays yours, forever exportable to any AOEF-compliant tool.

@@ -655,6 +654,16 @@

Built for working architects.

Everything your team needs to make EA a living, queryable, collaborative practice — not a PowerPoint exercise.

+
+
⌘
+

AI-Native via MCP

+

Connect Claude or any MCP-compatible agent to ArchiPulse. The AI creates workspaces, models elements and relationships, queries views, and exports AOEF — all through natural language.

+
+
+
↔
+

AOEF Interoperability

+

Import and export valid AOEF XML at any time. Full roundtrip with Archi, archimate-editor, BiZZdesign, and Sparx EA. Your models are never trapped.

+
⚙

Collaborative Repository

@@ -662,33 +671,18 @@

Collaborative Repository

⚡
-

Semantic Diff

-

Upload an AOEF file and review element-by-element what changed and who changed it. Your model's history, readable at a glance.

+

Import Preview

+

Upload an AOEF file and review element-by-element what would change before committing. No surprises, no accidental overwrites.

◈

EAM Analytical Views

-

Application Dashboard, Application Landscape Map, Capability Tree, Technology Catalogue — pre-defined views generated from your model data.

-
-
-
⬡
-

Dependency Graph

-

Interactive application dependency graph powered by XY Flow. Visualize integrations, pan and zoom, filter by lifecycle and type.

-
-
-
⤢
-

Enrichment Pipeline

-

Connect real-world resource catalogs — AWS, Confluence, Excel, custom sources — to your ArchiMate workspace. Community-contributed extractors.

+

Application Dashboard, Landscape Map, Capability Tree, Technology Stack, Dependency Graph — pre-defined views generated automatically from your model data.

-
↔
-

Open & Integrable

-

Import and export AOEF XML at any time. Compatible with Archi, archimate-editor, BiZZdesign, Sparx EA. Full REST API. Self-hosted.

-
-
-
⌘
-

CLI & AI Integration

-

archipulse CLI for scripting and automation. MCP server (archipulse mcp) connects ArchiPulse directly to Claude or any MCP-compatible AI agent.

+
⊞
+

Model Editor

+

Create and update elements and relationships directly from the web UI. No file upload required — edit your model live and see changes immediately.

@@ -698,36 +692,36 @@

CLI & AI Integration

How it works
-

One insight. Radical simplicity.

-

The ArchiMate Open Exchange Format already defines what entities exist. Map them directly to PostgreSQL tables — and everything else becomes trivial.

+

Two ways in. One model out.

+

Start from an existing AOEF file or let an AI agent build the model from scratch — the result is the same: a persistent, queryable, interoperable ArchiMate repository.

1
-

Model in your preferred tool

-

Use Archi, archimate-editor, or any AOEF-compatible tool. ArchiPulse works alongside what you already have — it doesn't replace it.

+

Bring your model — or describe it

+

Upload an AOEF file from Archi, BiZZdesign, or any compatible tool. Or connect Claude (or any MCP agent) and describe your system in natural language — the AI creates elements, relationships, and diagrams directly.

2
-

Upload AOEF

-

ArchiPulse parses the model and stores it in PostgreSQL — one row per element, relationship, and diagram. XSD validated. No transformation magic.

+

Stored in PostgreSQL, structured as AOEF

+

Every element, relationship, and diagram lives in a relational database — one row per concept. Queryable, versioned, and always exportable. No proprietary format, no lock-in.

3
-

Collaborate and enrich

-

Multiple architects edit the same workspace directly via the web interface or REST API. The enrichment pipeline pulls from external sources and maps resources to ArchiMate elements.

+

Explore, collaborate, and analyze

+

Multiple architects edit the same workspace simultaneously. Explore through EAM analytical views, dependency graphs, and capability trees — all generated automatically from your model data.

4
-

Explore, analyze, export

-

EAM analytical views, interactive dependency graphs, capability trees. Export back to AOEF at any time — importable in any compliant tool.

+

Export and round-trip

+

Export valid AOEF at any time and open it in Archi, Sparx EA, or any compliant tool. Your architecture travels with you — no conversion, no data loss.

@@ -834,8 +828,8 @@

Documentation

Get started
-

Your architecture deserves better than a static file.

-

ArchiPulse is free, open source, and self-hosted. Apache 2.0. Your data stays in your infrastructure.

+

Let AI build your enterprise architecture.

+

ArchiPulse is free, open source, and self-hosted. Connect your AI agent, describe your systems, and have a queryable ArchiMate repository in minutes.

@@ -846,12 +840,12 @@

Your architecture deserves better than a static file.