Direct Answer
Prolaborate and Kernaro AI Hub solve different problems: comparing them directly is a category error. Prolaborate is a publishing and browsing layer: it takes EA repository content and presents it to non-architect stakeholders in a structured, navigable browser interface. Kernaro AI Hub is an AI intelligence layer: it connects an AI assistant to the EA repository so stakeholders can ask natural-language questions and receive governed, contextual answers. The user journey is completely different: Prolaborate users browse what architects have published; Kernaro users ask what they want to know. For many organizations, the right answer is both: Prolaborate for structured consumption of published architecture views, Kernaro for dynamic AI querying of repository intelligence. Where budget forces a choice, pick based on whether your stakeholders primarily need to browse or primarily need to ask.
Key Takeaways
- Prolaborate = publish and browse. Kernaro AI Hub = ask and answer.
- Different user journeys: Prolaborate is a portal; Kernaro is a conversation interface.
- Prolaborate is purchased from Sparx Systems (not Sparx Services). Kernaro AI Hub requires EA GraphLink, available through Sparx Services.
- Kernaro AI Hub is in General Availability from 2026.
- EA GraphLink Interface B (MCP Server) is the technical foundation of Kernaro AI Hub.
- Both products address the same root problem: making EA content accessible to non-architects: they just do it differently.
- Most mature EA practices will eventually need both. Many start with Prolaborate first.
What Is Prolaborate?
Prolaborate is a stakeholder engagement platform developed by Prolaborate (a Sparx Systems ecosystem partner). It connects to a Sparx EA repository and publishes architecture content: diagrams, element lists, models, reports: to a web browser portal accessible to non-architects without Sparx EA licenses.
What Prolaborate shows:
- Architecture diagrams as rendered, interactive views
- Element details (name, description, tagged values) presented in a structured layout
- Navigation through the model (by package, by diagram, by search)
- Filtered views: show only the content relevant to a particular stakeholder group
- Report-style outputs from the repository
Who uses Prolaborate:
- Business stakeholders who need to see architecture deliverables but do not have Sparx EA licenses
- Executive sponsors reviewing published architecture views
- Project managers checking application portfolio data
- Operations teams browsing technology landscape maps
The user journey in Prolaborate: The architect publishes content from Sparx EA to Prolaborate. The stakeholder opens a browser, navigates to the relevant view, and browses what the architect has published. The stakeholder is a consumer of a pre-structured presentation layer.
Purchasing Prolaborate: Prolaborate is licensed through Sparx Systems or directly through Prolaborate. It is not a Sparx Services product. Sparx Services can advise on configuration and integration, but the license relationship is with Prolaborate/Sparx Systems.
What Is Kernaro AI Hub?
Kernaro AI Hub is an AI-powered intelligence interface that connects AI assistants to the Sparx EA repository via EA GraphLink Interface B (the MCP Server). Instead of browsing pre-published content, stakeholders interact with an AI assistant that can dynamically answer natural-language questions about the architecture.
What Kernaro AI Hub answers:
- “Which applications support the Customer Onboarding capability?”
- “What is the current lifecycle status of our CRM applications?”
- “Which technology components have no documented business owner?”
- “What decisions were recorded in the last Architecture Review Board?”
- “Which capabilities have no application coverage?”
Who uses Kernaro AI Hub:
- Executives who want architecture intelligence on demand, without navigating a portal
- Project managers asking specific questions about system dependencies
- Architects checking their own repository for governance gaps
- Business analysts investigating which systems support specific business processes
The user journey in Kernaro AI Hub: The stakeholder opens an AI chat interface (within Kernaro AI Hub, or through a connected AI assistant like Copilot or Claude). They type a natural-language question. The AI queries the EA repository through the MCP Server, retrieves governed architecture data, and returns a contextual answer. No browsing. No navigation. No pre-published views required.
Purchasing and deploying Kernaro AI Hub: Kernaro AI Hub requires EA GraphLink (from Sparx Systems) and MCP Server configuration (EA GraphLink Interface B). Sparx Services implements EA GraphLink and the Kernaro AI Hub integration through the Connect engagement. Kernaro AI Hub reached General Availability in 2026.
The Technical Distinction
Both tools access the Sparx EA repository. The difference is in how they access it and what they return:
Prolaborate: Uses the Sparx EA repository’s native data access to render and present architecture content as structured HTML views. It presents what the repository contains in a readable format.
Kernaro AI Hub: Uses EA GraphLink Interface B (MCP Server), which exposes the repository as an MCP-compliant context source. An AI assistant connected to this MCP Server can dynamically query elements, relationships, tagged values, and documentation: then synthesize answers rather than display raw data.
The MDG governance quality in Sparx EA matters for both tools, but it matters more for Kernaro AI Hub. Prolaborate can present poorly-governed data as a list. Kernaro AI Hub generates intelligence from data: if the data has missing owners, inconsistent lifecycle values, or incomplete capability coverage, the AI’s answers will reflect those gaps. This is why MDG Technology governance (Sparx Services Amplify) is often a prerequisite for Kernaro AI Hub deployment.
Comparing User Journeys Side by Side
| Aspect | Prolaborate | Kernaro AI Hub |
|---|---|---|
| Interaction model | Browse / navigate | Ask / answer |
| Content source | Published views | Live repository queries |
| Requires architect to publish? | Yes: content must be published | No: queries 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: AI synthesizes answers |
| Governance dependency | Moderate | High (MDG quality critical) |
| License source | Prolaborate / Sparx Systems | EA GraphLink + Sparx Services |
| Availability | Available now | GA 2026 |
When to Choose Prolaborate
Prolaborate is the right choice when:
- Stakeholders primarily need to browse and navigate published architecture views
- Your EA team produces structured deliverables (landscape diagrams, standards registers, capability maps) that stakeholders need to reference
- You want controlled publishing: architects decide what is visible and when
- You are not ready for AI integration: Prolaborate has lower MDG governance prerequisites
- Your stakeholders are comfortable with portal navigation interfaces
- You need to replace the habit of emailing static PowerPoint exports
When to Choose Kernaro AI Hub
Kernaro AI Hub is the right choice when:
- Stakeholders want to ask specific, dynamic questions rather than browse pre-structured content
- Your EA repository is well-governed (MDG stereotypes applied consistently, key tagged values populated)
- You want to connect EA intelligence to existing AI tools (Copilot, Claude, Gemini) that stakeholders already use
- You are building agentic EA workflows where AI tools query architecture data as part of broader automated processes
- Executive stakeholders want architecture intelligence without the friction of navigating a portal
When to Choose Both
The strongest EA stakeholder layer combines both:
- Prolaborate for structured browsing: the technology landscape portal, the standards register, the published capability map
- Kernaro AI Hub for dynamic intelligence: executive queries, governance checking, ad-hoc analysis
This combination mirrors how stakeholders naturally want to consume information: sometimes they want to browse a map; sometimes they want to ask a question.
Frequently Asked Questions
Q: Can Kernaro AI Hub replace Prolaborate entirely? Not entirely. Kernaro AI Hub is optimized for natural-language querying and answer synthesis. Prolaborate is optimized for structured navigation and browsing of published architecture views. Some stakeholders: particularly those who prefer visual exploration of diagrams and structured layouts: will find Prolaborate a better fit. Others who want direct answers will prefer Kernaro. The tools complement rather than replace each other.
Q: Does Kernaro AI Hub require EA GraphLink? Yes. Kernaro AI Hub is built on EA GraphLink Interface B (the MCP Server). EA GraphLink must be deployed and the MCP Server interface enabled before Kernaro AI Hub can be configured. Sparx Services implements EA GraphLink through the Connect engagement, which includes Kernaro AI Hub setup.
Q: Is Prolaborate sold by Sparx Services? No. Prolaborate is a product of Prolaborate (a Sparx Systems ecosystem partner). Licensing is purchased through Sparx Systems or Prolaborate directly. Sparx Services can advise on Prolaborate configuration and integration as part of an EA program, but the license and vendor relationship is separate.
Q: What happens if my Sparx EA repository has poor data quality? Does Kernaro AI Hub still work? Kernaro AI Hub will work, but its output quality will reflect the repository’s data quality. If elements lack owners, if lifecycle status tagged values are unpopulated, or if MDG stereotypes are applied inconsistently, the AI’s answers will be incomplete or imprecise. This is why Sparx Services recommends MDG governance establishment (Amplify engagement) before or alongside Kernaro AI Hub deployment. The MDG quality gate is what transforms raw repository data into trustworthy AI-queryable intelligence.
Q: Which AI assistants does Kernaro AI Hub support? Kernaro AI Hub uses the Model Context Protocol (MCP), which means any MCP-compatible AI assistant can connect to it. This includes Claude (Anthropic), Microsoft Copilot, Google Gemini, Salesforce Agentforce, and ChatGPT Enterprise. The MCP standard means Kernaro AI Hub is not locked to a single AI vendor: your organization uses whichever AI assistant fits your ecosystem.
Q: How is Kernaro AI Hub licensed? Kernaro AI Hub licensing is connected to the EA GraphLink license from Sparx Systems, with implementation and configuration delivered by Sparx Services through the Connect engagement. For current licensing details, contact Sparx Services to discuss your specific configuration.
Q: Can stakeholders use Kernaro AI Hub directly in Microsoft Teams or Outlook? Yes, if Copilot is the connected AI assistant. Because Kernaro AI Hub uses MCP and Copilot is MCP-compatible, stakeholders with Copilot access in M365 (Teams, Outlook, SharePoint) can ask EA-related questions directly within those surfaces. The EA MCP Server is available as a context source to the same Copilot instance stakeholders use for other work: no separate interface needed.
Q: When will Kernaro AI Hub be available for production deployment? Kernaro AI Hub reached General Availability in 2026. Sparx Services is deploying it through the Connect engagement for organizations that have EA GraphLink in place. If you are planning an EA GraphLink deployment now, your implementation will include Kernaro AI Hub as a deliverable.
Ready to Deploy Kernaro AI Hub?
Sparx Services’ Connect engagement covers EA GraphLink deployment, MCP Server configuration, and Kernaro AI Hub setup: including the MDG quality assessment that determines whether your repository is ready for AI querying.
If you are starting from Prolaborate and want to add AI intelligence, Connect can layer Kernaro AI Hub on top of your existing Sparx EA environment.
