How Figma Manages Sandboxes at Scale
Comments on “How Figma Manages Sandboxes at Scale”
Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked
Figma describes Nimbus, an internal platform that manages sandboxes for AI-generated code across several cloud providers. Products request a sandbox through a configuration file, and Nimbus handles provider choice, network policy and health checks. Outside trusted hosts it allows only body-less read requests. Figma reports that warm pools cut provisioning latency by 90% and raised availability from 99% to 99.95%. These figures come from Figma itself, with no independent verification. The design lets teams swap providers without changing the product interface.
Why it ranked
No. 19 of 139 with a score of 0.65. The panel rated it highest on new information (0.91) and technical depth (0.84), lowest on audience breadth (0.48). Placed No. 19, No. 45 by score alone: the placement terms moved other stories past it.
- AI judgeJudge 2claude-haiku-5-5
- Detailed engineering write-up of a company's internal sandbox platform with concrete design, warm pools, security policy and reliability techniques; useful to infra builders, though a single company's system with limited independent evidence.
- AI judgeJudge 3gpt-5.6-luna
- A detailed engineering account of multi-provider sandbox orchestration for AI workloads, covering isolation, credential handling, network policy, warm pools, reliability, control loops, and simulation. It is company-specific but broadly useful to AI infrastructure builders.
Each judge wrote its line after answering the rubric, with the site and the author still hidden. Every answer behind this is in the table under Score.
Score
0.65total under rubric v2.3
- Significance0.57
- Reader interest0.79
- Audience breadth0.48
- Practical relevance0.75
- Substantiated0.66
- Technical depth0.84
- New information0.91
- Counts against: Promotional0.12
- Counts against: Overclaim0.17
Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).
| Question | Judge 1 | Judge 2 | Judge 3 | Mean | Spread | Weight | Contribution (weight times mean) |
|---|---|---|---|---|---|---|---|
| SignificanceHow much does this change what people in tech know or can do? | 0.59 | 0.40 | 0.72 | 0.57 | 0.32 | +0.24 | +0.137 |
| Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on? | 0.70 | 0.80 | 0.88 | 0.79 | 0.18 | +0.26 | +0.206 |
| Audience breadthHow many people who build technology does it concern? | 0.37 | 0.50 | 0.58 | 0.48 | 0.21 | +0.13 | +0.063 |
| Practical relevanceHow useful is it to someone who builds software or tech products? | 0.72 | 0.70 | 0.82 | 0.75 | 0.12 | +0.22 | +0.165 |
| SubstantiatedHow well is it backed? Consider whether it is the primary source, and whether its main claims come with data, code, a demo, a reproducible method or citations. | 0.60 | 0.60 | 0.78 | 0.66 | 0.18 | +0.05 | +0.033 |
| Technical depthHow technically substantive is it? | 0.90 | 0.80 | 0.82 | 0.84 | 0.10 | +0.05 | +0.042 |
| New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)? | 0.86 | 0.90 | 0.96 | 0.91 | 0.10 | +0.05 | +0.045 |
| PromotionalIs it mainly marketing with little substance (a press release, ad or sponsored post with no real information)? A launch post that carries real news is not promotional. | 0.12 | 0.15 | 0.08 | 0.12 | 0.07 | −0.19 | −0.022 |
| OverclaimDo the headline or conclusions claim more than the body supports? | 0.18 | 0.20 | 0.12 | 0.17 | 0.08 | −0.11 | −0.018 |
| Sum of contributions | +0.650 | ||||||
| Claim-check penalty | 0.000 | ||||||
| Total, as published | 0.650 | ||||||
Spread is the highest minus the lowest judge answer. marks a spread above 0.40: the judges disagree, and the story is marked contested.
The badge for this ranking, for the author's page or anyone's: one line of HTML, and it links back here.
<a href="https://rubric.hrih.si/editions/2026-11-05/19/"><img src="https://rubric.hrih.si/badge/2026-11-05/19.svg" alt="Ranked #19 on Rubric, 5 Nov 2026" width="238" height="28"></a>Claim check
Claim check: 8 no source given. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.
No source givenNumber
Figma's warm sandbox pools cut provisioning latency by 90% compared with spinning up a new sandbox for each request.
The article gives no link or citation for it.
The article says “Warm pools cut our provisioning latency by 90% compared to spinning up a new sandbox each time a request comes in”
The source says No source to compare with.
No source givenNumber
Nimbus's provisioning availability rose from 99% to 99.95% as a result of the warm pool and automated provider selection.
The article gives no link or citation for it.
The article says “Nimbus’s provisioning availability increased from 99% to 99.95% as a result of the warm pool and automated provider selection”
The source says No source to compare with.
No source givenNumber
Figma's goal was for Nimbus to return a provisioned sandbox in under one second.
The article gives no link or citation for it.
The article says “our goal was for Nimbus to return a provisioned sandbox in under one second”
The source says No source to compare with.
No source givenDate
Nimbus launched internally in November 2025.
The article gives no link or citation for it.
The article says “Since launching internally in November 2025, Nimbus has grown into shared infrastructure for multiple product surfaces”
The source says No source to compare with.
No source givenGeneralization
Figma's namespace design is similar to the Kubernetes operator pattern, where the product declares its intent and the control plane owns the work needed to support it.
The article gives no link or citation for it.
The article says “Nimbus’s namespace design is similar to the Kubernetes operator pattern, where the product declares its intent while the control plane owns the work required to support it”
The source says No source to compare with.
No source givenNumber
For hosts outside the trusted list, Nimbus permits only body-less GET, HEAD or OPTIONS requests, blocking POST, PUT and any request with a body.
The article gives no link or citation for it.
The article says “For destinations outside that list, Nimbus permits only read requests—GET, HEAD, or OPTIONS—with no request body”
The source says No source to compare with.
No source givenCausal conclusion
Automation built into Nimbus has made incidents rarer, because it can reroute traffic to a healthy provider automatically instead of paging an on-call engineer.
The article gives no link or citation for it.
The article says “Because we built so much automation into the platform, incidents are now rarer”
The source says No source to compare with.
No source givenNumber
Figma expected to manage tens of thousands of sandboxes across multiple products with differing memory and network permission requirements.
The article gives no link or citation for it.
The article says “we’d soon be managing tens of thousands of sandboxes across multiple Figma products, all with different memory and network permission requirements”
The source says No source to compare with.
Also covered by
No other coverage was clustered with this story.
Elsewhere
Elsewhere: HN 3 pts, not on front page
Recorded for context only, checked 5 Nov 2026, 05:46 UTC. It played no part in the ranking.