Make it always-on.
Deploy the included server runtime to a persistent host, then connect this control plane.
Deploy your runtime
The project includes a Node.js runner, a Chromium Playwright worker, a Selenium container, and persistent web hosting. Download the project from the editor to get the runner directory.
Prepare a persistent host
Use a Linux host with Docker, at least 4 GB RAM, and an HTTPS reverse proxy. The host must remain powered on; this app cannot provision a machine or guarantee uptime.
Start the Docker services
Create a random runner token, configure trusted browser hosts, and start the services. Named volumes keep your site and execution records across restarts.
cd runner cp .env.example .env # Set RUNNER_TOKEN and your approved browser hosts in .env docker compose up -d --build
Connect your control plane
In the editor’s Secrets panel, set RUNNER_URL to your HTTPS runner origin and RUNNER_TOKEN to the same token used by the runtime. Configure outbound access for that runner host if prompted.
Runner connection
Only the owner or an administrator can access runner status and execute commands.
What stays persistent
Real users & sessions
Built-in authentication manages account records.
Web content & job history
Stored in the runner’s persistent Docker volume.
Runner credentials
Backend-only Secrets; never bundled in the browser.
24/7 is a deployment property
The runtime has restart policies and health checks. Continuous availability also depends on your hosting provider, power, networking, backups, and monitoring. Selenium and Playwright execute on the deployed runner, not in this preview.