Skip to content
sup3rapp

Glossary

sandbox isolation

Sandbox isolation is the practice of running untrusted code in a confined environment that cannot reach other tenants, projects or shared infrastructure.

Last updated 19 August 2026

Generated code is untrusted code. Not because a model is malicious, but because nobody read it before it ran, and because what a model writes is influenced by whatever text it was given — which can include text written by someone else.

Isolation comes in strengths, and the vocabulary is worth knowing because the industry uses it loosely. Logical isolation means one system enforces separation between tenants in software. Container isolation gives each workload its own filesystem and process namespace, sharing a kernel. Virtual machine or microVM isolation gives each workload its own kernel, which removes the largest class of escape.

The question to ask any AI app builder is not whether it says "secure" but three specifics: what is the boundary, does the preview run inside it, and is one project's boundary shared with anyone else's. Previews are where this quietly slips, because a preview feels like a rendering rather than an execution, and it is an execution.

sup3rapp runs every project in its own sandbox, previews included. Several competitors document strong isolation too — Replit and v0 both publish detail here, and it would be dishonest to claim this as a difference against them.

See it run on your own idea

sup3rapp is in private beta. Access is by request; there is no self-serve signup yet. Tell us what you want to build and we will match you to a batch as places open.