---
title: "Integration Readiness | Tajo"
description: "An honest readiness matrix for Tajo integrations: what is live, what is in progress, and what is only in the catalog."
url: https://tajo.io/integration-readiness/
markdown: https://tajo.io/integration-readiness.md
lang: en-US
alternates: {bg-BG: /bg/integration-readiness.md, cs-CZ: /cz/integration-readiness.md, de-DE: /de/integration-readiness.md, da-DK: /dk/integration-readiness.md, es-ES: /es/integration-readiness.md, fr-FR: /fr/integration-readiness.md, el-GR: /gr/integration-readiness.md, hr-HR: /hr/integration-readiness.md, hu-HU: /hu/integration-readiness.md, it-IT: /it/integration-readiness.md, ja-JP: /jp/integration-readiness.md, ko-KR: /kr/integration-readiness.md, ar-SA: /ar/integration-readiness.md, nl-NL: /nl/integration-readiness.md, no-NO: /no/integration-readiness.md, pl-PL: /pl/integration-readiness.md, pt-BR: /pt/integration-readiness.md, ro-RO: /ro/integration-readiness.md, ru-RU: /ru/integration-readiness.md, sv-SE: /se/integration-readiness.md, zh-CN: /zh-cn/integration-readiness.md, sl-SI: /sl/integration-readiness.md, sr-Latn-RS: /sr/integration-readiness.md, th-TH: /th/integration-readiness.md, tr-TR: /tr/integration-readiness.md, ur-PK: /ur/integration-readiness.md, vi-VN: /vi/integration-readiness.md, sk-SK: /sk/integration-readiness.md}
---

# Integration readiness, stated plainly

Most integration pages count logos. We count what actually runs, and we show you the difference.

Live

Live 3

In progress

In progress 15

Discovery corpus

Discovery corpus 72 vendors / 14,293 operations

Catalog listed

Catalog listed 179

“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](https://tajo.io/how-it-works/) for the full lifecycle.

## Reading the matrix

### Why the numbers shrink as you go up

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.

### What counts as live

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.

### How a system moves up

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.

## Why we publish it this way

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.

## Need a tier moved for your stack?

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.

## This page as Markdown: [integration-readiness.md](https://tajo.io/integration-readiness.md)

Loading Markdown…

[Open in Claude](https://claude.ai/new) [Open in ChatGPT](https://chatgpt.com/)