Posit Cloud

Free allowance: USD 0 forever: 25 compute hours a month, 1 GB maximum RAM, 1 CPU, 1 hour maximum execution, 25 projects and 3 concurrent projects
Verdict: caveatusable, with a named limit or an unprobed read path
Cost: free tier
Identity: emailno card, no phone
Binding limit: volume-quota25 compute hours per month, then the plan stops; 1 hour maximum execution per run
Evidence: documented4 sources; a first-party page was read and the sentence quoted
Freshness: stale on 2026-11-24checked 2026-10-24 (live); stale on 2026-11-24

Free tier	USD 0 forever: 25 compute hours a month, 1 GB maximum RAM, 1 CPU, 1 hour maximum execution, 25 projects and 3 concurrent projects unit hours; metered on wall-clock; The only provider that publishes a monthly compute-hour counter.
Price	none stated
Limits	volume-quota (binding) 25 compute hours per month, then the plan stops source volume-quota (binding) 1 hour maximum execution per run source
Binding	volume-quota 25 hours a month is four hours a week, and the 1-hour execution cap means no single job can use even one day of it
Identity	email a Posit Cloud account; the plans page states no card for Cloud Free
Egress	no egress allowance or price published
Per-object cap	not applicable: the unit is a session, not an object
Retention	25 projects persist on the free plan; the pricing page states no expiry
Interface	rest, cli RStudio and Jupyter projects in a browser
Tooling	the web IDE; project files and a console
Composes with	25 hours a month of 1 GB R or Python for small scripted jobs, capped at one hour per execution
Reliability	no reliability event recorded
Notes	1 GB RAM is the smallest shape. The 1-hour execution cap rules it out for anything long, and 25 hours a month is the tightest published allowance after Binder.
Evidence note	documented every number is from the vendor's plan table read. Nothing was run, so enforcement is unproven.
Parsed numbers	price USD 0 10 hours a day / month price USD 0 / month has-free-tier 1 volume-quota 1 hour

Evidence 4

date	source	what it proved
2026-10-24	posit.cloud/plans	quoted: '\| Compute Hours \| 25 hours per month \|' for Cloud Free
2026-10-24	posit.cloud/plans	quoted from the plan row, Free column first: '\| Max RAM \| 1 GB \| 8 GB \| 32 GB \| 16 GB \| 1 GB \|' and '\| Max CPU \| 1 CPU \| 2 CPUs \| 8 CPUs \| 4 CPUs \| 1 CPU \|'
2026-10-24	posit.cloud/plans	quoted: '\| Max Execution \| 1 hour \|' for Cloud Free
2026-10-24	posit.cloud/plans	quoted from the plan rows, Free column first: '\| Projects \| 25 \| Unlimited \| Unlimited \| Unlimited \| 25 \|' and '\| Concurrent Projects \| 3 \| Unlimited \| Unlimited \| Unlimited \| 3 \|'; the Free column header reads '$0 / forever'

More fields 12

shape	`{"vcpu": 1,"ram_gib": 1,"disk_gib": null,"gpu_class": null,"gpu_count": null}`
billing model	free
term	none
m10h usd	0.0
m24h usd	0.0
price arithmetic	USD 0.00 on Cloud Free; the paid Basic tier is USD 25 a month for 150 hours and 8 GB
free tier kind	free-forever-with-quota
unattended	no
unattended mechanism	unverified: no scheduler is described on the plans page, and the 1-hour execution cap bounds any run
network out	`{"allow_outbound": true,"allow_inbound_listen": false,"ports": "unstated","static_ip": false,"ipv6": false,"per_session_bytes": null}`
session cap	`{"wall_clock_min": 60,"idle_reap_s": null,"restart_required": false,"note": "1 hour maximum execution on Cloud Free"}`
units	RAM and disk are quoted in the vendor's own decimal GB, not GiB. The ram_gib and disk_gib keys carry the vendor's number unconverted, so where a vendor writes 30 GB the key holds 30 and the true value is about 27.9 GiB. No conversion was performed.

Unknown values 1