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 merely cataloged, what is registered in the governed runtime, what can read into a sync, and what can write as a sync or send destination. The numbers below are the platform's current, honest state. When they change, this page changes.
| Tier | Today | What it actually means |
|---|---|---|
| Write destination Brevo, Shopify, HubSpot, Salesforce, Pipedrive and Zoho CRM. | 6 | Connectors with a real write action used as a sync or send destination. Every write passes the runtime's gates: single-use, input-bound approvals and budget caps. |
| Reads into a sync Registered integrations that can read records into a sync. | 47 | Sources for a sync. Some also expose actions such as webhook creation, chat replies or POST endpoints that only read; those do not count as writes. |
| Registered Integrations registered in the live runtime. | 55 | Authenticated and executing under governance. Registration alone moves no records: the two tiers above say what each one can do. |
| Discovery corpus API operations from the vendors' published specs that the agent drafts from. | 27 vendors / 5,937 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. | 200 | 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, budget caps, 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; registering it in a governed runtime is work; reading its records into a sync is more work; writing to it as a destination is the most work of all. The ladder shows exactly where that work stands.
A connector counts only when it has a real write action used as a sync or send destination. Creating a webhook, replying in a chat or calling a POST endpoint that only reads does not count. That is why 6 of 55 qualify. No integration carries a certified label today.
Early access partners set the order. If your stack needs a corpus vendor registered, or a registered integration made a write destination, 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 registered and made writable next. Tell us which systems you need connected, and we'll build toward them with you.