--- title: "The ADE: an Agentic Development Environment · Frazer" description: "Frazer’s ADE is the whole environment for engineering with agents: the Frazer app and the editors you already use, devboxes, agents and squads, Knowledge, Frazer Reviewer, GitHub runners and cache, and the cloud you deploy to, under one identity, one set of rules and one audit trail." url: https://frazer.ai/ade index: https://frazer.ai/llms.txt tokens: 2695 --- > For agents: every page on frazer.ai is indexed at https://frazer.ai/llms.txt. # The ADE: an Agentic Development Environment · Frazer **ADE** Agentic Development Environment # The new standard for engineering with agents. An environment, not an editor. When agents do most of the typing, the work changes shape: you set direction, approve and review, and the work runs in parallel on real machines. Frazer’s ADE is the whole environment for that: the Frazer app and the editors you already use, devboxes, agents and squads, company Knowledge, Frazer Reviewer, GitHub runners and cache, and the cloud you deploy to, under one identity, one set of rules and one audit trail. [Download the Frazer app](https://frazer.ai/app#download) [See how it works](https://frazer.ai/ade/how-it-works) [Tour the app](https://frazer.ai/ade/tour) Frazer app for macOS, Windows and Linux extension for VS Code and the editors built on it JetBrains 00 · The front door: the Frazer app, Home Fig. 1 · product UI, demo organization *Home in the Frazer app for lena at Acme, a demo organization: “What should we build, lena?” over an empty composer that picks the model route, the agent and the box, and quick actions for a session, a fan-out, a deploy, a box and an agent. Needs you: a staging deploy to apply, one question asked by 212 sessions, noah’s production deploy waiting for a second person, and an assistant that wants to email a supplier. Running now: the pgx-v57 fan-out at 412 of 1,000, a session, the platform-ops squad and a personal agent. Then recent sessions, and the boxes: lena-api running, lena-gpu asleep, and noah-api shared with lena for 6 more days.* A **Needs you, in one list** A plan to apply, one question asked by 212 sessions, a production approval and an agent that wants to send mail. B **Work running without you** A fan-out at 412 of 1,000, a squad on its objective, sessions that keep going when the laptop closes. C **One key to start anything** A session, a fan-out, a deploy, a box or an agent, from a composer that picks the model route, the agent and the box. D **Real machines** Boxes on named servers, a GPU box asleep until you wake it, and boxes a teammate shared with you. Fig. 1: the Frazer app’s Home, product UI with a demo organization. 01 · What changes ## Agents do the typing. You direct, approve and review. The scarce resource is no longer keystrokes or compute; it is your attention. So an ADE runs work in parallel, checks it before it reaches you, and asks you only for the decisions that need a person. An editor with an agent in it, and the ADE | | An editor with an agent in it | The ADE | | --- | --- | --- | | Where work runs | On your laptop, one session at a time | On real machines: your devbox, and a microVM for every session of a fan-out | | How much at once | As many tabs as you can keep an eye on | Designed for 1,000+ concurrent sessions per organization; 100 per person by default | | Context | Whatever you paste in | Company Knowledge, skills and MCP servers on every box and agent, with each person’s permissions | | Review | Every diff, by hand | The Reviewer and a verifier check first; you review clusters of similar results | | Shipping | Your own tokens, scripts and deploys | One plan to apply; production waits for a person with a passkey | | Spend | Found on next month’s invoices | Budgets per item, run, agent and project that stop before they spend | | Record | Spread across every tool | Every write is a plan with an audit entry: who, on whose behalf, and why | 02 · The ADE, defined Fig. 2 ## Not one app. The whole environment. An editor with an agent in it helps one person type faster. An ADE is everything around the work: the machines it runs on, the agents that do it, the knowledge they read, the gates that check it and the cloud it ships to. Frazer builds every part, so they share one identity, one set of rules and one audit trail. *Every way in (the Frazer app, VS Code, Zed, Windsurf, JetBrains, a terminal, the browser, the console, Slack and Teams, the API and MCP) opens one environment of seven parts: the Frazer app, devboxes, agents and squads, Knowledge, Frazer Reviewer, GitHub runners and cache, and the cloud you deploy to. All of them share one identity, one set of rules and one audit trail, on your servers, your cloud accounts or Frazer servers. An editor is one part; the environment is the product.* **Fig. 2** The ADE: seven parts on one identity, one set of rules and one audit trail - [Frazer app](https://frazer.ai/app)The front door: sessions, runs, triage, squads, Knowledge, deploys and your Inbox in one window. - [Devboxes](https://frazer.ai/devboxes)Real machines with local NVMe, set up for your company, shared by role. - [Agents and squads](https://frazer.ai/agents)Sessions, standing agents and squads, from preconfigured images, with budgets. - [Knowledge](https://frazer.ai/knowledge)Your code and company knowledge, with each person’s permissions on every answer. - [Frazer Reviewer](https://frazer.ai/reviewer)Evidence or silence, and a verifier from another model family. - [GitHub runners](https://frazer.ai/runners/github)CI in a microVM per job, lanes for agent PRs, one warm cache. - [The cloud you deploy to](https://frazer.ai/platform)Kubernetes, serverless, databases and Frazer Monitoring, on any hardware. - [Under all of it](https://frazer.ai/ade/control)One identity, one set of rules and one audit trail: IAM, approvals, budgets, the LLM gateway. 03 · A thousand sessions, and you stay in charge ## A thousand sessions, and you stay in charge. Nobody watches a thousand sessions. The ADE splits the job into three parts it can carry for you: it fans the work out, holds every session inside guardrails, and brings results back as decisions. - 01 · Fan out ### One prompt. A thousand items. One prompt with variables over a catalog query, repositories, tickets or a list. A dry run on three items first, then waves. Each person runs up to 100 sessions at a time by default, and an admin can raise that to 1,000; the rest queue instead of failing. [A thousand sessions](https://frazer.ai/ade/sessions) - 02 · Guardrails ### Every session inside your rules. Each session runs in its own microVM with short-lived grants. Budgets per item and per run stop before the next model call, and a kill switch trips on failures, a broken guardrail or no progress. Agents never approve. [Stay in charge](https://frazer.ai/ade/control) - 03 · Review ### Decisions, not a thousand diffs. The Reviewer and a verifier from another model family check every result at its exact commit. You review clusters of similar changes, a representative and three spot checks, then open draft pull requests in batches. [How it works](https://frazer.ai/ade/how-it-works) Frazer is designed for 1,000+ concurrent sessions per organization: a target, not a measurement. 04 · The front door Fig. 3 ## The Frazer app is the front door. Your editor is welcome too. The Frazer app, built by Frazer with its own agent engine in Rust, puts the whole ADE in one window: sessions on your box, fan-out runs and triage, squads, Knowledge, the deploy sheet, Cloud and your Inbox. Close the laptop and the work goes on. Prefer your editor? The Frazer extension brings sessions, boxes, approvals and Plan cards to VS Code and the editors built on it, and JetBrains connects through Toolbox. Same boxes, same rules. - **Resume anywhere** Sessions live on the box, not the laptop; pick them up on another device. - **Every tool** Each Frazer product is a panel, a palette command or a slash command. - **One identity** One sign-in, one device check, one revoke for every way in. [The Frazer app](https://frazer.ai/app) [Tour the app](https://frazer.ai/ade/tour) *VS Code on the devbox lena-api with the Frazer extension: a Frazer sidebar lists sessions, boxes, approvals, runs and knowledge, and rules.ts shows two hunks from the Frazer agent waiting to be accepted.* **Fig. 3** The Frazer extension in VS Code, on lena-api demo organization 05 · Go deeper ## See it end to end. - ### [How it works](https://frazer.ai/ade/how-it-works) One piece of work, from a prompt to production, in eight steps on the real screens. - ### [A thousand sessions](https://frazer.ai/ade/sessions) Fan-out, waves and budgets, where sessions run, and how results come back. - ### [Stay in charge](https://frazer.ai/ade/control) Approvals, budgets, guardrails, grants and Secrets, audit and the kill switch. - ### [Tour](https://frazer.ai/ade/tour) Twelve screens of the Frazer app, and every way into the ADE. Questions ## The ADE, answered. [Every price](https://frazer.ai/pricing) Is this an IDE? An IDE is an editor. The ADE is the environment around it: the machines your sessions run on, the agents and squads that work in parallel, the knowledge they read, the reviewer that checks their work, the CI that proves it and the cloud it ships to, under one identity. The Frazer app is how you open it; your editor still edits. Do I have to switch editors? No. Work in the Frazer app, or keep VS Code or an editor built on it, with the Frazer extension, or JetBrains through Toolbox. Zed, a terminal and the browser reach the same box. Every way in opens the same boxes, sessions and approvals, with one sign-in, one device check and one revoke. What runs where? Your laptop runs the app or your editor and holds nothing long-lived. The Frazer agent and your sessions run on your devbox, a VM on a server you can name. Fan-out sessions and managed agents run in their own microVMs; CI runs on GitHub runners, a fresh microVM per job; what you deploy runs on Kubernetes or serverless. All of it on your servers, your cloud accounts or the Frazer fleet. What does it cost? On servers you bring, devboxes, agents, GitHub runners and Knowledge are part of **$1.50 per physical core a month**, and your first server with up to 16 cores is free. On the Frazer fleet you pay by the second: devboxes at $0.030 per vCPU-hour plus $0.007 per GiB-hour, agent sessions at $0.05 per active vCPU-hour, and only storage while asleep. Models cost the provider’s price plus 5 %, or nothing extra with your own key. Squads and campaigns cost nothing by themselves; their budgets cap the meters. Frazer Reviewer is $15 per active human committer a month, or $7.50 with your own model key; agent pull requests take no seat, and public repositories are free. ## Start with one session. Stay in charge at a thousand. [Start building](https://frazer.ai/start) [Download the Frazer app](https://frazer.ai/app#download)