Sandboxed apps

Sometimes a team needs a small real application: an explorer for their data, a calculator, a form with some logic behind it. Big companies have started building internal app builders for exactly this, such as Ramp's Glass and Stripe's Harbor (The Pragmatic Engineer wrote about the trend). I am building the same idea into WP as sandboxed apps: you ask Chip for an app, and it writes it, ships it and keeps it running.

A running app inside WP: a table explorer showing column types, null and unique counts and numeric statistics for a customer's table, with the space's tables listed on the left

Built by an AI, kept like real software

Every app lives in a git repository, so engineers can clone it, review it and push changes too. Each push shows whether a person or an agent made it.

The repository's push log: two pushes to main by a human

Every version is a release you can inspect and roll back to with one click.

Release log: seven releases of a table explorer, the first five failed builds, v6 superseded and v7 live, with build logs, a rollback button and the git history below showing a commit by Chip

This screenshot is my favourite: Chip's first five attempts failed to build, it read the errors, fixed them, and version 7 went live. Nobody ever saw the broken versions.

Cheap to run, safe to open

A short file in the repository says how to start the app and which data it may read.

App settings: the idle timeout and the wp-app.json manifest with port, start command, health check, requested data scope, install command and runtime

Each app runs in its own sandbox that goes to sleep when nobody is using it and wakes up on the next visit, so an app nobody is using costs almost nothing. An app can only see the data it asked for, and only as the person viewing it.

The serving sandbox: running from the app's release, with the app's files and manifest in its filesystem