Developer & AI tooling
Libraries, SDKs, components and internal tooling — plus the MCP servers, agent integrations and evaluation harnesses that make AI features survive production.
What we do
We build the layer between your team and the tools they use. SDKs, client libraries, framework extensions, database providers, and the internal tooling that quietly saves an hour a day per developer.
Increasingly that includes the plumbing around AI. Not model training — the tooling that decides whether an AI feature survives contact with production. MCP servers that expose your systems to agents safely. APIs legible to a model as well as to a person. Evaluation harnesses, so you can tell whether a prompt change made things better or merely different.
Damien has spent a career on this layer. Fluent API design on the .NET Framework at Microsoft, and half the engineering behind Code First for Entity Framework. Web APIs at Netflix and Xbox. Developer experience and SDKs at Auth0. The official MongoDB provider for EF Core. The Tree-sitter C# parser behind GitHub's semantic code features is his too.
How we work
A good library feels native. A developer using it shouldn't have to think about where your code ends and the framework's begins. That means matching the conventions of the ecosystem it lives in rather than importing our own.
AI tooling has to be measurable. A feature with no evaluation harness is a feature nobody can safely change, because there's no way to know whether the last adjustment helped. We build the harness first and the feature second.
Real usage is the specification. The code your team writes today, and the workarounds they've already built, tell us more than a requirements document.
Where a fix belongs upstream, we'll help you get it there rather than building you a fork to maintain forever. Everything ships with tests, documentation and a plan for who maintains it after we're gone.
Who it's for
Teams hitting the edge of an open-source library and weighing up a fork.
Companies shipping an API who need a client SDK developers won't complain about.
Teams with an AI feature that demos well and behaves unpredictably in production.
Platform teams who need internal tooling built by someone who has built it before.
From the blog
What we've learned building software, and the opinions we came away with.
You don't need WordPress any more
I ran WordPress for years — my own sites and clients', from cPanel to HHVM to a dedicated server. Then came the hack while I was asleep, and the content I couldn't manipulate. Why I left, and what I run instead.
Reintroducing Intracia
A new site, a clear list of the work we take on, and Intracia out in the open for the first time.