- Free allowance
- Free $0 forever: 1 concurrent container, 1 request per 42 seconds, zerotrust execute only, 15 minute TTL max, no sessions or services, community support
- Verdict
- caveatusable, with a named limit or an unprobed read path
- Cost
- free tierpaid plans from USD 7/month
- Identity
- cardcard required, no phone
- Binding limit
- request-rate7 requests a minute and 1 concurrent execution on Development; 91 a minute and 4 concurrent on Production at USD 91 a month
- Evidence
- documented5 sources; a first-party page was read and the sentence quoted
- Freshness
- stale on 2026-12-05checked 2026-11-04 (live); stale on 2026-12-05
| Free tier | Free $0 forever: 1 concurrent container, 1 request per 42 seconds, zerotrust execute only, 15 minute TTL max, no sessions or services, community support unit mixed; metered on request-count; the free tier is a concurrency and rate allowance, not a byte or an hour allowance |
|---|
| Price | none stated |
|---|
| Limits | - request-rate (binding) 7 requests a minute and 1 concurrent execution on Development; 91 a minute and 4 concurrent on Production at USD 91 a month source
- retention-clamped 15 minute TTL max on the free tier; paid plans get 'Custom TTL', and the maximum permitted TTL is not published source
Freeze/unfreeze is the lifecycle: a frozen service unfreezes on an HTTP request, which is what turns a 15-minute-TTL container into a service. The requests-per-minute cap, not the container size, is what a webhook or agent workload hits first. |
|---|
| Binding | request-rate At 7 requests a minute a single agent loop or a modest webhook receiver saturates the plan long before the 1 vCPU or the 2 GB is used, and the next step up is USD 91 a month. |
|---|
| Identity | card The paid path is 'Purchase API Key' from the pricing page, so the USD 7 tier is bought, not registered for. The USD 0 free tier also requires an account. Whether a debit or prepaid card is accepted, whether any authorisation is held, and whether the free tier can be entered without a card are not stated on the pages read. |
|---|
| Egress | Not published. Neither the pricing page nor the docs page read states a traffic allowance, a per-GB rate, or an egress quota; the plan card sells concurrency, request rate and container size only. Services are served with automatic HTTPS on *.on.unsandbox.com and custom domains by CNAME. |
|---|
| Per-object cap | 10 files per execution, 10 MB total per execution and 5 MB per single file; maximum container resources 8 vCPU and 16 GB RAM |
|---|
| Retention | unknown: sessions and services survive freeze/unfreeze and services auto-unfreeze on an inbound HTTP request, but no page read states how long a frozen service or a snapshot is kept before deletion |
|---|
| Interface | rest, cli REST API with public/secret API keys, a Python client (un.py), 42+ language runtimes, persistent sessions over tmux/screen, and long-running services with automatic TLS. |
|---|
| Tooling | The vendor's own Python client and raw REST. Sessions are reached with a shell over tmux or screen, so existing SSH-style workflows do not transfer: this is an API-first product, not a machine you log into. |
|---|
| Composes with | USD 7 a month buys a 1 vCPU / 2 GB container that can run as a long-lived HTTPS service with a custom domain, freezing between requests. That makes it a candidate for a small always-on endpoint or a scheduled job runner, not for a daily-driver shell and not for a VPN node. |
|---|
| Reliability | Nothing observed. A container that is frozen between requests loses in-flight process state on the unfreeze unless the service is designed for it; the docs present freeze as resource saving and do not promise process continuity. |
|---|
| Notes | The plan ladder is USD 0 / 7 / 91 / 203, so the USD 7 tier is the only affordable one and its 7 requests a minute is the whole offer. Region and hosting provider are not published. The maximum custom TTL on a paid plan is the single fact that decides whether USD 7 buys an always-on service or an occasionally-running one; it was not recoverable from the pricing or docs pages, and support would have to answer it. |
|---|
| Evidence note | documented Plan prices, resources and rate caps come from the vendor's pricing page read; the lifecycle and freeze behaviour come from the docs page read. What is missing and would change the record: the maximum custom TTL (which decides whether this is an always-on box at all), the egress terms, and the payment/identity gate. |
|---|
| Parsed numbers | - price USD 7 10 hours a day / month
- price USD 7 / month
- has-free-tier 1
- request-rate 7 requests / minute
- retention-clamped 15 minute
|
|---|