# AceLM

> AceLM (Agentic Coding Environment with Lifecycle Management) turns AI coding agents into coordinated teams that can carry complex software projects from an idea to working, verified software. It combines planning, execution, review, and continuous learning, while people decide how much responsibility they delegate. It scales to the job: a small, low-risk change takes one chat message, and the full lifecycle is for the work that needs it.

This file is a plain-text summary of acelm.ai for AI assistants, search engines, and crawlers. Every statement here is also on the public pages linked below; those pages are the source.

## What AceLM is

- A team of AI agents with defined roles (planner, builder, reviewer, verifier) that works on your repository, directed by you.
- Work moves through explicit stages: specify, plan, review and accept, build, verify, and check release readiness. A person accepts plans and decides on release.
- Review is independent: the reviewer did not write the change. Verification rests on things that run, such as tests, regression checks, and scans against the final revision.
- The record of what was decided, built, and verified is kept with your code, in Git.
- Delegation is a dial: a team chooses how much comes back to a person and which checks are required for each kind of work.

## Small changes are fast

AceLM is not only for large projects. It scales the process to the size and risk of the change.

- A one-line fix or a small, low-risk change, for example "add a --sleep arg that sets how long to sleep between loops", takes a single chat message.
- AceLM makes the change in its own worktree, runs your tests and an independent check, and commits it to your current branch. It never pushes.
- There is no spec, no plan, and no merge for you to approve. AceLM records the change for you behind the scenes.
- A small change skips the paperwork, not the checks.
- If the request turns out to touch a public API, stored data, security, or dependencies, or grows as it works, AceLM stops before committing and proposes the fuller route.
- The full lifecycle, with specs, reviewed plans, and release gates, is for work that needs it: several files or concerns, a public API, stored data, security, or dependencies.

## Components

- Jack: the command-line interface (CLI).
- Queen: the desktop app.
- King: the web interface.
- Deck: the engine. It does the work where your code lives and keeps the record.
- Dealer: AceLM's central services, including access to models.

## Models, data, and hosting

- Model access works with your own provider keys or through AceLM-managed model access.
- Model calls go through Dealer. You set the retention schedule for your data.
- AceLM always keeps de-identified telemetry (which of AceLM's own prompts ran, the model and provider, timing, tokens, cost, and counts). It never includes your prompts or your code.
- AceLM runs on AceLM's own dedicated servers. Organizations that must meet NIST SP 800-171 can have AceLM hosted in their own environment under a negotiated license.

## Access

- Access is by invitation, in early access. Request it at https://acelm.ai/request-access/

## Pages

- [Home](https://acelm.ai/): what AceLM is, a small change in one message, and the delegation dial.
- [How it works](https://acelm.ai/vision/): how planning, execution, review, verification, and learning fit together, and how people choose how much to delegate.
- [Capabilities](https://acelm.ai/capabilities/): coordinated roles, independent review, evidence of work, durable project records, and configurable rigor.
- [Lifecycle](https://acelm.ai/lifecycle/): the stages, what each must prove, and how small changes skip the ceremony but not the checks.
- [For teams](https://acelm.ai/enterprise/): authority, evidence, and policy for the engineering team that owns the work.
- [Questions and answers](https://acelm.ai/faq/): straight answers, including "Is AceLM too heavy for small changes?" and "Does a small change skip testing or review?".
- [Components](https://acelm.ai/components/): Jack, Queen, King, Deck, and Dealer, and how they fit together.
- [Interfaces](https://acelm.ai/interfaces/): design mockups of the command line, desktop, and web interfaces.
- [Contact](https://acelm.ai/contact/)

## Not on this site

- Pricing and a release date are not published. The interface pages show design mockups with sample data.