Registry defines and distributes the integration knowledge. Engine applies and runs it inside your workspace boundary. That is the whole architecture.
Registry is the company's one catalog of public APIs and private services: what they do, how to reach them, and which version you are actually on. Bring a service in once—from a spec, a live GraphQL endpoint, or just the provider docs—and every team inherits the answer.
Engine applies what Registry knows. It checks the call is allowed, resolves the credential, applies the policy, makes the request, and writes down what happened—for every application and agent, inside your infrastructure.
How the two fit together
Registry is where a service becomes something the company understands—operations, versions, auth requirements, what changed last week. Engine is where that understanding becomes a real call, with the credential resolved and the policy applied, close to your systems.
Product teams move fast without each of them having to carry the full weight of every integration.
Developers find what the company already supports and how to use it, instead of reconstructing the answer from an old branch and a Slack search.
Auth, retries, rate limits, pagination. Solved in the runtime rather than re-solved, slightly differently, in every product.
Applications, agents, and developers each get something shaped for their work—without the company ending up with three integration estates.
Let Fused host an isolated Engine, or run one yourself. Either way, every team starts from integrations the company already trusts.
Create account