Every capability, installable.
Xema is a foundation you build on, however you want: apps, agents, agent teams, workflows, harnesses, runtimes and integrations. Everything you build runs on the same agentic layer as every other agent in the company. This page is for the people and agents who extend it. What you build — new expertise, new connections to your systems, a complete department solution — installs as a package, organisation by organisation, on the same foundation every other package uses: identity, permissions, approvals, audit, agents and connections.
One connection
Your CRM
Connected once, by Sales
- passed: SalesProposal drafts from live dealswithin each seller’s own access
- passed: SupportCustomer history in every replythe next week — nothing rebuilt
- held: FinanceRenewal checks before invoicingchanges to a record need approval
Build anything on it.
Your way.
AApps
Your own screens and logic, installed beside everything else and held to the same rules.
BAgents
Agents with your expertise and your tools, with an identity and a grant of their own.
CAgent teams
Standing roles and workers, shaped the way your company works.
DWorkflows
Your process as steps, review loops and gates, run the same way every time.
EHarnesses
Your own harness strategy: roles, lanes, reviews and landing, installed and versioned.
FRuntimes
Bring a runtime or your own SDK. Identity, permissions and audit come with it.
GIntegrations
Connect the systems you run on, in both directions, through connectors and MCP.
Examples to start from: agent teams and agents and runtimes for engineering teams.
Everything a package
can bring.
Multi-step processes your teams can run as they are and adapt to how they work.
Purpose-built tools and views that appear right inside the platform, alongside everything else.
New behaviors and processing tuned to a domain — added cleanly, without disrupting what already runs.
Connect your own knowledge and information sources so agents work from what your business actually knows.
Structured templates that define exactly what finished, reviewable work looks like for your domain.
Packaged know-how, judgment, and skills — the experience an agent needs to act well in your world.
Preconfigured working sessions tuned to a task: what the agent sees, what it can do, and what gets recorded.
A full department solution — screens, logic, processes, and governance — packaged to install all at once.
Adapters that link Xema to the tools your business already runs on, in both directions.
Install it.
The platform does the wiring.
A package is a directory with one manifest at its root. The manifest names every component it ships and where each one lives; the platform discovers it, verifies it, and hands each contribution to the registry that owns it. New capabilities extend the platform; they never fork it.
AVerified before it lands
A package is fetched from the source it declares, its signature is checked, it is statically analysed, and it is stored content-addressed — so the same reference always resolves to the same bytes.
BDeclared, then read
One manifest states what the package ships. The platform reads it and routes each contribution to the registry that owns it — processes to the workflow engine, skills to the skill registry, capabilities to the capability registry.
CAdds without disrupting
New logic and services slot in alongside everything already running. Adding a capability is an install, not a rewrite.
DFeels native
New tools and screens appear directly in the platform, consistent with everything else your teams already use.
Define a capability once.
Everything reaches it the same way.
A capability is a named business operation — refund an invoice, change a booking, redline a contract — with its inputs, its risk, who may run it and who approves. It is what your packages expose, and what your permissions and approvals attach to.
1Declare the capability
Name the operation, its schema, its risk, and what happens when it goes wrong.
2Bind it to its providers
None yet, one, or several: an internal API, an MCP server, a Xema workflow, an automation, a partner’s agent. Change the binding later; the capability the business governs does not move.
3Let anything call it
A person, an agent, an app, a schedule, an external platform. Same decision, same credentials boundary, same record — whichever one it is.
Your developers, your agents,
your partners.
Build packages for your own organisation: processes, capabilities, screens and connections. Your domain, on the shared base.
your platform teamAn authorised coding agent builds and extends applications, within the permissions it was given.
within granted permissionsPackage industry expertise once — processes, screens, skills, tools — and let each customer organisation install it.
installable per organisationWhoever builds a package, it builds on the shared platform — security, governance and audit come with every one of them.
A package can be a full solution.
A package can carry a complete experience: its own screens, its own logic, its own definitions of done, its own guided workspaces, its own connections. The platform supplies the shared base — the working environment, the knowledge layer, and the governance — and the package supplies the domain expertise. Every app gets these building blocks from the base platform, and reaches outside systems through supported connectors and exposed capabilities:
Ask a person to decide before work goes ahead. People or agents raise the request; the person picks from the answers offered — approve or refuse, or choose between proposals.
A tamper-evident, append-only record of what happened on the platform, kept for compliance and review.
Route your agents’ calls to MCP tools, whether you register the servers or a package ships them.
One place that decides who or what may do which action, checked for every request.
A shared entry point for connecting outside services, which per-service connectors build on.
Define multi-step processes once and run them reliably, with the finished output defined up front.
Store documents and search them by meaning, so apps and agents can work from your own knowledge.
One audited route for reading and searching the public web, with the content treated as untrusted.
Have work that
doesn't fit a generic copilot?
Installable packages are how you grow the platform without rebuilding it — and how a department-specific idea becomes a real, governed solution the whole business can use.