--- title: "Devboxes: real machines, smart about caches, shared by role · Frazer" description: "A Frazer devbox is a VM on a server you can name, with local NVMe, a private network and caches shared across the pool. It opens already set up for your company, from the Frazer app or any IDE." url: https://frazer.ai/devboxes index: https://frazer.ai/llms.txt tokens: 1346 --- > For agents: every page on frazer.ai is indexed at https://frazer.ai/llms.txt. # Devboxes: real machines, smart about caches, shared by role · Frazer Devboxes · Real machines for engineers and agents Fig. 1 # Devboxes that are real machines. Smart about caches. Shared by role. A box is a VM on a server you can name, with local NVMe, a private network to its neighbors and caches shared across the pool. It opens already set up for your company, from the Frazer app or any IDE, for you, your team or your agents. [Give your team boxes](https://frazer.ai/start?product=devboxes) `frazer devboxes create --template go` **lena-api** large DATASHEET · BOX compute vCPU **16** · overcommit stated per size Memory **64 GiB** · never overcommitted storage Home **200 GiB** · snapshotted on stop and nightly Scratch **200 GiB** · local NVMe · erased on stop Caches pool tier **eng-pool** · hot tier on scratch placement Server **Borealis** · vin1-b-01 · EPYC 9354 Disks 2 × 1.92 TB NVMe · burn-in passed Network vRack private L2 · lena-api-acme.access.frazer.run people and tools Members lena owner · noah collaborator, 6 days Profile **acme-baseline v12** · 14 items REV 12 ACME-STAGING **Fig. 1** What a box tells you about itself · demo organization 01 · Real hardware Fig. 2 ## Not a mystery disk. A drive you can name. We set up the servers with you, burn them in before they take work, and connect them over a private network. Every box shows the server, the CPU and the drives it runs on. **Fig. 2** One server, three boxes: cores, memory and NVMe as they are allocated ### Burned in before work CPU, memory, disk and network stress tests run before a server is available; the results stay on its page. ### Private network Servers in a site talk over the provider’s private L2 (vRack, vSwitch); boxes reach your VPC and databases privately. ### Honest sizes Memory is reserved, never overcommitted. CPU overcommit is written on each size, never hidden. 02 · Shared caches Fig. 3 ## A hundred boxes, one cache. A hundred boxes building the same Go monorepo should not each fetch, compile and store the same objects. Frazer keeps one shared tier per pool and a hot tier on each box’s NVMe. **Fig. 3** Shared tier per pool, hot tier per box, trusted writers only 1. ### Local NVMe The box’s own hot tier answers first, at local disk speed. 2. ### Pool cache A miss asks the pool’s cache service by the exact action key the Go command computes. 3. ### Build and keep Still a miss: compile, keep the result locally. Only trusted builders publish to the pool. | Ecosystem | Shared across the pool | Local to the box | | --- | --- | --- | | Go build | GOCACHEPROG (Go 1.24+) to the pool cache service; or a read-only snapshot of a prebuild’s GOCACHE as an overlay | Overlay upper and helper tier on scratch NVMe | | Go modules | Read-only module snapshot per pool, refreshed by prebuilds; site module proxy for misses | Overlay upper on scratch | | Containers | Frazer Registry pull-through cache per site, peer-to-peer between servers | Container image store on NVMe | | Bazel, Rust, C++ | Remote cache on the same pool service (Bazel remote cache, sccache) | Output base on NVMe | | npm, pnpm, pip | Pull-through package proxy per site | Package store on NVMe | Each pool shows its cache size, hit rate and the bytes it saved, in the console. 03 · Shared boxes with roles ## Pair on one box. Safely, and only for as long as needed. Owner, Collaborator and Viewer, for people or groups. Every grant except the owner’s expires; rules can ask for an approval; every connection is verified and on the record. - **lena** · owner Owner no expiry - **noah** · own account on the box Collaborator 6 days left · renew - **amara** · watches sessions read-only Viewer 8 h · recorded - **platform** group · team box Owner contact: kenji Members of lena-api · product UI, demo organization Isolation One VM per box; one account per person inside it Verified Two factors, an enrolled device and a step-up for someone else’s box Revoke Accounts and sessions end within a minute of a revoke 04 · Provisioning profiles Fig. 4 ## Set up once by admins. Improved by everyone. A profile gives every box the company’s skills, MCP servers, connections, knowledge, models and instructions, live and without a rebuild. What people add on their own boxes becomes a report an admin can roll out to the fleet. **Fig. 4** Layers: later layers add, nobody overrides a locked item lena added an MCP server on lena-apichange report What linear · remote · OAuth · 22 tools, 6 write Used 38 calls in 3 days Elsewhere 3 other boxes added it too Catalog Not in the org catalog · publisher verified A change report · product UI, demo organization Shared models work the same way: one open model on your GPU server, published to the boxes in a profile with a quota per box, through the LLM gateway. 05 · Connect from any IDE ## Open it with whatever you like. One sign-in, one device check, one revoke. [About the Frazer app](https://frazer.ai/app) - Frazer apprecommended - VS Codeextension - VS Code-based editorsextension - JetBrainsToolbox plugin - Zed - Hermes - SSH - Browser ## Give fifty engineers a box with one policy. [Start building](https://frazer.ai/start?product=devboxes) [See Knowledge](https://frazer.ai/knowledge)