Most integration pages count logos. We count what actually runs, and we show you the difference.
“Supports 200 integrations” can mean almost anything, and usually does. Tajo separates the claim into tiers with strict, verifiable definitions: what is live, what is in progress, and what is only in the catalog. The numbers below come from the connector registry. When they change, this page changes.
| Tier | Today | What it actually means |
|---|---|---|
| Live Brevo, Magento, and Stripe. | 3 | Verified with a run against the vendor's real API. Writes run only under the approved configuration, bound to its digest. |
| In progress Connectors with code in the runtime that are not verified yet. | 15 | Built or being built, not yet proven with a live run. We do not call these working until they are. |
| Discovery corpus API operations from the vendors' published specs that the agent drafts from. | 72 vendors / 14,293 operations | Not connections, drafting material. When your stack includes one of these vendors, the agent drafts against its real, documented API operations instead of guessing endpoints. |
| Catalog listed Entries in the integration catalog. | 179 | The roadmap surface: systems we have identified and scoped. A catalog entry alone moves no data, and we won't pretend otherwise. |
Tiers are ordered from most proven to broadest. Every integration, at every tier, runs under the same governance: digest-bound approvals, consent rules that fail closed and a tamper-evident audit log. See how it works for the full lifecycle.
Each tier is a strictly higher bar. Listing a system is easy; building a connector for it is work; proving it live against the vendor's real API is the most work of all. The ladder shows exactly where that work stands.
A connector counts as live only after a run against the vendor's real API proves it. Code alone, or a page in the catalog, does not count. That is why 3 of 179 qualify today. No integration carries a certified label today.
Early access partners set the order. If your stack needs a cataloged system built, or an in-progress connector proven live, that is precisely the forward-deployed work Tajo's agent and our team exist to do.
Because the alternative is the industry norm: a logo wall where a stale catalog entry and a battle-tested destination look identical until your project depends on the difference. Tajo's whole premise is verifiability — approvals you can check, runs that attest to what executed, audit trails that can't be quietly edited. A readiness page that inflated its numbers would be a strange front door for that product. This one doesn't.
Early access partners decide what gets built and proven live next. Tell us which systems you need connected, and we'll build toward them with you.