SpawnDroid

Plans and limits

What each plan includes, how concurrency is enforced, how retention works, and which add ons are available.

SpawnDroid limits parallel runners, not time. On every plan you can stream for as long as you need, but only the number of simultaneous devices your plan allows can run at once.

Plans

PlanPriceParallel runnersSeatsHistoryAvailability
Free€0117 daysAvailable
Team€59 / month3up to 330 daysComing soon
Scale€199 / month12up to 630 daysComing soon
Enterprise€549 / monthCustomUnlimited30 daysContact us

The Free plan is the only plan that can be purchased today. The number that governs your day to day work on every plan is the parallel runner count, not time.

If you want early access to a paid tier, join the waitlist from the pricing page and the team will invite you as capacity opens.

Parallel runners

A parallel runner is one live device. When you start a device and every slot in your workspace is busy, the request is rejected with HTTP 429 and a code of concurrency, and the console offers two ways out: stop the session that is currently running, or add a slot to the workspace. Nothing is queued, so a pipeline always knows immediately whether a runner is available.

Slots count live sessions across the whole workspace, so two artifacts running at once consume two slots. CI executions and manual runs draw from the same pool.

Add ons

Any tier can extend its limits without changing plan.

ItemPriceWhat it adds
Parallel slot€89 / monthOne more concurrent runner, cancellable at any time
Seat€29 / monthOne more workspace member, prorated to your billing cycle
Storage tier€59 / monthKeeps historical executions, logcats and artifacts for 30 days

Add ons are being prepared alongside the paid plans. Until billing is live, the upgrade paths in the console explain where each tier sits rather than charging you.

Seats and members

A seat is a member who can sign in to the workspace. Admins can invite and remove members, and every member sees only the workspaces they belong to. Enterprise workspaces remove the seat cap entirely.

Retention and history

SpawnDroid keeps your data long enough to review it, then prunes on a nightly sweep so storage stays predictable.

  • The newest release of every artifact is always kept, so the build in use is never removed.
  • Superseded releases older than your plan's history window are removed.
  • CI logcat captures and screen recordings older than the window are cleared, and the console stops offering links to them.

On the Free plan the window is 7 days. Paid tiers extend it to 30 days. The sweep also runs opportunistically when you visit the dashboard, so a workspace that is opened regularly stays tidy without waiting for the nightly pass.

Idle and session limits

There is no time allowance to track. A device stays up while it is in use: the console sends a heartbeat while someone is watching, and the device host reaps a runner that has had no heartbeat or viewer for a while, so a session everyone has walked away from is returned to the pool automatically. Every session also has a maximum lifespan as a backstop. Only idle time and the session lifespan are capped — concurrency is what bounds a workspace.

On this page