Matrix by Shared Kernel.Opinionated AI platform
for business solutions.

THE SOLUTION STRUCTURE

Your applications.
A common foundation.

Build complete applications in code, with shared services that connect them.

Business applications use Matrix Core and connect to shared portal, identity, workflow and messaging services, alongside existing systems.
Scroll to follow the diagramOpen diagram
Code, integration and deployment

Your domain logic and custom interfaces stay in full .NET applications. Matrix Core is used inside those applications; Portal, Workflow and Messages provide shared services. LLM skills and opinionated developer guidance support implementation. CI/CD and Docker practices support delivery. Legacy modernization proceeds through explicit interfaces, data ownership, tests and planned cutovers. Kubernetes remains a future deployment target.

AI on both sides.
A contract at the centre.

A V connects probabilistic development to deterministic execution, then to probabilistic consumption. Matrix provides the deterministic contract.
Open diagram
What makes the contract deterministic?

AI can generate code or interpret a request. The application executes defined interfaces, permissions and business rules against explicit workflow state. Matrix supplies the contracts and development guidance; Shared Kernel helps your team implement and verify the behavior. AI-generated output remains probabilistic.

PORTAL AND IDENTITY

One place to start.
Connected applications.

Users sign in, find their applications and reach their work.

A user reaches Matrix Portal through shared sign-on, then launches enrolled business applications. Identity providers and a common inbox connect the experience.
Scroll to follow the diagramOpen diagram

WORKFLOW AND MESSAGING

People decide.
Services execute.

See the business process, then the messages that connect it.

An illustrative approval process: start, validate a request, human review, an approved-or-rejected gateway, and the application of an approved change.
Illustrative approval processOpen diagram
Process ownership and messaging

Workflow owns decisions and process progress. Application services own business changes. Messaging transports commands and events; Messages provides the human inbox. A transport acknowledgement is not business completion. Shared Kernel qualifies the supported BPMN profile for your use case and verifies retries, duplicate handling and failure paths.

SHARED KERNEL

The platform engineers.
Inside your team.

We develop Matrix and co-develop your solutions at your premises.

Shared Kernel engineers and your team work together on requirements, implementation and verification, leaving working applications and internal capability.
Scroll to follow the diagramOpen diagram
What the engagement includes

Experienced practising engineers work with your developers and business teams on architecture, platform customization and implementation. We apply domain-driven design, project planning, work tracking, code review and meaningful tests. Documentation and knowledge transfer build internal capability, with maintenance and support responsibilities agreed for ongoing operation.

SECURITY AND QUALITY

Controls you can verify.

AccessAllowed and denied tests
AuditRetrievable records
Business rulesAcceptance tests
RecoveryRestore exercises
Security and audit integration

Shared services reduce the infrastructure responsibilities and exposed interfaces of individual applications. Shared Kernel helps configure and verify identity, application permissions and business rules. Retained audit evidence requires durable storage, controlled access and a retention policy. Acceptance applies to the selected release in your environment.

NIS2 support

Matrix and Shared Kernel can support the engineering work within your NIS2 programme through secure development practices, access controls, retained audit evidence and recovery verification. Compliance depends on your organization’s scope, governance and operation of its controls. Deploying the platform does not establish compliance on its own.

NIS2 Articles 20 and 21

YOUR FIRST APPLICATION

Build it together.
Decide with evidence.

  1. 01Choose the use case
  2. 02Build and verify
  3. 03Assess wider adoption
The investment decision

Agree a bounded use case, integration boundaries and acceptance criteria. Review actual effort, support needs and your team’s ability to make a change. A second use case tests reuse. Confirm the supported capability baseline, licensing, source access, application rights, integration and training costs, maintenance responsibilities and exit arrangements before wider investment.