Most integration pages count logos. We count what actually runs — and we show you the difference.
“Supports 199 integrations” can mean almost anything, and usually does. Tajo separates the claim into tiers with strict, verifiable definitions: what is merely cataloged, what is wired into the governed runtime, what can safely write, and what is certified end to end. The numbers below are the platform's current, honest state. When they change, this page changes.
| Tier | Today | What it actually means |
|---|---|---|
| Certified destination Brevo, with 7 typed targets. HubSpot is the emerging second destination. | 1 (+1 in progress) | The full governed lifecycle is proven end to end: typed write targets, approval gates, attestation, and audit — an integration you can publish and run against production today. |
| Write-capable Runtime integrations with at least one write action. | ~19 | These can perform writes through the runtime's gates — single-use, input-bound approvals and budget caps included — but haven't earned the certified label across every target yet. |
| Runtime-wired Integrations connected in the live runtime. | 53 | Authenticated and executing under governance. Many are read-oriented: good for discovery, sampling, and drafting; writes arrive as they pass the gates. |
| Discovery corpus Documented API operations the agent drafts from. | 27 vendors / 10,345 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. | 199 | 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; wiring it into a governed runtime is work; proving safe writes is more work; certifying every target end to end is the most work of all. The ladder shows exactly where that work stands.
A certified destination means every typed target has been exercised through the whole lifecycle — draft, validation, digest-bound approval, attested execution, audit. We certify one destination at a time, properly, rather than stamping the label across the catalog.
Early access partners set the order. If your stack needs a corpus vendor wired, or a wired integration made write-capable, that is precisely the forward-deployed work Tajo's agent — and our team — exists 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 wired and certified next. Tell us which systems you need connected, and we'll build toward them with you.