Draw It. Ask for It. Write It.One Worker, Any Way.
Build a Worker where you already work: on the canvas in the Console, from your own coding agent through the Lemma MCP server, in Python or TypeScript with the SDKs, or from the CLI and Terraform in your pipeline. Every way edits the same Worker.
Build Where You Work.
On the canvas, from a template, in a conversation beside it, in your own coding agent, in code or in your pipeline: every way builds the same Worker, and every revision runs on the same governed runtime.
Build visually in the Console.
Lay out the work as steps and connect them in the order it runs. Add an action from your catalog and map its inputs, route each case by what it found, and add an approval where a person decides. Test a run before you publish. Every other way to build edits the same workflow you see here.
- Steps, connected
- Each step is a block on the canvas; connect them in the order the work runs.
- Actions, configured
- Add an action from your catalog and map its inputs from what came before.
- Decisions and approvals
- Route each case by what it found, and send a decision to a person or a team.
Start from a template.
Skip the blank canvas. Pick a workflow that is already built from the template gallery, give it a name, and it opens as your own draft with every step in place. Connect your accounts, change what you need, then publish. Any workflow your team builds can become a template for everyone else.
- A working start
- Begin from a workflow that already runs, not a blank canvas.
- Yours to change
- It opens as your own draft: connect your accounts and edit any step.
- Shared with your team
- Turn any workflow into a template everyone can start from.
Build with the Lemma Assistant.
Describe the change you want in plain language. The Assistant makes it in the workflow you have open, checks that it works, and shows you the result on the canvas. Nothing goes live until you publish it.
- Works on the draft you have open
- Finds what it needs in your catalog
- Makes the change and checks it
- Shows the result on the canvas
- Leaves publishing to you
Build with your own AI coding agent.
Connect Claude Code, Codex or another supported coding agent to the Lemma MCP server, and sign in from your browser. From that agent’s session, build a Worker, publish a revision, run it, and inspect the result, without leaving the tool you already use.
- One server, many agents
- Claude Code, Codex CLI, GitHub Copilot CLI and Google Antigravity connect to the same MCP server.
- Signed in as you
- The agent works with your access, and asks you before it publishes.
- Build to result
- Create the Worker, publish a revision, run it and read what it did.
Build in code with SDKs and the REST API.
Define Workers in Python or TypeScript with the Lemma SDKs, keep the definitions in Git beside the rest of your code, and use the REST API to start a Worker from your own application with an API key.
- Python and TypeScript
- Workers defined in code
- In Git
- Reviewed like any change
- REST API
- Invoke from your own app
Automate delivery with the CLI and Terraform.
Use the Lemma CLI to validate a workflow file, push it as the Worker’s draft and publish it, from your terminal or your pipeline. Use the Terraform provider to declare the supported Lemma resources and review each plan before you apply it.
- Validate
- Push the draft
- Publish
- Terraform plan
- Review, then apply
Where You Work,One Worker.
The canvas, a conversation, your coding agent, your repository and your pipeline all build the same Worker, and each revision runs on the same governed runtime, whoever or whatever made the change.
Build Your First Worker.
See every way to build with our team.
Request a Demo