# InsForge (InstaCloud)

Official pricing: https://www.instacloud.com/pricing  
Category: paas · Isolation: vm

## Pricing regimes (raw)

- **Native product; see regime notes** (resource) [alt]
- **InstaCloud compute (microVM service, usage-billed)** (resource): $0.027792/vCPU-h, $0.013896/GiB-h

## Features

Yes: snapshots, memory snapshots, fork/clone, pause/resume, persistent disk, volumes, idle auto-stop, ≥24 h sessions, custom image (Docker or snapshot), start from your own snapshot, your own Docker/OCI image, full VM (own kernel), Docker inside, root, SSH, HTTPS preview URLs, custom domains, self-hosting, open source, SOC 2, HIPAA, SSO, wake on request, live fork (no pause), scheduled runs (cron), EU data residency, scoped API keys, MCP server, automatic snapshots, gVisor or VM (no shared kernel), firewall inside (nftables), extra volumes

No: nested virtualization, browser, desktop GUI, computer-use API, browser + desktop control, anti-bot stealth, CAPTCHA solving, residential IPs, preinstalled agents, public IPv4, raw TCP inbound, egress allowlist, static egress IP, private networking, BYOC, GPU, arm64, Windows, macOS, Python, Node.js, HTTP method/path egress rules, live resize, memory fork, snapshots on demand, agent harness API, hosted agent API (their own agent), inbound access rules, secret proxy, secret proxy for any API, shared volumes

Unknown: everything else. Evidence (source + quote) per feature: https://battleships.dev/data/providers/insforge-instacloud.json → feature_evidence

## Caveats

- Pro $25 monthly/$20 annual with $10 InsForge Compute credits; backend compute is specifically API+Postgres, NOT Custom Compute. Public table 4vCPU/16GB $0.2144/h describes backend project server. Do not price arbitrary containers at it. Custom Compute has separate usage billing, current rate unresolved; free 120h default custom compute. Backend bandwidth 250GB then $0.09/GB.
- Null values mean unknown, not free/unlimited. No model-token cost, tax or unverified ancillary charge included.
- Native browser/device/task/credit prices with unknown CPU/RAM are deliberately non-priceable. Check regime before interpreting any partial resource estimate.
- insforge.dev pricing contradiction: pricing page says the $10 InsForge Compute credit 'Does not apply' to Custom Compute, but docs.insforge.dev/pricing FAQ says Custom Compute on Pro comes with '$10 of InsForge Compute credits to offset it'. InsForge Custom Compute has no published per-hour rate (runs on Fly.io machines). InsForge Free projects pause after 1 week of inactivity.
- InstaCloud compute: new services are always-on by default ('New compute services are always-on and never scale to zero') and bill continuously; scale-to-zero is opt-in; volume-backed services cold-stop instead of suspend; since 2026-09-26 outbound traffic also keeps a scale-to-zero service awake (so an agent calling a model keeps billing). Root disk is rebuilt on every wake; only the volume persists.

## How this provider charges


YC: Spring 2026; directory status **Active**. Research scope: public-product-researched. Source: https://www.ycombinator.com/companies/insforge-instacloud

Custom Compute plus backend service

## Regime table

| Regime | When it applies | How billed | Numbers | Source |
|---|---|---|---|---|
| Native product; see regime notes | Incomplete or non-resource economics: rates remain null, never interpreted as free. | resource; CPU alloc, memory alloc | Unknown or native-unit billing; see facts below | https://insforge.dev/ |
| Free | Plan limits apply | Monthly fee; credits only as stated | fee=0; included usage=$None; concurrent=None; max session h=None | https://insforge.dev/ |
| Pro monthly | Plan limits apply | Monthly fee; credits only as stated | fee=25; included usage=$None; concurrent=None; max session h=None | https://insforge.dev/ |
| Pro annual equivalent | Plan limits apply | Monthly fee; credits only as stated | fee=20; included usage=$None; concurrent=None; max session h=None | https://insforge.dev/ |
| Enterprise | Plan limits apply | Monthly fee; credits only as stated | fee=None; included usage=$None; concurrent=None; max session h=None | https://insforge.dev/ |
| Retained disk / GiB-month | Lifecycle/scope must be checked | Native add-on | unverified, not $0 | https://insforge.dev/ |
| Snapshots / GiB-month | Lifecycle/scope must be checked | Native add-on | unverified, not $0 | https://insforge.dev/ |
| Egress / GiB | Lifecycle/scope must be checked | Native add-on | unverified, not $0 | https://insforge.dev/ |
| IPv4 / month | Lifecycle/scope must be checked | Native add-on | unverified, not $0 | https://insforge.dev/ |

## Verified billing facts and gotchas

1. Pro $25 monthly/$20 annual with $10 InsForge Compute credits; backend compute is specifically API+Postgres, NOT Custom Compute. Public table 4vCPU/16GB $0.2144/h describes backend project server. Do not price arbitrary containers at it. Custom Compute has separate usage billing, current rate unresolved; free 120h default custom compute. Backend bandwidth 250GB then $0.09/GB.

## Worked example

Requested: 4 vCPU/8 GiB, 50 simultaneous × 8 h/day × 22 days = **8,800 instance-hours**, 30% CPU; 50 GiB snapshots and 100 GiB egress. A month is 730 hours only when explicitly used in rate conversion.

**Total: unknown.** This product does not publish a verified complete 4-vCPU/8-GiB tariff and/or the service bills a different unit. Fifty concurrent instances and eight-hour sessions are not automatically supported. Neither 30% utilization nor retained snapshots can be converted into free resources. Use the native plan terms above and request the missing CPU/RAM, retention, egress and concurrency quote.

## Sources and coverage

- https://www.ycombinator.com/companies/insforge-instacloud
- https://insforge.dev/
- https://insforge.dev/pricing
- https://insforge.dev/llms.txt

Page captures and documentation indexes/bundles are in `raw/`; provider JSON lists the evidence paths. HN query results were captured separately as `<id>--hn.txt`; they are discovery leads, not current tariff authority. Downloaded docs do not imply every feature was verified; unsupported assertions remain null.