What Loam does, in one page.
A scoped request becomes reviewed work. The decisions, findings, and open work then carry into the next session.
Four kinds of engineering judgment.
Each AI collaborator has a stable job, review pressure, and role-specific record. They work from the same current state and challenge the work from different angles.
Tests assumptions against source, keeps technical decisions legible, and asks for evidence before work advances.
Protects hierarchy, accessibility, spacing, and consistency, and holds work that has not been verified in the browser.
Turns a scoped plan into working code, explains trade-offs, and owns failures instead of talking past them.
Maps blast radius, checks claims against source, runs the verification gate, and records lessons for the next pass.
How memory actually works.
Learning-active sessions can add selected, source-tagged decisions, corrections, findings, and open work to the account-scoped record. A later session does not reload that record wholesale — it assembles a prioritized working set, while older entries remain available through recall.
Each specialist has their own memory store, scoped to their role. Carl’s memory is architectural — infrastructure decisions, hard-learned lessons, system relationships. Diana’s is visual — your design system, component patterns, spacing preferences. Anthony’s is practical — your codebase patterns, past bugs, what you’re currently building. Abish archives QA outcomes and blast radius maps.
You can clear a specialist’s memory, delete a project, or delete your account, including its reports and intake records. See Security for the remaining audio-file, backup, and infrastructure boundaries.
Autonomous delivery, not a longer prompt.
Build Mode is not a prompt that tells the team to work harder. It’s a structured loop where Anthony builds, Abish reviews, Carl approves or redirects, and the team iterates until the milestone is done — across multiple sessions if needed.
Hosted servers, set up by Loam.
When your arrangement with Loam includes hosting, a Loam administrator can set up a Lightsail instance, static IP, firewall rules, Cloudflare DNS, and an SSL certificate for your project in Loam’s own AWS and Cloudflare accounts. Customer accounts cannot start provisioning themselves today.
Direct the work. Get on with your day.
Call Meg at the front desk with the result you need. She verifies you, reads back the request, and confirms what the team will deliver. Order a document, research brief, deck, spreadsheet, email draft, web page, website, calendar file, callback, a research paper about your application, or a dev meeting to plan a change.
The finished work arrives by email. For a dev meeting, a team member calls at the time you name and walks you through the plan. You can show the team photos during a call, request a revision to delivered work, or email the team from your registered address. A fresh application review needs a new order. 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.
Meet the Team opens a conversation with all four AI collaborators; Conference Call focuses on one project. Your quiet-hours setting controls whether the team can call or text outside normal hours.
Three steps and you have a team.
Install the Loam extension from the VS Code Marketplace, connect the MCP server, then open a project and start a session. The team is briefed and ready, and the record can start building from your first session. Get started includes a first-hour exercise that shows it working.