Pricing
What Loam costs, and what it doesn’t cover.
USD $499 per user, per month
Model usage on provider accounts you control is billed by that provider, separately from Loam. Loam is in limited access, so every account starts with a conversation about the work.
One delivered outcome
A defined request, reviewed and delivered.
Visitors needed a clearer way to get access and install Loam. The team took that work through a completed milestone on Loam’s own site:
- Define the result. Visitors can tell whether they can install and how to request access. The milestone records those acceptance criteria before the work is judged.
- Deliver the work. Four clear access routes, installation prerequisites, and consistent installer verification details across two public pages.
- Check it and put it live. Separate QA, security and desktop/mobile sign-offs, and a live release recorded on June 21, 2026.
Inspect the milestone, acceptance checks, and release record →
Condensed evidence from Loam’s own site work. The record is redacted and carries dated corrections where installation guidance changed later. Use your pilot to measure the value of reviewed, delivered work in your own process.
Included
What you receive.
- The editor workflow. The Loam extension for VS Code, free on the Marketplace, and the signed installer. Development meetings, troubleshooting, code review, and Build Mode, with four role-specific AI working contexts.
- Codex, when you choose it. Off by default. Hand one task to Codex from inside a session; Loam writes the assignment, Codex returns the commit and its evidence, Loam reviews it and keeps deployment. First use checks the install, the sign-in, the pairing and a short test reply before anything is sent. Codex access and usage through customer-controlled provider accounts are separate; the Loam subscription does not include those charges.
- The engineering record. Selected decisions, corrections, findings, and open work saved to your account and carried into later sessions.
- Reception, by phone or email, from your registered phone number and email address. Order documents, slide decks, spreadsheets, email drafts, web pages, multi-page websites, calendar files, a research paper about your application, or a dev meeting with a verdict and plan. Send photos during a call, request revisions, and arrange a walkthrough of your dev meeting. See what you can order and what arrives.
- The documentation a review needs. Security, For IT, and the Proof Packet describe what is stored, where it is stored, and how it is removed.
Limits
What is limited today.
- Build Mode pauses after five milestones in one session. Resume the build to continue the plan.
- Memory is per user. Shared organizational memory is not shipped.
- One seat covers every client you work for. What the team learns on one of your projects comes with you to the next; nothing crosses into another customer’s account.
- Code changes by phone are available: a verified caller confirms the change, the team makes it on the project connected through GitHub, and it goes online through the steps you approved for your own server or, if your project already publishes itself from GitHub, through that. Saved and live are reported separately. See what Loam can do today. A dev meeting delivers the verdict, scope, and plan; it does not implement the change. Code reviews are read-only and require a new order for another review.
- Three kinds of hosting, by name. Loam-managed hosting: Loam administrators set up servers in Loam’s AWS and Cloudflare accounts when your order includes it. Publishing to your own server: connect a server you already have in Settings, under Servers, and approve each project’s steps once. Provisioning in your own cloud account is not available today. See what Loam can do today.
- No self-service export, retention settings, or customer-facing audit log. For IT lists these gaps, and Security lists what account deletion removes.
Other costs
What can cost extra, and who bills it.
| Cost | Who bills it | When it applies |
|---|---|---|
| Claude Code in your editor | Anthropic, on the developer’s own Anthropic account | Whenever you work in an editor session |
| Loam’s server-side model work | Loam during an active trial. After the trial, it runs on your Anthropic API key, and Anthropic bills you. | Once your trial ends |
| Image generation in Build Mode | Loam. You do not configure or pay for a Gemini key. | Only when enabled |
| Hosted servers | Priced in your plan or order form | Only if your order includes hosting |
| Your own server, if you connect one | Your hosting provider, under its own terms | Only if you publish to your own server |
| Anything bought directly from a provider | That provider, under its own terms | Outside Loam |
Loam does not store your payment card. Billing runs through a payment processor, and Loam keeps only a customer reference.
Terms
Billing terms in one place.
- Before you agree to a paid plan or order, you see its price, billing cycle, renewal, and cancellation terms.
- You can cancel at any time. Access continues through the end of the paid period.
- Except where the law requires otherwise, fees are non-refundable.
The full text is in the Terms.
Pilots
Put the pilot in writing before it starts.
A pilot is only useful when both sides agree on what it covers and how it will be judged. Settle these before day one:
- Who is in it, and for how long.
- What it costs, including whether hosted servers are part of the order.
- Which Anthropic account pays for model usage after any trial.
- Which workflows are in scope: editor sessions, Build Mode with a linked repository, and phone workflows.
- What Build Mode may push, and to which branch. What starting Build Mode authorizes.
Then judge it against your current process: time to resume work, accepted output, review findings that reach a final disposition, rework, and the quality of the handoff evidence.