What Is Prolaborate? Sparx EA’s Stakeholder Portal Explained

If you have ever exported a clutch of diagrams into a slide deck the week before a steering committee, Prolaborate is the answer to the question that follows: why are we doing this by hand every cycle? It is the most direct way to get current architecture content in front of an audience that has no intention of learning a modeling tool — and that is worth understanding precisely, because the portal is easy to confuse with the AI products that now sit alongside it.

What Prolaborate actually does

Prolaborate connects to your EA repository — a local file or a shared database — and serves selected content through a web portal to people outside the architecture team. The core capabilities break down as follows.

Diagram publication. Chosen diagrams are pushed to the portal, where stakeholders view them in a browser, zoom, and follow hyperlinks to related content. Edits made in EA appear in Prolaborate after a sync, so the published view tracks the model rather than freezing at a point in time.

Model views and matrices. Beyond static diagrams, Prolaborate exposes matrix and list views — application-to-capability mappings, risk registers, technology radar content — in tabular formats that business readers often find more approachable than a diagram.

Search and browse. Stakeholders search published content and navigate the published package structure, giving them a self-service path to the architecture information they need.

Commenting and feedback. A commenting layer lets stakeholders annotate diagrams with questions or observations without touching the underlying model — useful for review cycles where you want input but not edits.

Portal customization. Organizations brand the portal, organize content into sections, and use role-based access controls to decide which audiences see which views.

The line worth drawing is around what Prolaborate deliberately leaves alone: it does not generate analysis, answer questions, or build dashboards from raw EA data. It publishes what architects put in the repository. The relevance of what a stakeholder sees depends entirely on what has been modeled and how well it is maintained — the portal faithfully reflects the model behind it, for better or worse.

Where Prolaborate sits in the picture

The cleanest way to hold the distinction is to look at the path from repository to reader. Prolaborate runs along the top — an architect curates content and a stakeholder views it. Kernaro AI Hub runs along the bottom — a stakeholder asks a question and answers are synthesized live.

Who uses Prolaborate

The primary audience is business stakeholders who need to engage with architecture but do not work in Sparx EA. In practice that means:

• Program and project managers who need to see which applications are in scope for a transformation, what integrates with what, and what the target state looks like.
• Business process owners who review and sign off process models without learning a modeling tool.
• Governance committees and architecture review boards who want to read architecture views without sitting through a walkthrough.
• IT management who want a recurring view of the application landscape without navigating the EA client.

The benefit is access without complexity. Stakeholders get what they need without licenses, training, or a client installation, and architects keep control over what is published and when. For a fuller view of what that opens up, see Application Portfolio Management, where a published portfolio view is often the first thing leadership actually asks for.

How Prolaborate compares to Kernaro AI Hub

This distinction is worth stating plainly, because the two products are easy to confuse.

Prolaborate is a publishing layer. An architect decides what to publish; stakeholders view what has been published. The intelligence — the analysis, the synthesis, the interpretation — happens before anything reaches the portal. Prolaborate is the display medium.

Kernaro AI Hub is an intelligence layer. It reads the EA repository through EA GraphLink — a read-only MCP server deployed for the whole organization — and gives stakeholders an AI-powered query interface. Someone can type “What are the regulatory risks tied to our customer data platform?” and get a structured answer drawn from the repository — capabilities, applications, data flows, risk elements, compliance links — composed on demand. Kernaro AI Hub generates insight; Prolaborate shows pre-existing content. (GraphLink reached general availability in January 2026, so this pairing is recent rather than long-established.)

The practical test is what your stakeholder problem actually is. If it is “they can’t see our diagrams easily,” Prolaborate solves that. If it is “they ask architecture questions at inconvenient moments and want answers, not a presentation,” Kernaro AI Hub solves that. Plenty of large organizations have both problems, and both tools then have a role.

There is a governance angle too. Prolaborate asks architects to actively maintain published content — a stale diagram in the portal is a reputational risk for the EA team. Kernaro AI Hub queries the live repository, so currency comes down to repository hygiene rather than publication discipline. Both place demands on the team; they are simply different demands. If you are weighing the two head-to-head, the companion piece Kernaro AI Hub vs Prolaborate works through the decision in detail.

Licensing and procurement

Prolaborate is licensed directly from Sparx Systems. It is a separate product from Sparx EA and needs its own licensing, typically per named user or on a concurrent-user basis, with pricing that varies by user count and deployment model (cloud-hosted or self-hosted).

Sparx Services does not resell Prolaborate — if you are evaluating it, procurement runs through Sparx Systems or an authorized reseller. What we can do is advise on whether Prolaborate is the right tool for your stakeholder engagement problem and how to configure it well; commercial terms sit between your organization and Sparx Systems. Kernaro AI Hub, by contrast, is a Sparx Services product: it runs on EA GraphLink as its connectivity layer and is deployed with our help.

Can Prolaborate replace PowerPoint architecture reports?

For most organizations, yes — with one qualification. The structured, link-navigable views Prolaborate provides are genuinely better than static slides for architecture communication. Stakeholders explore at their own pace, follow links between related elements, and read current information rather than a snapshot from the last presentation cycle.

The qualification is that Prolaborate depends on a well-structured, actively maintained repository. If your repository is not a reliable source of truth, publishing it through Prolaborate exposes that unreliability to the exact people you most want to impress. The tool amplifies whatever is behind it — the quality or the gaps.

So effective adoption usually travels alongside a repository governance improvement program. That pairing — governance plus publication — is what turns EA from a back-office modeling exercise into a visible, valuable asset stakeholders rely on. It is also the throughline of how we think about an AI Augmented Architecture practice: get the repository trustworthy, then let publication and intelligence layers do their jobs on top of it.

Frequently asked questions