Platform overview
The components Skilder is built from and the boundaries between them.
The control plane stores and authorizes your roles and skills. A separate execution layer runs them.
Components
| Component | Responsibility | Built on |
|---|---|---|
| Web app | Authoring roles, skills, servers and settings | React |
| Control plane | Identity, permissions, the role and skill catalog, OAuth authorization | Fastify and Apollo GraphQL |
| Graph database | Workspaces, roles, skills, MCP server definitions, activity | Dgraph |
| Message bus | Every request that reaches a runtime | NATS, with JetStream for the audit trail |
| Remote MCP server | The endpoint agents connect to. Holds sessions and serves Skilder's own tools. Runs no MCP server and no script | MCP over Streamable HTTP |
| Runtime | Runs MCP servers and skill scripts | Container image |
How the parts connect
Two boundaries carry the design:
- The public endpoint and the execution layer are separate containers with separate identities.
- Every call to one of your MCP servers, and every skill script, crosses the message bus. Only Skilder's own tools run on the endpoint itself.
Standards
Agents connect over the Model Context Protocol on Streamable HTTP. An MCP client needs no Skilder plugin. Skills follow the Agent Skills standard and import and export as SKILL.md packages.
Where it runs
Skilder hosts the platform in Switzerland. A runtime can also run on infrastructure you operate, which keeps tool and script execution inside your network.
Next
- Execution and isolation, for what happens on a tool call.
- Security and data, for identity, encryption and hosting.