Skip to Content
TestingCheckpoints and rollback preview

Checkpoints and rollback preview

The checkpoint service defines records, retention behavior, REST/MCP operations, and a rollback state machine for apps.

No real recovery yet: the active snapshot adapter fabricates VM and database snapshot identifiers. Stop/start/health stages are simulated, and no disk or database state is captured or restored. A checkpoint created today is not a backup and must not be used as a recovery control.

What can be tested

The preview surface lets integration developers exercise:

  • manual checkpoint creation and listing;
  • pin, unpin, delete, and retention metadata;
  • ownership checks;
  • rollback state transitions; and
  • creation of a pre-rollback safety record.

The following MCP tools expose that control plane:

ToolPreview behavior
create_checkpointCreates a record with stub snapshot identifiers
list_checkpointsLists owned records and reported usage
pin_checkpointExempts a record from retention pruning
delete_checkpointDeletes an unpinned record
rollback_appExercises the simulated rollback sequence

Do not describe a successful response from these tools as a recovered app.

Production recovery today

For an immutable app deployment, recover from source and separately managed data:

  1. identify a known-good Git revision;
  2. confirm the database or object-store backup exists and can be restored;
  3. queue a new immutable deployment for that revision;
  4. restore data through the service’s documented recovery procedure; and
  5. verify application health and user-visible behavior before switching traffic.

Keep backup retention, restore testing, and recovery objectives outside the checkpoint preview until real adapters have shipped and passed a restore drill.

What remains

  • real VM and database snapshot primitives;
  • rollback integration with the immutable variant deployment pipeline;
  • failure-atomic restore behavior;
  • deploy hooks that create verified checkpoints;
  • capacity and retention enforcement against real storage; and
  • backup/restore drills with captured evidence.