Billing and limits

Your machine is your own bill. You pay for the hardware, the power, the network, and the hosting, and MIOSA does not charge you for the machine. MIOSA charges for platform usage under your plan; current rates and volume terms live on the pricing page.

This page covers the limits that a plan puts on OpenComputers, and the operational caps that apply to everyone.

Plan limits

Plan limits are per organization.

PlanHosts
free1
starter3
pro10
scale50
enterprise500

Registering past the limit returns 402 with error: "plan_limit_reached", plus the limit and current values.

PlanContainer and compose service slots
free2
starter10
pro50
team250
enterprise1000
PlanTunnels per host
free0
starter3
pro10
scale50

A compose project counts its services against the same container budget, so a project with three services uses three slots.

To raise a limit, contact support with your expected scale. See Support.

Operational limits

These apply regardless of plan.

LimitValue
Command length in a job1 to 8192 characters
Arguments per job256
Working directory length4096 characters
Job timeout1 to 3600 seconds; default 30
Exec stream timeout30000 ms
File transfer chunk4 MiB per read or write
Backup chunk8 MiB compressed
Backup compression level1 to 22; default 19
Backup retention1 to 365 snapshots, or 1 to 3650 days
Tunnel frame4 MiB
Tunnel connect timeout10 s
Tunnel response timeout30 s
Forwarded request headers per tunnel request64
Container stats tick10 s
Mesh size253 hosts
Tags per host20
Device browser token TTL3600 s

Job commands are also recorded in audit truncated to 512 characters, and environment variable names are recorded without their values.

Counters you can read

The platform meters usage per resource, and the counters are on the records you already fetch.

CounterWhere
Host egress and ingress bytesusage.lifetime_bytes_egress and usage.lifetime_bytes_ingress on the host record
Tunnel requests and bytesrequest_count, lifetime_bytes_ingress, and lifetime_bytes_egress on the tunnel
Snapshot sizetotal_bytes and compressed_bytes on the snapshot
Container resource uselast_cpu_percent, last_mem_mb, and last_stats_at on the container

For the platform-wide picture, use the Pricing and limits page and the Usage Rollup API.

Was this page helpful?