Skip to main content
Fused sits between the software making a call and the service being called. For every request it decides whether the call is allowed, resolves the credential, applies the policy, performs the provider interaction, and records what happened. Your product code stops carrying provider auth, retries, and pagination. Your agents stop holding credentials. Both get one consistent way in.

​
Two components

Registry

The catalogue. It turns an API description into a versioned service contract every team can inherit instead of working out again.

Engine

The runtime, in your infrastructure. Credentials, execution, policy, and event delivery stay inside it.
Registry defines and distributes integration knowledge. Engine applies and runs it inside your workspace boundary. Provider credentials, request payloads, and execution receipts stay with the Engine.

​
The four things you will work with

Workspace

Which services and versions your company has approved.

App (SDK)

A typed package holding only what one product needs.

MCP

An Engine-hosted server giving an agent scoped access across services.

Bucket

Where credentials live, and how they reach a call without reaching your code.

​
How a change reaches the Engine

Everything configurable is a file under .fused/, and every change goes through the same two steps.
The receipt binds an apply to that exact file content and that exact Engine. If the file changes, or you point at a different Engine, the apply is refused rather than doing something you did not review. An unchanged apply is a no-op. Immutable things behave accordingly: re-applying identical content to an existing app version changes nothing, and changing its scope returns app_version_immutable. You publish a new version instead of quietly rewriting the contract of software already in production.

​
Three credentials

Keeping these apart avoids most early confusion. Provider credentials never appear in a config file, a generated package, or an agent’s context.

Get an Engine running

Hosted or your own infrastructure. Everything else needs one.

Quickstart

Install the CLI and ship a working SDK.

​
Running this for a company

Everything on this site works on a Dev license, which is enough to build the whole thing end to end. What it is not is a production tier. Scale-up and enterprise teams get production licensing, SSO, and a support agreement. Tell us what you’re building and we’ll size it with you.