Skip to content

Glossary

Isolated runtime

An isolated runtime executes code sealed off from the network, the file system and other programs. How it protects data in apps built inside a company.

What is an isolated runtime?

An isolated runtime is an environment in which program code runs sealed off. The code only gets the capabilities it is explicitly given. Everything else stays closed to it: the internet, the server's file system, other programs on the same machine. Common forms are containers, virtual machines and so-called isolates, lightweight sandboxes inside a JavaScript engine.

The benefit is simple: even if code has a bug or tries something unexpected, the damage stays limited to its own area. For software written by an AI, that is an important foundation.

Isolated runtime at Openbase.one

At Openbase.one, the code of every app runs in an isolated runtime based on workerd isolates, without network access. An app reaches neither the internet nor other workspaces.

Two more layers sit on top:

  • Apps write no SQL. Every data access goes through the SDK and a capability gateway that checks each call against workspace, app and permissions.
  • Workspaces are separated at database level with row-level security.

For you, that means an app only sees what it is allowed to see and cannot quietly send data outside. Whether an app does the right thing in substance stays your decision; the check before going live and the way back to the previous version help with that.

Describe your first app and watch it go live, checked.

Start for free

Build the app you are missing.
Safe from the first version.

Signed up in 30 seconds, with email, Google or Microsoft. The workspace is ready right away, no setup, no credit card.

Trial with €15 of AI credit. No credit card required.