back to microsandbox

enterprise

operate agent computers as an organization.

your team gets sso, roles, and 2fa. your finance team gets metering and invoices. your auditors get logs. the agents just get computers.

dithered team meeting representing organization-level sandbox operations

01

people and machines, accounted for

two-factor login, oidc sso, and org roles for the humans. api keys, personal access tokens, and ssh keys for the machines. nobody shares a password.

invite people as viewers, members, or admins. keep user access and machine access explicit instead of passing one credential around.

02

see everything, cap anything

audit logs record who did what. quotas cap what each org can consume. per-sandbox metering feeds monthly invoices you can actually reconcile.

private registries keep approved images with the organization. persistent volumes keep only the state a workload is meant to retain.

03

run it where your rules require

managed cloud is invite-only today. byoc brings the same runtime to your own cloud or metal. contact us to evaluate running microsandbox inside your own environment.

private beta. access is by request. invitations go out in batches. byoc starts with your constraints and your own security review.

how it works

how a team adopts microsandbox

01

bring your team

invite members with roles, turn on oidc sso and two-factor login.

02

set the guardrails

quotas cap consumption, private registries control images, audit logs record who did what.

03

account for it

per-sandbox metering rolls into monthly invoices you can reconcile.

book a deployment review.