Deploying the platform
How an operator stands up a hosted erun platform (for example erunpaas.com). You scaffold the platform's deploy artifacts and build a custom runtime image in your agent environment, then a runtime environment runs that image while erun deploy, erun terraform apply, and skills apply the Kubernetes + Terraform — you don't hand-run kubectl or terraform.
Release flow
ERun's release flow is repository-wide: a release moves all modules together (erun-cli, erun-common, erun-mcp, erun-ui, erun-devops).
Cloud setup
This page is for whoever sets up shared cloud capacity for a team. For the day-to-day Operator view, see Cloud contexts.
Data retention
The erun-backend-db component can run a daily sweep that deletes old rows from a handful of high-growth tables (reviews, comments, releases, AI sessions, invites) so a tenant's database doesn't grow forever. It's off by default — deploying or upgrading erun-backend-db never starts deleting rows on its own — and turning it on drops you into a report-only mode first, so you see what a sweep would remove before anything is actually deleted. This page covers turning it on safely: previewing a sweep, enabling it, checking or changing the bounds it enforces, and confirming what a scheduled run actually did.