Docs
Understand the storage model before you launch a session.
BurstFlare separates reusable instance state from per-session state so teams can keep one stable baseline while each session stays isolated where it should.
InstancesReusable runtime definitions with image choice, bootstrap script, environment, secrets, persisted paths, and shared home-state metadata.
SessionsContainers launched from an instance. Each session gets its own isolated /workspace so work stays local to that run.
SnapshotsThe latest session snapshot is restored on start so session-local files come back automatically without extra manual sync.
Common state/home/flare is shared per instance. BurstFlare restores it on start and syncs it back on stop, with explicit push and pull still available.
Quickstart
Standard CLI flow for creating an instance, starting a session, and attaching over SSH.
flare instance create node-dev --image ubuntu:24.04 --bootstrap-file ./bootstrap.sh flare session up sandbox --instance <instance-id> flare ssh <session-id> flare instance push <instance-id> flare instance pull <instance-id>
Use an image your worker supports. Session startup will restore the shared instance state and the session's isolated workspace before you connect.
Persistence model
What survives across starts, stops, and separate sessions.
| Path or object | Scope | Behavior |
|---|---|---|
/home/flare | Instance | Shared baseline synced across sessions of the same instance. |
/workspace | Session | Isolated per session and restored automatically when that session starts again. |
| Bootstrap script | Instance start | Runs on session start so dependencies and setup are rebuilt in ephemeral containers. |
| Snapshot | Latest session state | Captured for restart and preview flows without exposing raw storage mechanics. |