Managed, Multi-Tenant
Logical isolation per tenant, continuous updates, and nothing of your own to operate.
New: Introducing the Lemma MCP Server, and what we learned building it.New: Introducing the Lemma MCP Server. Read the blog post
Run Lemma where your policy says: managed, multi-tenant or single-tenant; in your own AWS, Google Cloud or Azure account; or on-premises in your data center, air-gapped where required. The Worker you design is the same in every one, so each workload runs where its data lives.
Run Lemma managed by Thread AI, in your own cloud account or on-premises, and place each workload where its data and its policy require. The Worker you design moves between them unchanged, each tenant stays in the region you pin it to, and the secrets it uses are encrypted under a key of its own.
Host Lemma the way your policy calls for: managed by Thread AI, shared or dedicated, or inside your own cloud account or data center. The same Worker design carries across all four.
Logical isolation per tenant, continuous updates, and nothing of your own to operate.
Dedicated infrastructure and configuration, upgraded in a window agreed with your team.
Deployed in your own AWS, Google Cloud or Azure account.
Your own data center, air-gapped where required.
One organization can hold several tenants, isolated workspaces in different supported regions. Each is pinned to one region when it is created, and that region is where its data is stored and where its Workers run. A company can run a US tenant and a European one under the same organization, and anyone with access to both switches between them in the Console.
Connect functions and sources with your organization’s own provider accounts, or start with Lemma Credentials, managed credentials, where a supported function allows it, without opening a separate provider account.
functions and sources connect with your organization’s own provider accounts and credentials.
Managed by Thread AI for supported functions, with no provider account to open.
Each tenant’s stored credentials and secrets are encrypted under a key of its own, and that key is itself encrypted before it is stored. The signing secrets for incoming webhooks are protected the same way, each under its own tenant’s key.
Buy Lemma through Google Cloud Marketplace, or through an enterprise private offer on the Microsoft Azure Marketplace. For AWS Marketplace procurement, contact us and we will work through it with your team.
Start managed, where it is fastest, and run each workload in your own cloud or data center as policy requires. The Worker is the same wherever it runs, and so is the record it leaves.
Walk through the deployment models with our team.
Request a Demo