Pricing
Machine time is the whole bill.
Bowse charges for minutes of CI and hours of agent machines — nothing per seat, nothing per repo. Pick a size and a monthly volume to see what it costs.
- No seats
- No platform fee
- No minimum spend
- Workspace spend limits
Sizes
Six sizes, one rate card for CI and machines.
Root disk size is fixed per shape and covers the OS image plus your tools. CI bills from the per-minute column; machines from per-hour.
| Size / label | vCPU | RAM | Root disk | Per minute | Per hour |
|---|---|---|---|---|---|
| 1x2bowse-1x2 | 1 | 2 GB | 16 GB | $0.0005 | $0.030 |
| 2x4bowse-2x4 | 2 | 4 GB | 32 GB | $0.0010 | $0.060 |
| 2x8defaultbowse-2x8 | 2 | 8 GB | 48 GB | $0.0012 | $0.072 |
| 4x16bowse-4x16 | 4 | 16 GB | 96 GB | $0.0024 | $0.144 |
| 8x32bowse-8x32 | 8 | 32 GB | 160 GB | $0.0048 | $0.288 |
| 16x64bowse-16x64 | 16 | 64 GB | 256 GB | $0.0096 | $0.576 |
Rates in USD, excluding tax. Runtime is metered from boot to shutdown and may change with notice.
Billing model
How billing works.
One meter, two units. CI minutes and machine hours draw from the same workspace balance.
Metered runtime
CI by the minute, agent machines by the hour, prorated. The meter runs from boot to shutdown, including preparation and cleanup.
Stopped means unmetered
A stopped machine isn’t charged for CPU or RAM. Its disk stays attached, so the next start picks up where the agent left off.
No seats, no platform fee
You pay for machine time only — not per user, per repository, or per workspace. Invite the whole team.
Spend limits
Set a cap per workspace. Once it’s reached, new machines don’t start and running ones stop, so a runaway agent can’t run up a bill.
FAQ
Pricing questions, answered plainly.
Something missing? support@bowse.dev
What counts as runtime?
Everything from the moment a machine boots until it shuts down — your steps or commands plus machine preparation and cleanup. Time a CI job spends waiting in GitHub’s queue isn’t billed.
How do I try Bowse before committing?
Point one workflow job at runs-on: bowse and give one agent a machine. Set a low spend limit on the workspace first; Bowse stops starting machines once it’s reached.
Do I pay anything in a month I don’t use Bowse?
No. There’s no minimum spend and no platform fee, so a quiet month costs nothing in compute.
What happens to a stopped machine’s disk?
It’s kept, with files and installed packages intact, so you can start the machine again later. Delete the machine when you no longer need it and the disk goes with it.
How many machines can run at once?
Each workspace has a concurrency limit, shown in the console. CI jobs above it wait in GitHub’s queue; machine creates above it return a clear error. Email support@bowse.dev to raise it.
Do CI minutes and machine hours share a balance?
Yes — both draw from the same workspace balance. CI is metered per minute; machines per hour of runtime, prorated. Usage for each appears separately on the invoice.
Which size should I pick?
Start with the default 2x8 and look at the CPU and memory charts in the console after a few runs. Move lint and formatting jobs down to 1x2, and Docker builds or parallel test shards up.
Price a workload before you move it.
Send us your monthly CI minutes or agent hours and we’ll walk through the estimate with you.