--- title: "Frazer: everything between an engineer and production, built as one" description: "Frazer builds everything between an engineer and production as one: the ADE, an Agentic Development Environment where you and your agents work; agents that take on work in parallel, inside your rules; and the cloud they build, deploy and run on. On your servers, your cloud accounts or ours." url: https://frazer.ai index: https://frazer.ai/llms.txt tokens: 2255 --- > For agents: every page on frazer.ai is indexed at https://frazer.ai/llms.txt. # Frazer: everything between an engineer and production, built as one [**New** The ADE: an Agentic Development Environment, from the editor to production](https://frazer.ai/ade) # Everything between an engineer and production. Built as one. Our mission **One engineer with the impact of a thousand.** Frazer is one company behind three layers that teams usually buy from different vendors: the **ADE**, the Agentic Development Environment where you and your agents work; **Agents** that take on work in parallel, inside your rules; and the **Cloud** they build, deploy and run on. Built as one, from the editor to production, on your servers or ours. [Start building](https://frazer.ai/start) [See how the ADE works](https://frazer.ai/ade) Frazer app for macOS, Windows and Linux VS Code, VS Code-based editors and JetBrains your servers, your cloud accounts or ours 00 · The whole vertical, working Fig. 1 · one piece of work, from a prompt to production *At Acme, a demo organization, lena writes one prompt in the Frazer app on a devbox. It fans out to 1,000 items, each session in its own microVM inside a budget. Frazer Reviewer, a verifier from another model family and Frazer CI check the pull requests on Fir before lena decides; the change deploys to Kubernetes or serverless and is watched in production. All of it runs on Acme’s servers, its cloud accounts or Frazer servers, under one identity, one set of rules, one audit trail and one bill.* A **You set direction** One prompt with variables, a dry run on three items, then answers and approvals. Your attention goes where results differ. B **Agents work in parallel** Each session in its own microVM, with your company’s knowledge and skills, inside a budget that stops before it spends. C **Gates before anything ships** The Reviewer, a verifier from another model family and Frazer CI’s agent lane check every pull request on Fir before a person decides. D **Production you can watch** Kubernetes or serverless on real hardware, watched after every rollout, under one identity and one audit trail. 01 · Why we own the whole vertical Fig. 2 ## Agents fail at the seams. So we own every layer. An agent that writes code still needs context, credentials, CI, an approval, a place to deploy and someone to pay for it. When each of those comes from a different vendor, every hand-off is a place where work stops, or leaks. Frazer builds all five layers as one product, so the rules that bound an agent hold from the editor to the server. L1 **ADE** Frazer app · VS Code · JetBrains · devboxes seam 1 · context usually breaks **Context** Each agent starts cold: no code index, no runbooks, no team skills. What one session learns stays on one laptop. one owner changes **Knowledge travels with the person** The same Knowledge bases, skills and MCP servers on every box and every agent, checked against each person’s permissions. L2 **Agents** sessions · squads · Knowledge · Reviewer seam 2 · credentials usually breaks **Credentials** Long-lived tokens get pasted into agents and CI. Nobody can say what an agent can reach, or revoke it in one place. one owner changes **One identity** Agents act for a person, never as them, with tokens that expire within the hour. One revoke ends every path. L3 **Build and ship** Fir · Frazer CI · GitHub runners · Cache · Registry · GitOps seam 3 · approvals usually breaks **Approvals** Approval is a thumbs-up in a chat thread, and production changes happen outside any record. one owner changes **One plan to apply, one audit** Every write is a plan. Production waits for a person with a passkey, and every step lands in one audit trail. L4 **Run** Kubernetes · serverless · databases · Frazer Monitoring seam 4 · latency and cost usually breaks **Latency and cost** Code, CI and deploys sit in different clouds, caches start cold, and every vendor sends its own bill. one owner changes **One site, one bill** Code, CI and deploys run in the same site with one warm cache. One bill, per physical core, with budgets that pause. L5 **Hardware** your servers · your cloud accounts · ours **Fig. 2** The stack an agent’s work passes through, and the four seams between its layers [See how the ADE works](https://frazer.ai/ade) [Every product](https://frazer.ai/platform) 02 · The platform Fig. 3 ## A complete cloud under it all. Enterprise-grade, automated end to end. [See every product](https://frazer.ai/platform) Kubernetes, serverless, version control, CI and runners, GPUs, devboxes, managed agents, databases, networking, observability, security, an LLM gateway, company knowledge and billing. Everything the console can do, the CLI, the API, the MCP server and the Frazer app can do too. **Fig. 3** One control plane over any hardware · groups as in the mega-menu 03 · Agents at the scale of a company Fig. 4 ## From one prompt to a thousand sessions. With guardrails built in. Give a squad of agents an objective: a manager splits it, workers run in their own sandboxes on the Frazer harness or a harness you choose, and you approve what ships. Frazer is designed for 1,000+ concurrent sessions per organization, with quotas that queue work instead of failing it, and CI lanes that keep agent pull requests from starving yours. - **Reviewer** Evidence or silence: a finding needs a reproduced test, a trace or an approved rule. - **Verifier** Another model family checks the exact commit before anything merges. - **Approvals** Production writes and large plans wait for a person, with step-up. - **Budgets** Per session, agent, squad and CI lane. A cap pauses; it never deletes. - **LLM gateway** One door to every model: keys, guardrails, logs, zero-retention mode. - **Security Center** Agents are principals: watched, scoped and revocable in one click. [Frazer Agents and squads](https://frazer.ai/agents) [How a thousand sessions work](https://frazer.ai/ade/sessions) **Fig. 4** Parallel work per engineer, by era 04 · Real hardware, anywhere Fig. 5 ## Real machines. Wherever you have them. Frazer runs on physical servers with local NVMe and a private network between them, provisioned with you and tested before they take work. Not a virtual disk of unknown speed. ### Your servers $ frazer servers add Bare metal in your rack, your office or your OVH and Hetzner accounts. One command; an outbound-only agent; no shell for us. ### Your cloud accounts Linux instances you already pay for join as dedicated nodes, and existing managed clusters attach under Frazer. ### Frazer servers Dedicated servers by the month, burned in before you get them and wiped with a certificate after. Or the Frazer fleet by the second. **Fig. 5** A site: three servers, local NVMe, private network 05 · Built for engineering work ## Not a bare cloud. The tools engineers and agents use all day. [### Frazer Agents Always-on agents and squads of managers and workers, from preconfigured images, on the Frazer harness or a harness you choose, with budgets and approvals. Learn more](https://frazer.ai/agents)[### GitHub runners CI in a fresh microVM per job, lanes so agent pull requests never starve yours, and one cache that is already warm. Learn more](https://frazer.ai/runners/github)[### Devboxes Real machines with local NVMe, shared caches across the pool, roles for teammates, and a provisioning profile that sets every tool up. Learn more](https://frazer.ai/devboxes)[### Knowledge Your code and company knowledge, indexed with permissions on every chunk, evaluated before each change, and on every box through MCP. Learn more](https://frazer.ai/knowledge) 06 · Pricing ## Pay for what we manage. Not for what you own. $1.50 per core per month $49 per data-center GPU $0 per cluster [Estimate your bill](https://frazer.ai/pricing) [Send us your cloud bill](https://frazer.ai/pricing/bill) ### Three 24-core servers you already own, for a month Management **$108.00** · 72 physical cores × $1.50 Clusters **$0.00** · as many as the servers hold Included GitOps, gateways, DNS, certificates, registry, secrets, backups, monitoring By use Fleet GPUs, agent sessions and tokens, only when you use them From the same price list as the console. Hyperthreads never count. 07 · Trust ## Your servers, your keys, your data. [Security and trust](https://frazer.ai/security) ### Nothing gets in Servers dial out to Frazer Link. No inbound ports, no shell access for us, signed operations only. ### Every action is on the record People, agents and Frazer itself act through the same API; each write is a plan with an audit entry. ### Proof you can check Sub-processors, DPA and security contact are public. Audits and certifications: we will publish them when we have them. Customer stories appear when customers sign them off. ## We don’t limit what you build. We give you every tool to succeed. [Download the Frazer app](https://frazer.ai/app#download) [Start building](https://frazer.ai/start)