Fibric is open at the seams. Connectors and operators are integrations built on MCP, and capability points to a connector through indirection, so what you build plugs into the same governed kernel everything else runs on. If you build integrations, deliver systems, or take products to market, there's a way to grow alongside us.
Pick the one that fits the work you already do. You can wear more than one hat, and the program flexes to match.
You write the integration. Use the connector SDK to wrap a SaaS API, a hardware protocol, or a piece of hardware as an MCP connector, then ship a capability the kernel can call. Because capability points to a connector through indirection, your connector slots in wherever that capability is needed, with no rewrite on either side.
Best fit: API & hardware developers
You stand the system up. You scope what an operator should sense, set the intent and the policy that governs it, and get a real operation live and trusted. The kernel does the safe part, the model proposes and a deterministic executor disposes, so your work is the judgment around it, not the plumbing under it.
Best fit: integrators & consultancies
You bring Fibric to the people who run things. You know an industry and the operators in it, and you put governed reasoning in front of them. We give you the materials, a path to co-sell, and a product that does what the demo showed, because only real data is ever used and every action leaves a receipt.
Best fit: go-to-market & channel
Three things that actually move the work forward. We'd rather give you fewer real ones than a long list of badges.
Your connector or operator gets a page in the Fibric marketplace, where operators browse and install. The platform is free and people pay for integrations, so a listing is a real surface in front of real buyers, not a directory entry nobody visits.
When a deal is a fit for both of us, we work it together. We bring you into conversations where your integration or your delivery is what makes Fibric land, and we share what we're hearing from operators so you build toward real demand, not a guess.
You build against the same defineConnector, tool, and auth primitives we use ourselves. The connector SDK is documented, the kernel contract is one canonical envelope per signal, and when you get stuck on something real, you reach a human who has shipped a connector before.
The program is early, and we'd rather be plain about it than oversell. We're not promising tiers, badges, or revenue you can't verify. What we're offering is a real way to build on the kernel and a real path to the operators who use it.
In return, what you ship has to clear the same line our own work does. Trust fails closed, not open. A connector that can't be made safe doesn't go live. Single-flight per entity and idempotency keys are kernel primitives, so a runaway loop is structurally out of reach, and every action you cause writes an attributable, reversible receipt.
That bar is the whole point. It's what lets an operator hand real work to something you built and trust the result. Build to it, and you're never locked in: your connector stays yours, swapping a vendor underneath a capability is config rather than a rewrite, and you can extend Fibric without asking us first.
No long onboarding maze. Tell us what you build, get the SDK, and ship something real.
Reach out and say what you make and who you make it for, a connector, a delivery practice, or a market you know. A real person replies, and we figure out together which kind of partner fits.
We point you at the connector SDK and the envelope contract, and answer the real questions as they come up. You build against the same primitives we do, with no private fork and no special path.
Build a connector, stand up an operator, or land a customer. If it's governed, real, and explainable, it's ready, and we review it with you against the line every Fibric integration has to clear.
It goes in the marketplace where operators can find and install it, and where a fit exists, we co-sell. You keep what you built, and it grows as the platform does.
Tell us what you make and who you make it for. There's no form to game and no tier to climb into. A real person reads every note and replies, and we'll figure out the right way to build together.
Already building a connector? Start in the connector SDK guide and write to us when you have something to show. The best partnerships start with working code, not a pitch.