Waymaker
Waymaker Host

Workspace Sandbox

Learn about Workspace Sandbox in WaymakerOS.

SandboxSchemaTesting

Test schema changes safely before applying them to production. A sandbox is a separate copy of your workspace's data layer where you can add tables, modify columns, and experiment without affecting live data.

How Sandboxes Work

Production Workspace
  └── Sandbox Workspace (isolated copy)
       ├── Make changes here
       ├── View differences (diff)
       ├── Push changes to production
       └── Or pull production state to reset

Your production workspace is the live version. A sandbox workspace is a safe testing environment linked to it. Changes in the sandbox do not affect production until you explicitly push them.

Creating a Sandbox

  1. Open Host
  2. Go to the Sandbox section
  3. Click Create Sandbox

A new sandbox workspace is created with a copy of your current production schema. You can now make changes without risk.

CLI

waymaker workspace create-sandbox

Making Changes

In your sandbox workspace, you can:

  • Create new tables
  • Add or remove columns
  • Change column types
  • Modify access rules

These changes only exist in the sandbox until you push them to production.

Viewing Differences

Before pushing, review what has changed between your sandbox and production:

  1. Go to the Sandbox section in Host
  2. The Schema Diff view shows:
Change TypeMeaning
AddedNew tables or columns that exist in the sandbox but not in production
RemovedTables or columns that were deleted in the sandbox
ModifiedColumns where the type or configuration changed

CLI

waymaker workspace diff

Pushing to Production

When you are satisfied with your changes:

  1. Review the diff to confirm what will change
  2. Click Push
  3. The schema changes are applied to your production workspace

This is a one-way operation — your sandbox changes overwrite the corresponding production schema. Tables and columns not touched in the sandbox are left unchanged.

CLI

waymaker workspace push

Pulling from Production

If you want to discard your sandbox changes and start fresh:

  1. Click Pull
  2. Your sandbox schema resets to match the current production state

This is useful if production has changed since you created the sandbox, or if you want to abandon your experiments and start over.

CLI

waymaker workspace pull

Sync History

Every push and pull operation is logged. The Sync History panel shows:

  • Who initiated the operation
  • When it happened
  • Whether it was a push or pull

This gives your team a clear audit trail of schema changes.

Best Practices

  • Always review the diff before pushing — check that only the changes you intended are included
  • Pull before starting if your sandbox has been idle for a while — production may have changed
  • Use descriptive table names so the diff view is easy to read
  • One change at a time — push focused changes rather than large batches to keep the history clean

Next Steps