Deploy pinned versions
Promotion happens through the instance repo instead of a live-edit control plane.
Self-host for production
Production should stay under your control.
Move Big Rocks is self-hosted by default in production. The sandbox exists to help you evaluate quickly, but the real deployment model is customer-controlled: one instance repo, one Linux host or fleet, one deliberate runtime and extension lifecycle.
Production shape
The deployment model should stay boring in the right ways.
One Go service, PostgreSQL, predictable extension packaging, and a customer-controlled instance repo create a production shape that agents and operators can reason about.
Keep ownership explicit
The customer owns the host, secrets, domains, and runtime configuration.
Promote from trial to real
Export sandbox data and move cleanly into self-hosted production when ready.
Move Big Rocks
Use the same deliberate system in evaluation, delivery, and real operations.
The point of the site is to make the next step obvious. The point of the product is to keep your work, knowledge, and agent operating model coherent after the site is out of the picture.