InstaBox: Product, team and how it was built
InstaBox (Cloud Linux machines for AI agents, United States): Self-serve paid plans on sale, November 2026. Evidence grade E: no revenue figure was checked. Team: 2 founders; Y Combinator lists a team size of 6 in November 2026, and the company has 2 open roles. Launched July 2025; still running.Added
- Outcome
- Self-serve paid plans on sale, November 2026
- Evidence
- E no revenue figure was checked
- Launch
- July 2025
- Status
- Still running
- Team
- 2 founders; Y Combinator lists a team size of 6 in November 2026, and the company has 2 open roles
- Outside funding
- Y Combinator Spring 2026; no amount found
- Main channel
- Not stated
What is not verified
No revenue figure was found, so the story is grade E. The InstaBox home page text, documentation, blog, changelog, Y Combinator page and InsForge pages were read. A reader could look for a press interview or a payment-processor statement. No source states that a customer has paid. The 75% beta-user figure and the weekly contribution counts are the founders' own statements. This story is grade E: the business is real and its product, price and customers are described from public pages, but no revenue figure was checked. Aiolum shows it as an idea worth studying, not as proof that it makes money.
InstaBox sells microVMs to AI agents. A microVM is a small virtual machine that can pause and resume in under a second. Each machine has Debian Linux, Docker, a desktop and a browser for a coding agent, a program that writes and tests code on its own. The company is InsForge, Inc., and InstaBox is one of its products, next to a backend platform for coding agents.
Hang Huang and Tony Chang founded InsForge, which released its open-source version on 31 July 2025. An archived copy of its code page dated 3 August 2025 already describes it as a backend for AI agents. InstaBox started a free beta on 14 October 2026 and added paid plans on 20 October 2026. Y Combinator lists the company with a team size of 6.
No revenue figure was found, so the story is grade E. The headline is a status fact from the company's own pages. Free, Pro, Builder and Team plans exist, and a plan is bought by card or Alipay on a billing page. No source states that a customer has paid for InstaBox.

