CompanyFabric vs LLMGateway
LLMGateway leads with open-source self-hosting and a hosted tier on top. CompanyFabric leads hosted-first and covers media models and agents, not just chat — with the SDKs, MCP server, provider adapters, and every starter template open under Apache-2.0.
The differences
Side by side
| CompanyFabric | LLMGateway | |
|---|---|---|
| Open source | SDKs, MCP server, adapters, and all templates (Apache-2.0); the hosted gateway is the product | Open-core gateway from the start |
| Modalities | Text + image + video + audio, one balance | Chat-completions centric |
| Payments | Credits, or BYOK at 0% platform fee | Credits / keys, depending on tier |
| Agents | Hosted agents as metered endpoints | Not a product surface |
Verdict
Which should you pick?
Self-hosters who need the gateway itself open will prefer LLMGateway. If you want one balance across text and media, or agents behind the same key, CompanyFabric is the shorter path — and everything you integrate with (SDKs, MCP, templates) is open.
FAQ
Frequently asked questions
Is CompanyFabric open source?
The integration layer is: SDKs, the MCP server, provider adapters, and every starter template ship under Apache-2.0, with no hard lock to our endpoint — the base URL is always an env var. The hosted gateway is the product; a minimal self-host proxy is something we'll evaluate if real demand appears.
One key. Every model. Exact prices.
Migrating from LLMGateway is a base-URL change. Free starter credits included — no subscription required.