This is where Infragate's build notes go. One post per thing that shipped, written by whoever shipped it, usually with the screenshots from the run that convinced us it worked. Expect a lot of "here is the config file and what it does" and not much launch language.

It is not a changelog and not a roadmap. If a post is here, the thing in it exists and you can go use it. When something turns out to be a bad idea, the post stays up with a note on top instead of quietly disappearing.

What Infragate makes

Three things are out today:

• CAPA. An open-source CLI for the capabilities an agent gets: skills, tools, MCP servers, sub-agents, hooks, all declared in one file per repo. Start with the post that introduces it.
• Lanyard. A hosted MCP gateway. One URL in front of the servers you pick, each person signed in as themselves, one revocable key per agent. How it works.
• ShareCube. Where agent output becomes team input: HTML and Markdown artifacts with a URL, versions, and comments anchored to the exact sentence. How it works.

A capabilities registry and agent telemetry are being built and are not out yet. All of it is built on the Model Context Protocol, because an open standard is the only version of this that survives.

Where this came from

None of it started as a product. It started as a chatbot that needed to read live data out of a hospital operations platform, and three approaches that did not hold up. That post is still the first one on this blog.

For the company itself, who we are and where this is going, that page lives on the main site: infragate.ai/about. The products are at infragate.ai/products and the code is on GitHub.