The questions that come up on every call.

Ngentix is a hosted integration platform. Software companies embed it so their own customers can connect the tools they already use — and those customers pay Ngentix directly, per flow. Ngentix Enterprise is a separate product: the same control plane, deployed standalone inside your own cloud account.

Self-serve access is opening shortly. Until it does, joining the early-access list is the way in: you get told the day it opens, and in the meantime we map your stack so the first flow is ready rather than starting from a blank page. Ngentix Enterprise engagements are running now and are not gated on that.

A flow is one source connected to one destination, kept live — the connection itself, monitored and repaired when the system on the other end changes, whether or not there is anything to move in a given month. Shopify orders into HubSpot is one flow; you add another flow for each pairing you need.

Ngentix Enterprise is the control plane deployed inside your own cloud account, standalone — built for MSPs, MSSPs, systems integrators and enterprises who need it running on their own infrastructure rather than ours. The engine discovers systems, builds self-healing connectors, governs agents, and keeps a tamper-evident record. Nearly 150 connectors already run in production, and counting. Ngentix Enterprise is priced per engagement.

Ngentix is $15 per flow per month, billed from the moment a flow is live — for keeping it running, watched, and repaired when the system on the other end changes, whether or not there is anything to move that month. Introductory pricing, subject to change. If you resell Ngentix to your own clients, the commercial terms are per engagement — see the MSP page. Ngentix Enterprise is priced per engagement.

When an upstream system changes its API — a field renamed, an endpoint moved, a version incremented — a normal integration breaks and someone gets paged. Ngentix Enterprise detects the drift automatically, re-infers the schema, remaps it to the Unified Data Model, rebuilds the connector, and re-tests it. You get a log entry, not a 2am incident. If it genuinely cannot resolve the change within its configured attempt budget, it escalates with a precise diagnostic.

Integrations are not hard to build — they are hard to keep. When a source system changes, everything downstream breaks, and engineers typically burn 20–30% of their capacity on keep-the-lights-on integration toil. Ngentix addresses that ongoing maintenance cost with connectors that repair themselves.

Traditional platforms treat integration as moving data through a pipe — they do not understand what flows through them, they break when systems change, and they need engineers to maintain them. Ngentix Enterprise understands the meaning of the data (via the UDM), heals itself when systems change, and acts as an operations control plane for partner fleets. The difference is architectural, not a feature that can be bolted on.

No. The connector lifecycle — discovery, schema inference, build, test, and self-healing — runs autonomously in Ngentix Enterprise. There is no proprietary transformation language to learn, and nothing to maintain by hand once a connector is built. Your engineers stay on product instead of becoming an integration maintenance team.

AI-native. MCP (Model Context Protocol) server, client, and gateway, plus A2A (Agent-to-Agent) are first-class parts of the core platform. Every connector the engine builds is automatically an MCP tool, grounded in the Unified Data Model so AI agents understand what they are touching — not just how to call an endpoint.

Ngentix Enterprise is built for MSPs, MSSPs, systems integrators, ERP/CRM consultants, and fractional CIO/CTO shops — and for the teams whose integrations keep breaking in ERP-heavy ecosystems like Workday, Sage Intacct, Acumatica, and NetSuite. If that’s you, Ngentix Enterprise deploys inside your own cloud account and is priced per engagement. If you are a software company who wants your customers to connect the tools they already use, the hosted platform is what you want instead — you pay nothing and your customers are billed per flow.

Authentication is delegated — credentials are provisioned by your team or your MSP and never embedded in generated code or written to logs. A built-in governance engine enforces policies on identity, resource, action, and condition across every connector call, MCP tool, and agent delegation, and produces an immutable, tamper-evident audit log of every action.

The Ngentix Enterprise engine is a self-contained runtime that runs inside your infrastructure, your client’s, or a partner’s — not a multi-tenant cloud you have to trust with your data. The first connector can be live in days, not the months a legacy deployment requires.