NewInfinite storage: a box whose storage grows as you write.Infinite storage is here.Read the post
Talk to a founder

Prized for teams

A cloud dev box for every engineer on your team.

Your engineers and their coding agents work on cloud dev boxes in one shared workspace. The owner can cap each engineer’s monthly spend, and an audit log records who did what to each box, key and secret.

Talk to a founderRead the teams docs

A box for every engineer

Each engineer runs their own cloud dev boxes, for their own work and their coding agents, in one shared workspace.

  • Three roles: owner, member and contractor. Members see every box, secret and environment. Contractors see only the boxes they create.
  • People sign in with Google or GitHub. There are no passwords.
  • Invite people by email or with a link, or claim your company’s domain and turn on auto-join, so teammates on it join by signing in.
  • Shared environments hold the team’s repos, env vars, secret files and setup script.
  • Removing someone revokes their keys.

Spend the owner controls

One prepaid balance pays for the workspace. Only the owner changes the plan.

  • The owner can cap each engineer’s monthly spend. The cap is checked when a box is created, woken or resized.
  • The owner can also limit how many boxes each engineer can have, the largest size they can pick, and how long their idle boxes run before pausing.
  • These limits apply to members and contractors.
  • The owner can set quiet hours that pause running boxes in a daily window, except boxes the owner exempts.
  • Overage is off by default. With overage off, boxes pause when the balance reaches zero, and their disks are kept.
  • Owners get an email when the balance runs low. The Activity page shows spend by engineer and by box.
The Policies page with spend per member set to $25 a cycle, 2 boxes per member, largest size Small, an auto-pause floor of 120 minutes idle, and quiet hours on from 22:00 to 06:00 Monday to Friday and all day Saturday and Sunday.
The owner’s Policies page: $25 a cycle, 2 boxes and the Small size per member, idle boxes paused within 2 hours, and quiet hours on. A test workspace.
The new box form with the Small size selected and, under Create box, the red message: Workspace policy: your boxes have used $27.26 of the $25 each member may spend this billing cycle.
A member past the $25 cap tries to create a box, and the dashboard refuses it under the button. A test workspace.

An audit log

Every workspace keeps a log of who created, woke, paused, resized, forked, connected to or deleted each box.

  • It also records who changed keys, secrets, members and policies. In the dashboard, each row names the person and how they acted, such as from the CLI or the dashboard.
  • Owners and members can download it as CSV, and filter it with the CLI or the API. Contractors cannot read it.
  • It can also be sent, signed, to your own HTTPS endpoint every hour.
  • Rows are kept for 90 days by default, or 7 to 365 days as the owner sets.
  • Commands and prompts sent through Prized’s exec and prompt tools are logged by the CLI. What an agent types inside its own terminal session is not recorded.
Audit log events for one member: box settings changed, prompt sent and command run (both marked reported), secret created, box deleted, box paused and box created, each marked CLI or dashboard.
Audit log rows for one member: boxes created, paused and deleted, a secret created, and a command and a prompt, marked reported. A test workspace.

Where it runs

Boxes run in Prized’s AWS account, in five regions in the US and EU.

  • If your team needs them in your own cloud account, we support that on request.
  • us-west-2
  • us-west-1
  • us-east-1
  • us-east-2
  • eu-central-1

Talk to a founder.

Tell us how your team works and what it needs.

Book a callRead the teams docs