Open-source commitments and custom solution onboarding

What we publish

Sigrix publishes the parts of its platform that other people build against. A marketplace can be a product; the contract an agent is run and licensed under should not be one. Eight projects are open today, all under Apache-2.0, in one GitHub organisation, sigrix-io:

• Postern: the open protocol for running and licensing packaged AI agents, four HTTP verbs and a licensing check. Its specification is 0.1, a draft.
• sigrix-runtime: the runner inside every bundle Sigrix delivers, and the specification's complete implementation.
• Gatehouse: the page an agent is run from in the browser, for any runner that serves Postern's four verbs.
• sigrix-mcp: the client sellers publish through, from their own editor.
• sigrix-launcher: starts an MCP server you bought from your MCP client, after checking the purchase.
• mullion: the library that opens every image uploaded to Sigrix, and that you can use for anything else.
• Herald: the tool that announces each Hub update on every channel we post to, this one included.
• Bailey: an open-source assistant that runs ready-made solutions on your own machine, with your own AI key. It is in development, and open from its first release.

The open source page shows how the pieces connect.

Three commitments

1. The document is what you pin to. Sigrix runs a Postern implementation, but the specification is the definition. Where the two disagree, the document wins, and the disagreement is worth an issue.
2. Published before it is finished. Feedback is cheapest while changing things is still free. The specification is not tagged yet, and every page that shows it says so.
3. No dependency in either direction. A distributor is optional, the schemas work without ever being fetched, and nothing in the protocol requires our services.

Issues and pull requests are read in the sigrix-io organisation on GitHub, the one community surface we run today.

Help listing a custom solution

Built an MCP server, an agent or workflow, or an integration that doesn't fit a listing type? The Sigrix team will onboard it with you through Custom solutions:

1. Tell us what you built: what it does, who it's for and how it runs today.
2. We follow up: a person replies with questions, such as how buyers install it, what it needs to run and how to price it.
3. We set up the listing: if none of the listing types fit, we add one, with the fields and review checks your product needs.
4. You publish and sell: it goes through the same review as every listing, and nothing goes live without your go-ahead.

If it already fits a listing type, such as a prompt, persona, skill or MCP server, you can publish it directly.