Skip to main content
Once you have built and tested your Blueprints, you deploy a release of your project to a runtime cluster. The runtime cluster runs the release, and other systems call its public Blueprints over REST, MCP, or n8n. On Leapter Cloud, Leapter runs the runtime cluster for you.

From the editor to production

1

Deploy

Click Deploy in the top toolbar of the editor. The dialog creates a release of the version you have open and deploys it to an environment of the runtime cluster. The changes you keep making in the editor don’t reach callers until you deploy again.
2

Call

Callers send an evaluation key with every call. On Leapter Cloud, the Deploy dialog creates the first key and shows the call for curl, MCP, and OpenAPI. See Create the evaluation key and call a Blueprint.
3

Monitor

The Admin UI of the runtime cluster lists the runs of your project and its usage. See Find a run and read usage. Before you deploy a change, Impact Analysis replays production runs on the new version.
The Lab’s old run addresses (https://lab.leapter.com/runtime/…) were retired and answer with HTTP 410. If an integration still uses one, deploy the project and reconnect the integration with the new address and an evaluation key. On Leapter Cloud, the Admin UI is at https://runtime.leapter.com/runtime-management/ui.

Call your Blueprints

The Runtime Cluster guide describes each way to call a deployed release:

The Share menu

The Share menu in the top toolbar shares your logic without running it:
The top toolbar with the buttons Design, Deploy and Share. The open Share menu lists Code, Embed, PNG, Export and Link.

The Share menu sits next to the Deploy button in the top toolbar.

What to do next