---
title: "Integration Readiness | Tajo"
description: "An honest readiness matrix for Tajo integrations: what is cataloged, what is registered in the runtime, what reads into a sync, and what writes as a destination."
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.

Write destination

Write destination 6

Reads into a sync

Reads into a sync 47

Registered

Registered 55

Discovery corpus

Discovery corpus 27 vendors / 5,937 operations

Catalog listed

Catalog listed 200

“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](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; 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.

### What counts as a write

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.

### How a system moves up

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.

## 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 registered and made writable 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/)