Introduction
Hiver is a sandboxed execution platform. You provision isolated containers — called sandboxes — run commands inside them, manage files, and observe what happens, all from a TypeScript client that connects to a local controller running on your machine.
There is no cloud account required to get started. The client talks to http://localhost:10000 by default, where a local controller manages sandbox lifecycles.
Key capabilities
- Isolated execution — each sandbox gets its own container with a private process tree and filesystem. Commands run with
exec, with output available as a one-shot result or as a streamed async iterator. TTY mode is supported for interactive workloads. - File system access — mount one or more file systems into a sandbox at explicit paths. Backends include local directories (useful for development), Google Drive, and Google Cloud Storage. Per-path ACL rules control read/write/deny access.
- Network policy — by default sandboxes have full outbound internet access. Egress rules let you restrict which hosts, ports, methods, and paths are reachable. The proxy can also inject headers or query parameters into outbound requests without exposing them to the sandbox.
- Event streaming — a durable SSE stream (
/v1/events) emits every event the sandbox produces. The client reconnects automatically across transient drops, resuming from the last seen event ID so no events are missed. - Snapshots — capture sandbox state to a named key on shutdown and restore it on the next start. The same snapshot can be restored into multiple sandboxes in parallel, which is useful for branching long-running work.
Next: Getting Started