The Xano CLI now includes ephemeral sandbox environments as a structural safety layer for the code-first development workflow. When a paid user runs workspace push, they'll be blocked and prompted to first push to a sandbox environment.
Here's how it works:
xano sandbox push: changes to your sandbox
xano sandbox review: edit any logic, inspect the snapshot diff, and promote changes to your workspace
From your local workspace state, the CLI spins up an isolated ephemeral environment and surfaces a link for you to review and validate—before anything touches production. Environments time out after 2 hours (with a countdown warning at 15 minutes), and you can extend by 1 hour.
Once validated, the Review & Push flow gives you a human-in-the-loop path to promote changes to a workspace branch. If you want to remove this safety net and enable direct push, an admin can do so in Workspace settings or through the CLI.
Sandbox environments are available for paid plan users (one per user, unless you’re on a Custom pricing plan), and you can learn more in the Xano documentation.