Fused is available by license. Request access →
The runtime in your infrastructure

Run the integration gateway in your world.

The licensed Fused Engine runs close to your products and data. It handles credentials, API calls, MCP sessions, and webhook traffic inside the environment you operate.

Request access View Engine source
Source-available and licensed. A Fused license key and Registry connection are required to run it.
Clusters of applications use Capability SDKs and agents use MCP servers. Fused Engine resolves policy and credentials inside the customer's infrastructure before calling external services.APPLICATIONSAGENTSPRODUCT INTERFACECapability SDKtyped calls + incoming eventsAGENT INTERFACEMCP serversearch_docs + executeFUSED ENGINEResolve the request.Apply workspace policyResolve identity + credentialsExecute close to your systems● RUNNING ON YOUR SIDEEXTERNAL SERVICES

Inside the Engine

The runtime behind each request.

A few layers keep access predictable without leaking integration concerns into every product that needs them.

01Workspace contractServices, versions, and the policies this Engine is allowed to run.
02Buckets: the context walletKeys, variables, and connected users held together for an Artifact to use.
03Credential resolutionThe credential selected by the Artifact is resolved only after the request is approved.
04Local executionProvider calls and agent scripts run through the Engine in your infrastructure.
05Reliable eventsIncoming events are verified, queued, and delivered to the SDK that selected them.

The Artifact chooses the context.

Artifact configuration selects the Bucket for a request. The Bucket simply holds its keys, variables, and connected users—like a wallet the Engine opens at execution.

Credentials arrive at the last responsible moment.

Applications and agents send intent. Engine resolves and injects the configured credential when it makes the approved provider call.

Your runtime remains your boundary.

API payloads, MCP execution, and webhook traffic stay in the infrastructure where you deploy Engine.

CONTROL IT AS CODE

fused-cli keeps the runtime reviewable.

Point it at your Engine, review a plan, and apply workspace, SDK, MCP, webhook, and Bucket configuration from the terminal.

Download fused-cli See config as code
Source-available, licensed to run.

You can inspect the Engine source. Commercial or production use requires a Fused agreement and license key, and Engine requires its Registry handshake to start.

View Engine source

Configuration as code

Your integration layer belongs in the repo.

Describe the workspace and the interfaces your products need in reviewable YAML. fused-cli shows the change before it applies anything to Engine.

apiVersion: fused/v1
kind: workspace
services:
  linear:
    versions:
      - version: "v1"
  slack:
    versions:
      - version: "v2"
WORKSPACE CONFIG

Plan it. Review it. Apply it.

Choose the services and versions this workspace can use. Engine resolves the plan into local runtime state before anything changes.

From your terminalfused-cli workspace plan && fused-cli workspace apply
Credentials stay out of these files and resolve from Buckets inside Engine.Download fused-cli

How it fits

The gateway runs where your integration traffic lives.

01

Install the Engine

Run the licensed binary or container in the environment your team operates.

02

Connect your workspace

Use the CLI to apply service access and the right credential context.

03

Run the request

Call providers, execute agent operations, and receive events close to your systems.

Run Fused Engine in your infrastructure.

Request access to receive your Fused license key, then deploy Engine close to the products, credentials, and integration traffic it serves.

Request a license key