Research investigation R1105 / comparison
Render’s sandbox snapshot restores default to allow-all networking unless restrictions are reapplied
Render documents snapshot restoration as creating a new sandbox, not inheriting the source sandbox’s configuration. Operators must separately reapply network restrictions, intended environment variables for new commands and custom timeout settings.
The comparison is bounded to four supplied Render documentation snapshots and the sampled recovery paths and settings. The recorded evidence cutoff is later than the question timestamp, 2026-11-05T16:30:57.089Z. Readable live pages were corroboration, not an independently timestamped historical archive. The headline leads with the documented configuration consequence rather than research authorship, distinguishing it from the supplied recent launch and research headlines.
The comparison is bounded to four supplied Render documentation snapshots and the sampled recovery paths and settings. The recorded evidence cutoff is later than the question timestamp, 2026-11-05T16:30:57.089Z. Readable live pages were corroboration, not an independently timestamped historical archive. The headline leads with the documented configuration consequence rather than research authorship, distinguishing it from the supplied recent launch and research headlines.
- Dataset ID
- spd:render-sandbox-recovery-which-restrictions-and-processes-survive-each-path-d3713890
- Stable URL
- /research/render-sandbox-recovery-which-restrictions-and-processes-survive-each-path-d3713890
- Version
- Live
- Coverage
- Live collection
- Records
- 0
- Fields
- 7
- Updated
| Entity | Metric | Value | Unit | Observed | Source | Transform |
|---|
Measurement technique
How to read this report
- 01Use the supplied four-document sample: Managing Sandbox Snapshots, Creating and Configuring Sandboxes, Sandboxes SDK for TypeScript, and Limits for Render Sandboxes. Preserve the recorded retrieval cutoff of 2026-11-05T16:32:10.314Z. Recovering this evidence is not a new collection or experiment.
- 02Build an evidence_matrix with idle resumption, runtime-snapshot restoration and filesystem-snapshot restoration as rows. Separate networking, creation-time environment injection, running processes, and runtime/idle timeouts. Label explicit preservation, required reapplication, documented reset and unresolved guarantees separately rather than forcing each category into a single score.
- 03Idle-resumption row: existing sandbox; explicit preservation of the suspended filesystem. Preservation of network restrictions, creation-time environment variables, running processes and custom timeout durations is not explicitly guaranteed in the sampled documentation. The runtime countdown explicitly resets after suspension and resumption; command execution and file transfers reset idle timing, while status checks do not. Sources: https://render.com/docs/sandboxes-creating, https://render.com/
- 04Idle-resumption timeout evidence also comes from https://render.com/docs/sandboxes-sdk-typescript and https://render.com/docs/sandboxes-limits. A reset countdown does not establish a reset of the configured duration to its default.
- 05Runtime-snapshot-restoration row: new sandbox; source network policy is not inherited and defaults to allow-all unless supplied again. New commands use newly supplied environment variables, while resumed processes retain their captured environment. Running processes are preserved through captured filesystem, memory and CPU state. Source timeout configuration is not inherited; absent explicit settings, runtime and idle timeouts default to 24 hours and 15 minutes. Sources: https://render.com/docs
- 06Filesystem-snapshot-restoration row: new sandbox; the same network-policy, new-command environment and timeout reapplication requirements apply. Only the writable filesystem is preserved, not running processes, so processes must be restarted. Snapshot-restoration evidence: https://render.com/docs/sandboxes-snapshots; configuration and defaults: https://render.com/docs/sandboxes-creating and https://render.com/docs/sandboxes-sdk-typescript.
- 07Keep recovery prerequisites alongside the matrix: idle resumption is documented within 30 days and requires available group concurrency. Runtime restoration requires the exact source compute plan; filesystem restoration permits a different supported plan. Treat these as availability constraints, not preservation guarantees.
Sources
Evidence
1 publisher supporting 0 records. Expand a publisher to inspect its cited pages.