Overall AI readiness score
A combined result across all audit signals.
Overall AI readiness score
A combined result across all audit signals.
Lemma is a runtime for software built by coding agents: the agent writes the app, and Lemma provides a pod with durable tables, files, functions, agents, workflows, permissions and apps so a team can operate it. It targets teams running back-office loops such as support triage, lead qualification and onboarding, and can be reached through Slack, ChatGPT, Claude, Telegram, WhatsApp, email or a purpose-built app. It is open source (AGPLv3 core, Apache-2.0 SDKs) and runs locally, on your own server or on Lemma Cloud.
Written by AI from the site’s llms.txt and homepage.
Overall AI readiness assessment
Lemma was independently audited by llmsmap. lemma.work currently scores 80/100 for AI readiness. The result combines AI-specific files, crawler policy, sitemap discovery, structured homepage data, and—when available—the mobile Google Lighthouse technical profile.
llms.txt is accessible and contains 730 tokens. No accessible llms-full.txt was detected, so deeper context still has to be assembled from regular pages. No separate ai.txt policy was detected; it is optional, but can clarify training, retrieval, and attribution preferences.
robots.txt is available. 11 of 11 tracked AI bots are not blocked. Declared sitemaps: 1. The homepage exposes Schema.org types Organization, WebSite; 7 OpenGraph tags were found and markup completeness is 80%.
The Google Lighthouse measurement is still collecting. Once complete, performance, accessibility, technical quality, SEO, and experimental browser-agent signals will be added with a limited weight.
The background queue is collecting mobile Performance, Accessibility, Best Practices, SEO, and experimental browser-agent signals.
Machine-readable files, crawler policy, discovery, and homepage markup.
Full version was not found
ai.txt file was not found
1 sitemap found
Types: Organization, WebSite
7 OG tags found
Based on robots.txt analysis
Declared discovery routes for crawlers and agents.
Social preview metadata found on the homepage.
og:titleLemma — Hire an AI teammateog:descriptionHire an open-source AI teammate and share it with your people. It learns from all of you, builds the tools the job needs, and answers each person within their permissions.og:urlhttps://lemma.workog:image:width1200og:image:height630og:typewebsiteStructured entities and properties exposed on the homepage.
nameLemmaurlhttps://lemma.workdescriptionLemma is the runtime for agent-built software: a coding agent writes the app, and Lemma gives it a pod so a whole team can use it.logohttps://lemma.work/icon-192.pngsameAshttps://github.com/lemma-workcontactPointhttps://lemma.work/contactlegalNameFolks and Machines, Inc.publisher{"@id":"https://lemma.work/#organization"}# Lemma > Lemma is the runtime for agent-built software: a coding agent writes the app, and Lemma gives it a pod — durable tables, files, functions, agents, workflows, permissions, and apps — so a team can run it, not just the person who prompted it. Open source (AGPLv3 core, Apache-2.0 SDKs). Runs on your own machine, your own server, or Lemma Cloud. ## When to use Lemma - Turning a coding agent's output into something a team can operate day to day: support triage, lead qualification, expense review, onboarding, launch tracking, and similar back-office operating loops. - Giving an agent durable state (tables, files) and deterministic actions (functions) instead of re-deriving everything from chat history on every run. - Reaching one system from wherever the work already happens — Slack, ChatGPT, Claude, Telegram, WhatsApp, email, or a purpose-built app — under one permission model, instead of copies of the data forking per surface. - Calling a product programmatically: the SDKs and CLI are the primary integration path, not a UI meant only for humans. - Skip Lemma for a single-session chat agent with no persistent state, no team of users, and no automation beyond that one conversation — that is simpler done directly against a model provider. ## Docs - [Documentation](https://lemma.work/docs): platform concepts, SDK reference, CLI reference, and build guides. - [Quickstart](https://lemma.work/docs/getting-started): create an account, run Lemma locally or in the cloud, install the CLI, and create a pod. - [Overview](https://lemma.work/docs/overview): the mental model — pods, tables, files, functions, agents, workflows, apps. - [SDK Installation](https://lemma.work/docs/sdk/installation): install and configure `lemma-sdk` (TypeScript) or `lemma-sdk` (Python). - [SDK Core Client](https://lemma.work/docs/sdk/client): the LemmaClient namespace map. - [CLI Overview](https://lemma.work/docs/cli/overview): command groups and global options for `lemma-terminal`. ## API - [OpenAPI spec](https://lemma.work/openapi.json): the full Lemma Cloud API surface, one operationId and description per operation. - [Auth and Context](https://lemma.work/docs/cli/auth-and-context): authenticate the CLI and inspect org/pod context. - [React Auth and Pod Access](https://lemma.work/docs/sdk/react-auth): AuthGuard and pod-access hooks for app frontends. ## Optional - [About](https://lemma.work/about): who makes Lemma. - [Contact](https://lemma.work/contact): support, security, sales, and privacy contacts. - [Privacy](https://lemma.work/privacy) - [Terms of Service](https://lemma.work/tos) - [Changelog](https://lemma.work/changelog): every release, newest first. - [Blog](https://lemma.work/blog) - [GitHub](https://github.com/lemma-work/lemma-platform): source, issues, and the license split. - [Discord](https://discord.gg/x2NVyNPQR): talk to the team and other people building with Lemma.
Sites with a close AI-readiness score — compare how they set up llms.txt and markup.