Kernaro AI Hub vs Prolaborate: Which Stakeholder Layer Is Right for Your EA Practice?

Put plainly: these two products answer different questions, so lining them up head to head is the wrong frame. Prolaborate is a publishing and browsing layer — it takes content from your EA repository and presents it to non-architect stakeholders in a structured, navigable portal. Kernaro AI Hub is an AI intelligence layer — it lets those same stakeholders ask the repository natural-language questions and get governed, contextual answers back. Prolaborate users browse what architects have published; Kernaro users ask what they want to know. For many organizations the honest answer is both. Where budget forces a single choice, decide on one thing: do your stakeholders mostly need to browse, or mostly need to ask?

Both products exist because the same problem keeps biting EA teams — the people who most need architecture answers are the ones least able to open Sparx EA. The two solve it from opposite ends. Below is how they actually differ, and where each earns its keep.

The core distinction

Strip away the feature lists and the difference is a single contrast: a portal you read versus a conversation you query.

What Prolaborate is

Prolaborate is a stakeholder engagement platform built and sold by Sparx Systems. It connects to a Sparx EA repository and publishes architecture content — diagrams, element lists, models, reports — to a browser portal that people can use without a Sparx EA license.

It tends to land with business stakeholders who need to see deliverables but have no EA license, executive sponsors reviewing published views, project managers checking application-portfolio data, and operations teams browsing the technology landscape. The common thread is consumption: someone curated a view, and the stakeholder reads it.

On licensing, Prolaborate is purchased directly from Sparx Systems — it is a separate product from Sparx EA and is not a Sparx Services offering. Sparx Services can advise on configuration and integration as part of a wider enterprise-architecture program, but the commercial relationship is between your organization and Sparx Systems.

What Kernaro AI Hub is

Kernaro AI Hub is a web-based portal that gives business stakeholders guided, AI-assisted access to EA content without a Sparx EA license. Under the hood it uses the MCP interface of EA GraphLink to pull live model data, then presents it through a conversational interface. Rather than browsing pre-published pages, stakeholders ask questions and the assistant answers from the repository as it stands today.

It suits executives who want architecture intelligence on demand without navigating a portal, project managers probing system dependencies, architects spot-checking their own repository for governance gaps, and analysts tracing which systems support which business processes.

Kernaro AI Hub is a Sparx Systems product, and it is new — it launched in January 2026, so any team running it today is measured in its first weeks and months, not years of production use. It does not stand alone: deploying it depends on EA GraphLink and its MCP server interface being configured first. Sparx Services helps you stand up that EA GraphLink foundation and get the repository to the standard the AI layer needs; if you want to connect AI directly to the model your architects work in day to day, that is the role of the local AI Power Tools for EA MCP server, which is a separate product.

The technical distinction

Both products read from the same Sparx EA repository. What separates them is how they read it and what they hand back.

Prolaborate uses Sparx EA's native data access to render architecture content as structured HTML views. It shows you what the repository contains, formatted for reading.

Kernaro AI Hub reads through EA GraphLink's MCP interface, which exposes the repository as a Model Context Protocol source. To do that, EA GraphLink needs an MDG Technology defined for the repository — the layer that translates the physical Sparx schema into the GraphQL schema the MCP server serves. To be clear, none of this is built into Sparx EA core — there is no native MCP server in the box. EA GraphLink is the paid product that adds it: a read-only server deployed centrally for enterprise-wide access. A connected assistant can then query elements, relationships, tagged values, and documentation, and synthesize an answer rather than display raw rows.

Repository governance matters for both, but it matters more for Kernaro AI Hub. Prolaborate can publish poorly governed data as a tidy list and the gaps stay hidden. Kernaro generates intelligence from that data, so missing owners, inconsistent lifecycle values, or incomplete capability coverage all surface in the answers. That is why MDG governance — the focus of Sparx Services' Configure the Solution track — is usually a prerequisite for a Kernaro AI Hub deployment that stakeholders can trust.

Comparing the user journeys side by side

Aspect	Prolaborate	Kernaro AI Hub
Interaction model	Browse and navigate	Ask and answer
Content source	Published views	Live repository queries
Requires architect to publish?	Yes — content must be published first	No — queries the repository directly
Non-technical stakeholder friendly?	Yes	Yes — natural language
Dynamic queries	No — shows published content	Yes — any query the model supports
Answer synthesis	No — displays raw content	Yes — the AI synthesizes answers
Governance dependency	Moderate	High — MDG quality is critical
License source	Sparx Systems	Sparx Systems — on an EA GraphLink foundation Sparx Services configures
Maturity	Established	New — launched January 2026

When to choose Prolaborate

Reach for Prolaborate when:

• Stakeholders mainly need to browse and navigate published architecture views
• Your team produces structured deliverables — landscape diagrams, standards registers, capability maps — that stakeholders reference repeatedly
• You want controlled publishing, where architects decide what is visible and when
• You are not yet ready for AI integration; Prolaborate carries lighter governance prerequisites
• Your stakeholders are comfortable with portal-style navigation
• You are trying to break the habit of emailing static slide exports

When to choose Kernaro AI Hub

Reach for Kernaro AI Hub when:

• Stakeholders want to ask specific, open-ended questions rather than browse pre-structured content
• Your repository is well governed — MDG stereotypes applied consistently, key tagged values populated
• You want to surface EA answers inside the AI tools stakeholders already use, such as Copilot, Claude, or Gemini
• You are building AI-driven EA workflows where architecture data feeds broader automated processes
• Executives want architecture intelligence without the friction of learning a portal

When to choose both

The strongest stakeholder layer rarely picks a side. It runs Prolaborate for structured browsing — the technology-landscape portal, the standards register, the published capability map — and Kernaro AI Hub for dynamic intelligence — executive queries, governance checks, ad-hoc analysis. That pairing matches how people actually consume information: sometimes you want to study a map, sometimes you just want to ask a question. The bigger picture of how this fits an AI-enabled practice is laid out in AI Augmented Architecture.

Frequently asked questions

If you are starting from Prolaborate and want to add AI intelligence on top, Kernaro AI Hub layers onto your existing Sparx EA environment rather than replacing it. Talk to Sparx Services about Kernaro AI Hub →