# Inferrex

> Self-healing integration infrastructure. Connect any API, map any data, heal any breakage — automatically. Cloud, enterprise, sovereign, or air-gapped.

## Main

- [Inferrex — Self-Healing Integration Infrastructure](https://inferrex.com/): Connect any API, map any data, heal any breakage — automatically. Cloud, enterprise, sovereign, or air-gapped.

## Pages

- [Functionality](https://inferrex.com/functionality): Schema inference, AI pipeline, pipeline graphs, sync tiers, self-healing, archival, intelligence, and developer tooling.
- [Technical](https://inferrex.com/technical): Kubernetes-native microservices, multi-provider AI with failover, seven API protocols, and four deployment modes.
- [Compliance](https://inferrex.com/compliance): Inferrex classifies the regulations that apply to your data the moment you connect — GDPR, PCI-DSS, HIPAA, SOX and 150+ more across 59 jurisdictions.
- [Pricing](https://inferrex.com/pricing): Capacity-based pricing. Every feature included. Unlimited users. No per-connector charges.
- [Compare](https://inferrex.com/compare): Inferrex vs MuleSoft, Boomi and Workato — AI schema inference and self-healing versus manual mapping and breakage.
- [The Corpus](https://inferrex.com/corpus): The provider intelligence corpus that powers Inferrex inference, classification, and self-healing.
- [About](https://inferrex.com/about): Inferrex is the lingua franca of business data: a comprehension layer that reads every system, reconciles the dialects, and lets them communicate through one governed, traceable view.
- [The Lingua Franca](https://inferrex.com/lingua-franca): The Inferrex Lingua Franca: why integration is a comprehension problem, and how a shared, governed layer that understands every dialect ends it.
- [Manifesto](https://inferrex.com/manifesto): How Inferrex operates — the operating doctrine behind the product. One version, public and internal: radical transparency, trust first, integrity over growth.
- [Partners](https://inferrex.com/partners): Partner with Inferrex — referral, delivery, and OEM models for the self-healing integration layer.
- [Founder](https://inferrex.com/founder): Why Aaron Gammon built Inferrex.
- [Claims & Stats](https://inferrex.com/claims): Every numeric claim on this site, sourced and dated, with live pipeline status.
- [See It Work](https://inferrex.com/demo): Watch Inferrex infer a schema, build a golden record, and heal a breakage.
- [Contact](https://inferrex.com/contact): Talk to us about Inferrex Cloud, Enterprise, or Sovereign.

## Developer docs

- [Developer Docs](https://inferrex.com/docs): Build on Inferrex — REST API, TypeScript SDK, and MCP server over the self-healing integration layer.
- [Quickstart](https://inferrex.com/docs/quickstart): From an API URL to flowing data in TypeScript: infer a schema, approve it, wire a pipeline, sync.
- [API Reference](https://inferrex.com/docs/api-reference): Every customer-facing Inferrex API endpoint, generated from the live route definitions — base URL, auth, and each resource group.
- [API Changelog](https://inferrex.com/docs/api-changelog): Dated, reverse-chronological record of every change to the customer-facing Inferrex API — also published machine-readable at /api-changelog.json.
- [TypeScript SDK](https://inferrex.com/docs/sdk): The @inferrex/sdk typed client: install, authenticate, resource groups, error handling.
- [MCP Server](https://inferrex.com/docs/mcp): Connect Claude, Cursor and other agents to Inferrex with the @inferrex/mcp Model Context Protocol server.

## Insights

- [Insights](https://inferrex.com/insights): Long-form writing from Inferrex on data, government, AI, and why comprehension has to come before integration.
- [The State Cannot See Itself](https://inferrex.com/insights/the-state-cannot-see-itself): British government does not have a technology problem; it has a comprehension problem. The recurring cost, in the low tens of billions a year, of a state that cannot reconcile its own data.
- [Comprehension Over Connection](https://inferrex.com/insights/comprehension-over-connection): The integration industry spent twenty years getting better at connecting systems. That was the wrong problem. Connection scales linearly and breaks constantly; comprehension compounds.
- [The N×N Problem](https://inferrex.com/insights/the-nxn-problem): Why every connector-catalogue platform collapses under its own count: connections wanted grow as the square of the systems, connectors built by hand grow in a line, and the gap is permanent.
- [A Lingua Franca for Business Data](https://inferrex.com/insights/lingua-franca-for-business-data): A lingua franca is not a translator between two systems; it is a shared language above all of them. Why that distinction is the difference between a connector catalogue and a comprehension layer.
- [Why Everyone Can Be Different](https://inferrex.com/insights/everyone-can-be-different): Most integration platforms demand conformity to one schema — and conformity is the thing that breaks. The model that survives reality adapts to difference instead of abolishing it.
- [What Self-Healing Integration Actually Means](https://inferrex.com/insights/self-healing-integration): Retries, alerts, auto-reconnect and dashboards are not self-healing. Real self-healing detects that the provider changed, re-understands the new surface, and repairs the mapping itself.
- [The Hidden Cost of Brittle Integrations](https://inferrex.com/insights/hidden-cost-brittle-integrations): The visible cost of a broken integration is the smaller half. The larger half is invisible: silent bad data, the interruption tax, and the roadmap features that quietly never got built.
- [Inferring API Structure](https://inferrex.com/insights/inferring-api-structure): The interesting capability is not connecting a known API; it is reading one nobody built a connector for. How a system reads an unfamiliar API and turns raw structure into business meaning.
- [Sovereign Integration Infrastructure](https://inferrex.com/insights/sovereign-integration-infrastructure): Why integration infrastructure with zero external dependencies — your hardware, your bundled models, no external calls — has become a board-level requirement for defence, finance, and government.
- [Air-Gapped Doesn’t Mean Crippled](https://inferrex.com/insights/air-gapped-not-crippled): Air-gapped editions are usually crippled because most AI is a call to an external model. If you own your models and run them locally, air-gapping changes nothing — the capability survives the isolation.
- [From AI SaaS to Critical National Infrastructure](https://inferrex.com/insights/saas-to-critical-infrastructure): A class of software is crossing from application you can swap to infrastructure a country depends on. When it crosses, how it is built, bought, and governed all change — and most vendors have not noticed.
- [Data Sovereignty for Regulated Industries](https://inferrex.com/insights/data-sovereignty-regulated-industries): A practical framework: what data sovereignty actually means, the five questions a regulated buyer must answer, and why the integration layer is the processor most often missed in the review.
- [How One Person Built Production-Grade Infrastructure](https://inferrex.com/insights/one-person-production-infrastructure): A self-taught salesperson built a sixteen-service production platform solo. Not by prompting a chatbot, but by pairing AI leverage with ruthless engineering discipline — and what that says about who gets to build.
- [Building a Self-Sovereign AI Training Loop](https://inferrex.com/insights/self-sovereign-ai-training): Why we improve our models without distilling from frontier providers: a closed loop fed only by our own corpus and human corrections, so quality keeps improving with no line to the outside world.
- [Why We Built Our Own AI Layer](https://inferrex.com/insights/own-ai-layer): Wiring in a frontier API hands you three dependencies you do not control and one wall you can never pass: you cannot air-gap a product that has to call out to a cloud model. Why we own the layer instead.
- [Embedded Integration Infrastructure](https://inferrex.com/insights/embedded-integration-infrastructure): The Stripe-for-data-integration model: embed one integration-infrastructure partner and every tool becomes connectable and self-healing — turning your biggest churn driver into your strongest retention mechanism.
- [Inferrex vs Traditional iPaaS](https://inferrex.com/insights/inferrex-vs-ipaas): An honest, capability-for-capability comparison — including where the incumbents are genuinely stronger. Traditional iPaaS is a mapping tool; Inferrex is a comprehension layer, and that drives everything else.
- [What’s Inside an API Schema Corpus](https://inferrex.com/insights/api-schema-corpus): A big corpus number means nothing on its own. What matters is depth, normalisation into one canonical model, and compounding — and why a deep API schema corpus is a moat you cannot scrape your way to.

## Legal

- [Terms of Service](https://inferrex.com/legal/terms): Inferrex terms of service.
- [Privacy Policy](https://inferrex.com/legal/privacy): Inferrex privacy policy.
- [Data Processing Addendum](https://inferrex.com/legal/dpa): Inferrex data processing addendum.
- [Cookie Policy](https://inferrex.com/legal/cookies): Inferrex cookie policy.
- [Acceptable Use Policy](https://inferrex.com/legal/acceptable-use): Inferrex acceptable use policy.
- [Subprocessors](https://inferrex.com/legal/subprocessors): Inferrex subprocessors.

## API

- [OpenAPI specification](https://inferrex.com/openapi.json): The complete machine-readable contract — every endpoint, parameter, response, example, auth scope, rate-limit table, webhook catalogue, and error shape. Credential-free.
- [Interactive API reference](https://inferrex.com/docs/api-reference): The spec rendered with try-it. https://inferrex.com/v1/pricing is also public + keyless.
- [Quickstart](https://inferrex.com/docs/quickstart): Authenticate and make your first call.
- [TypeScript SDK](https://inferrex.com/docs/sdk): Typed client, 1:1 with the API.
- [MCP server](https://inferrex.com/docs/mcp): Native Model Context Protocol tools for agents.