Why did InstaBox work?
Four causes, in the order they mattered. Each one is a reusable lesson.
The founders built it to fix their own agent bottleneck
Tony Chang wrote that his laptop froze at five agents and that agents shared ports and settings. In July 2026 the team moved its agents to cloud microVMs. He wrote that weekly GitHub contributions rose from about 580 to about 1,200 after the move. This is the company's own account.
Idle machines pause, which keeps the free plan affordable
Hang Huang wrote that a machine pauses after 30 idle minutes and that its processor and memory then return to a shared pool. He said this lets the company oversubscribe its own bare-metal servers. The free plan is one 4 vCPU machine.
It bills machines by the second while they run
The documentation says a paid machine is billed for its vCPUs and memory only while it runs. A paused machine costs only its disk. Each paid plan includes credits equal to its fee, so a small user pays the fee.
How it was built
These details come from the company's blog, changelog and documentation. They are grade C. [6, 1, 9, 3, 5]
- Tony Chang wrote that the control plane runs on Firecracker, a microVM monitor with native snapshots. A machine starts from a snapshot in under two seconds.
- The home page text says a machine is a Firecracker microVM that runs Debian 13 with Linux kernel 6.18.60 by default.
- A blog of 22 October 2026 says the company uses WorkOS for sign-in and to block spam sign-ups.
- The changelog says the documentation runs on Mintlify since 6 November 2026.
- Hang Huang wrote that the company runs on its own bare-metal servers.
- The company offers a command line, TypeScript and Python software kits, an MCP server, webhooks and a GitHub Actions runner.
Tools named in the sources
Each one opens its page in the Tools tab, with every story that uses it.
Who tried this before InstaBox, and why did they fail?
Three companies in our database of failed startups built cloud developer platforms and closed. The values below are from that database, were read on 12 November 2026 and are not independently verified.
Nitrous.io
The promiseInstant cloud development environments, a code-anywhere editor that removed local set-up.
Why it diedThe record says it was squeezed between Amazon's Cloud9, which Amazon could offer cheaply, and the bundling of developer tools into larger platforms.
Parse
The promiseA backend-as-a-service platform that let mobile developers skip building servers.
Why it diedThe record says Facebook bought it in 2013, then shifted its priorities, while Google's Firebase offered a free tier that Parse could not match.
DotCloud
The promiseA platform-as-a-service that spared developers from managing servers.
Why it diedThe record says the company turned to Docker, the container tool it created, and the original platform was left behind.
The failed startups come from our database of 1,749 dead startups, retold here in our own words. Its entries are AI-assisted summaries of public sources, so these cards carry no evidence grade.
What changed
The three records show two pressures. A larger company gave the same service away or bundled it, as the records say of Amazon and Google. Or the company's own technology became the better product, as Docker did for DotCloud. InstaBox sells machines that other clouds also rent.
The company's answer is the customer: AI agents that need a whole computer, paused when idle. Agent work comes in bursts, Hang Huang wrote. The sources do not show whether enough teams pay for that to last.
Can one person copy InstaBox now?
The idea can be copied; the demand is not shown.
A small team that runs many coding agents can sell the machines it built for itself. The sources show a price list, a billing page and a company that says it ran into the problem first. They show no revenue and no paying customer. A reader should treat this as a pattern, not as proof that it earns.
Where it is still open: Machines for other long-running agent jobs: browser testing, mobile app testing, build servers and continuous integration.
- 1Run your own agents on isolated machines until the setup works for you.
- 2Pause idle machines to return their processor and memory to a shared pool.
- 3Offer a free machine so engineers can test it without paying.
- 4Charge a monthly fee that includes usage, and bill the rest by the second.
How much revenue does InstaBox make?
Each row shows the evidence grade and the source numbers from the list at the end of this page. The grades are explained in How Aiolum verifies.
| Fact | Value | Grade | How we know | Sources |
|---|---|---|---|---|
| What is sold | A Linux machine for each AI agent, billed by usage | C | The company describes a Firecracker microVM with 4 vCPUs and 8 GiB of memory by default. Y Combinator lists it as cloud computers for AI agents. | [1, 10] |
| Company and names | InsForge, Inc. is the company; InstaBox and InstaCloud are its products | C | The InstaBox blog says InstaBox is built by InsForge. The InsForge home page links InstaCloud in its footer. The InstaCloud page carries the copyright line of InsForge, Inc. Y Combinator shows the company as InstaBox. | [7, 16, 19, 10] |
| Start | Founded in 2025; open-source release on 31 July 2025 | C | Y Combinator says Founded: 2025. The founder wrote that the open-source version of InsForge launched on 31 July 2025. An archived copy of insforge.dev dated 18 February 2025 is titled "InsForge | No-code Backend". No earlier name was found. | [10, 12, 21, 17] |
| Agents from the first release | Yes, in the code page of 3 August 2025 | C | The archived GitHub page calls InsForge "the Agent-Native Supabase Alternative" and tells the reader to connect an AI agent to it. | [14] |
| InstaBox beta and launch | 14 October 2026 | C | Hang Huang wrote on 19 October 2026: "Since we launched on Oct 14, beta users have been using InstaBox for free." | [5] |
| Founders | Hang Huang, founder and CEO; Tony Chang, founder and CTO | C | Y Combinator lists both as active founders. Both write the company's blog posts. | [10, 4] |
| Team size | 6 per Y Combinator; 2 open roles | C | Y Combinator lists Team Size: 6. The careers page of InsForge lists two open roles. The company published no headcount. | [10, 18] |
| Funding | Y Combinator Spring 2026; no amount found | C | Y Combinator lists the batch, and the InsForge home page says Backed by Y Combinator. No funding amount or investor was read. | [10, 16] |
| Prices | Pro US$20 a month; Builder US$100; Team US$500 | C | The company's documentation lists these plans and the unit prices. Each paid plan includes credits equal to its fee. | [2, 1] |
| How a plan is bought | Card on the Billing page; Alipay for Pro and Builder | C | The changelog says to subscribe with a card on the Billing page. A blog of 5 November 2026 adds Alipay at checkout. | [3, 8] |
| Open-source traction | 13,300 stars on the InsForge repository | C | The GitHub page showed 13.3k stars on 12 November 2026. The founder wrote that the project had 500 stars two weeks after its release. | [15, 12] |
| Beta use | 75% of beta users had one active machine | C | Hang Huang stated this in the pricing blog of 19 October 2026. No count of users was given. | [5] |
How to read this table. Grade C means the company or a directory states the value. No value here is grade A or B. No value is calculated on this page.
| Plan | Per month, billed yearly (US$) | Per month, billed monthly (US$) | Limit |
|---|---|---|---|
| Free | 0 | 1 machine of 4 vCPU and 8 GiB; 5 snapshots; paused after 30 idle minutes; 100 GiB egress a month | |
| Pro | 20 plus usage | US$20 of credits; up to 100 machines at once; machines up to 8 vCPU and 16 GiB; email support | |
| Builder | 100 plus usage | US$100 of credits; up to 200 machines at once; machines up to 16 vCPU and 32 GiB | |
| Team | 500 plus usage | US$500 of credits; up to 500 machines at once; machines up to 32 vCPU and 64 GiB; priority support | |
| Usage: vCPU | 0.004 per vCPU-hour | Billed by the second, only while a machine runs | |
| Usage: memory | 0.00225 per GiB-hour | Billed by the second, only while a machine runs | |
| Usage: egress | 0.02 per GiB | Beyond the plan's monthly egress; ingress is free |
The documentation says each paid plan includes monthly credits equal to its fee, and usage beyond them is billed at the unit prices. Only a monthly price is published. Enterprise has no published price. Early accounts keep five free machines until 1 December 2026.
When did InstaBox launch, and how did it grow?
From an open-source backend in July 2025 to a priced cloud-machine product in October 2026.
- 31 July 2025CThe founders release the open-source version of InsForge with authentication, a database and file storage. [12]
- 18 November 2025CThe company announces the official launch of InsForge, a backend for AI coding agents, and names Zeabur and Peak Mojo as early users. [13]
- 18 May 2026CThe company posts its Launch YC page for InsForge, written by Hang Huang and Tony Chang. [11]
- 14 October 2026CInstaBox launches as a free beta for cloud machines for AI agents. [5]
- 20 October 2026CThe company adds Free, Pro, Team and Enterprise plans, with Pro at US$20 a month and Team at US$500 a month. [3, 5]
- 3 November 2026CThe company adds a Builder plan at US$100 a month between Pro and Team. [3]
What could go wrong for InstaBox?
The risks are the mirror image of the causes above.
What is not verified
No revenue figure was found, so the story is grade E. The InstaBox home page text, documentation, blog, changelog, Y Combinator page and InsForge pages were read. A reader could look for a press interview or a payment-processor statement. No source states that a customer has paid. The 75% beta-user figure and the weekly contribution counts are the founders' own statements.
Names, a sister product and a waitlist
The Y Combinator launch post of 18 May 2026 speaks of InsForge, and the company page now shows InstaBox. InsForge also lists InstaCloud, a separate product. InstaBox used a waitlist and invite codes in October 2026. Hang Huang wrote on 22 October 2026 that Pro users skip the waitlist. The newest dated mention of the waitlist is a blog of 23 October 2026. The documentation still lists an error named "invite_required", so a free account may still need an invite code.
Badges, counters and quotations have no second source
The company says it is built by InsForge, which "completed a SOC 2 Type II audit". No report was read. The same blog shows SOC 2 and HIPAA badges in the site footer. The InsForge home page shows counters of projects, database size, storage and egress with no readable values. It also shows eight quotations from X posts about InsForge, which were not checked on X. The InstaBox home, terms and privacy pages need a script. Only the Markdown copy of the home page was read.
Free machines attracted abuse
Hang Huang wrote that bots signed up hundreds of accounts to mine cryptocurrency, which broke the terms. The company limited the free plan to one machine. A later blog says WorkOS helps block spam sign-ups. The sources show no regulator or store action against the product.
Sources
The grade next to each source is the best grade that the source can support. "Read in full" means that the text of the page was downloaded and the numbers were checked in it.
- C InstaBox home page as Markdown (llms.txt)Read in full on 12 November 2026. The home page needs a script, so this is its text copy. Source for the product, machine, plans and unit prices.
- C InstaBox documentation: PricingRead in full on 12 November 2026. Source for the plans, the included credits, the unit prices and the free-machine rule.
- C InstaBox changelogRead in full on 12 November 2026. Source for the plan dates, the card checkout, the Builder plan and the Mintlify documentation.
- C InstaBox blog indexRead in full on 12 November 2026. Source for the post dates and authors, the earliest on 2 September 2026.
- C InstaBox blog, 19 October 2026, by Hang Huang: InstaBox PricingRead in full on 12 November 2026. Source for the 14 October 2026 launch, the free plan, idle pausing, abuse and beta use.
- C InstaBox blog, 18 October 2026, by Tony Chang: Why We Moved Our Coding Agents to the CloudRead in full on 12 November 2026. Source for the founders' own agent problem, Firecracker and the contribution counts.
- C InstaBox blog, 10 November 2026, by Tony Chang: Our Trust Center Is LiveRead in full on 12 November 2026. Source for InsForge as the builder of InstaBox and the SOC 2 statement.
- C InstaBox blog, 5 November 2026, by Tony Chang: Pay for InstaBox with AlipayRead in full on 12 November 2026. Source for Alipay at checkout for Pro and Builder.
- C InstaBox blog, 22 October 2026, by Hang Huang: Secure Auth with WorkOSRead in full on 12 November 2026. Source for WorkOS, the waitlist and the Pro express lane.
- C Y Combinator company page: InstaBoxRead in full on 12 November 2026. Source for the founders, the batch, the year founded, the team size and the launch post.
- C Y Combinator Launch post: InsForge, the backend platform for AI-native developersRead in full on 12 November 2026. Source for the authors and the post date of 18 May 2026.
- C InsForge blog, 21 August 2025, by Hang Huang: Focus or DieRead in full on 12 November 2026. Source for the open-source release on 31 July 2025 and the 500 stars.
- C InsForge blog, 18 November 2025: InsForge LaunchRead in full on 12 November 2026. Source for the official launch and the early users named.
- C Internet Archive copy of the InsForge GitHub page, 3 August 2025Read in full. Source for the agent-native description in the first week after the open-source release.
- C GitHub page: InsForge/InsForgeRead the top of the page on 12 November 2026. Source for the 13.3k stars and the Apache-2.0 license.
- C InsForge home pageRead in full on 12 November 2026. Source for the company name in the footer, the Y Combinator mark, the counters and the quotations.
- C InsForge blog indexRead in full on 12 November 2026. Source for the earliest post, dated 21 August 2025.
- C InsForge careers pageRead in full on 12 November 2026. Source for the two open roles.
- C InstaCloud home pageRead in full on 12 November 2026. Source for InstaCloud as a separate InsForge product.
- C Database of failed startups, local exportRecord pages read on the website on 12 November 2026. AI-written summaries, not independently verified. Source for the failed predecessors.
- C Internet Archive copy of the InsForge home page, 18 February 2025Read in full on 12 November 2026. Only the page title could be read. Source for the InsForge name on the site before the open-source release.
Run this company? Send corrections or a verified figure to aiolum@livyden.com