DeepEllum
The registry where AI agents, skills, tools and MCPs live — install capabilities into Ellum AI or any third-party platform from one marketplace.
The problem
Every AI platform was rebuilding the same capabilities in-house. Adding a new tool meant shipping core platform code. We wanted capability to be something you install, not something you rebuild — and we wanted that registry to serve more than one product.
What I did
- Defined the registry model that treats agents, skills, tools, CLIs, MCPs and integrations as one installable resource class.
- Specified how Ellum AI consumes capabilities over a connection to DeepEllum rather than storing them locally, so agents can be upgraded without touching core code.
- Scoped subscription-aware installation, so what an agent can do maps to what the customer actually pays for.
- Designed a monitoring agent that scans other AI platforms for new capabilities and logs them for an administrator to review — with the legal review step built into the flow, not bolted on.
Where it landed
6
resource types unified in one registry
3rd
party platforms supported by design
Stack & tools
Next.jsMCPFastAPIPostgreSQL
Next project