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.
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 Share menu sits next to the Deploy button in the top toolbar.
What to do next
- Release and deploy: deploy your first release and create its evaluation key
- Deploy a release and call it: the same path in the Runtime Cluster guide, up to the first call
- Impact Analysis: check what a new version changes before you deploy it