Business and Enterprise include dedicated vCPU sizes.
Sandboxes
A flat compute rate for each size, measured by the second while it runs.
Size
vCPU
Memory
Price
Always on
micro
1
0.5 GB
$0.0316/h
$23.05/mo
tiny
1
1 GB
$0.0359/h
$26.22/mo
xs
1
2 GB
$0.0446/h
$32.58/mo
smallPopular
2
4 GB
$0.0893/h
$65.16/mo
quad
4
4 GB
$0.1437/h
$104.90/mo
medium
4
8 GB
$0.1785/h
$130.32/mo
large
8
16 GB
$0.3570/h
$260.65/mo
xl
16
32 GB
$0.7141/h
$521.29/mo
Desktops
The same resource model, with a desktop for visual work and shared sessions.
Size
vCPU
Memory
Price
Always on
xs
1
2 GB
$0.0446/h
$32.58/mo
smallPopular
2
4 GB
$0.0893/h
$65.16/mo
medium
4
8 GB
$0.1785/h
$130.32/mo
large
8
16 GB
$0.3570/h
$260.65/mo
xl
16
32 GB
$0.7141/h
$521.29/mo
Apps & databases
Measured CPU and memory usage, with a full-size ceiling.
Size
vCPU
Memory
Price
Always on
micro
1
0.5 GB
$0.0316/h
$23.05/mo
tiny
1
1 GB
$0.0359/h
$26.22/mo
xs
1
2 GB
$0.0446/h
$32.58/mo
smallPopular
2
4 GB
$0.0893/h
$65.16/mo
medium
4
8 GB
$0.1785/h
$130.32/mo
large
8
16 GB
$0.3570/h
$260.65/mo
xl
16
32 GB
$0.7141/h
$521.29/mo
CPU and memory are metered by use, up to the full-size ceiling shown above.
Everything else
Persistent resources have their own meter, separate from running compute.
Disk
$0.09/ GiB-month
Provisioned persistent disk
Snapshots
$0.018/ GiB-month
Stored snapshot data
Object storage
$0.0162/ GiB-month
Stored application artifacts
Outbound transfer
$0.054/ GB
Network egress
Builds
Free
Structured rate-book setting
Models
Models, priced per million tokens.
Input and output have separate rates. The model’s context window is a capacity limit.
Model
Input / 1M
Output / 1M
Context
Kimi K2.6Default
$1.90
$8.00
256k
Kimi K2.7 Code
$1.90
$8.00
256k
DeepSeek V4.1 Flash
$0.60
$2.40
1M
GLM-5.3
$2.80
$8.80
1M
How MIOSA compares
The same resource shape, using the published rate references captured with this site.
Product
Resources per machine
Per hour, one machine
boatflat per size
$0.018/h0.2x
MIOSAFlat per size
$0.089/h1.0x
Fly.iofull size
$0.092/h1.0x
Novitafull size
$0.117/h1.3x
Freestylefull size
$0.132/h1.5x
E2Bfull size
$0.166/h1.9x
Daytonafull size
$0.166/h1.9x
Blaxelby memory, while active
$0.166/h1.9x
AWS AgentCoreactive CPU · used RAM
$0.217/h2.4x
CloudflareNearest: standard-3
$0.220/h2.5x
Modalfull size
$0.238/h2.7x
Islofull size
$0.300/h3.4x
Runloopfull size
$0.317/h3.5x
Vercel Sandboxactive CPU
$0.341/h3.8x
Railwayactive CPU · used RAM
$0.411/h4.6x
Per month
Compare
Session
Peak machines at once
Up to 50 at once: 500 machine-hours
a month.
CPU busy
CPU utilization changes providers that meter active CPU. Flat-size resources keep the same
compute rate.
$45.39/ month on MIOSA
1,000 × 30 min × $0.0893/h = $44.65 + $0.74 disk
Developer: $20/mo, credited toward usage
1
boatflat per size
$20.00/ month
$20/mo usage minimum
2
MIOSAFlat per size
$45.39/ month
Developer: $20/mo, credited toward usage
3
Fly.iofull size
$47.08/ month
4
Novitafull size
$58.32/ month
5
AWS AgentCoreactive CPU · used RAM
$63.65/ month
Disk is not priced on the source page
6
Cloudflareactive CPU
$74.02/ month
Nearest: standard-3 · $5/mo plan fee shown separately
7
E2Bfull size
$82.80/ month
$150/mo plan fee shown separately
8
Blaxelby memory, while active
$82.80/ month
Disk is not priced on the source page
9
Daytonafull size
$83.18/ month
10
Vercel Sandboxactive CPU
$106.40/ month
Disk is not priced on the source page · $20/mo plan fee shown separately
Sources and method 14
Hourly values use the full resource size. Monthly estimates add disk while the workload
exists, apply credited plan minimums, and show other plan fees separately. Budget estimates
also apply listed session, machine and resource limits. Missing prices stay unavailable rather
than becoming zero.
This is a captured comparison, not a live price feed. Open a provider’s source to check its
current terms.
A credit is a unit of usage balance. In the captured MIOSA price book, one credit represents $0.01. The practice credits shown in this local documentation are separate and have no monetary value.
02How is usage billed?+
Compute is recorded by the second while the resource runs. A flat-size sandbox and a usage-metered service use different meters. Storage is separate, and a paid plan’s credited commitment acts as a monthly minimum.
03What happens at a $0 balance?+
The Free plan does not allow automatic overage. The published plan description says machines pause when the balance reaches zero; additional credit can be purchased on the official service.
04Is there a free plan?+
Yes. The captured rate sheet lists a $0 Free plan with a small monthly usage allowance and lower capacity limits. Check the comparison table for the exact published limits.
05Do idle sandboxes keep billing?+
A running sandbox is still a running resource. Pausing stops its compute meter, while retained disk or other persistent resources can continue to have their own charges.
06Do builds cost anything?+
The structured build-price field captured for this reconstruction marks builds as free. The original service controls actual billing; use its current price book when making a purchase.
Rate snapshot: Nov 9, 2026. This is a local interface reconstruction. Account and plan actions continue on miosa.ai.