Day-2 operations
Day-2 tasks for operating the platform underneath your environments — SSH access, backups, and restore.
This chapter covers day-2 tasks: things you do once an environment is running and you need to reach inside it. Most customers never need to touch this section — the Hub handles the common cases without an SSH terminal.
Before opening a terminal, check whether the Hub already covers what you need:
- Adding an SSH public key? See Settings → SSH keys for per-environment keys, or Settings → Organization → SSH keys to propagate a key to all your environments at once.
- Triggering or reviewing a backup? See Settings → Backup to browse snapshots and kick off a restore from the Hub UI.
If those don't cover your situation — you need to run a Magento CLI command, inspect a log file, restore a specific file from a snapshot, or do any other direct server work — the pages below are for you.
What "operations" means here
StoreFrame environments are full Linux VMs running a containerized stack. The Hub manages provisioning, scaling, and routine maintenance automatically. What it does not do is give you a shell. That's what SSH access is for.
Backups run automatically on a schedule — you don't need to configure them. The system backs up your entire project directory daily to encrypted off-site storage, retains snapshots for up to 12 months, and encrypts everything at rest. You can restore from the Hub UI or directly over SSH using the restic-restore helper.
Pages in this chapter
Users and SSH — SSH port, the app user, sudo escalation, and how SSH key propagation works.
Backups — What gets backed up, the retention schedule, and how to restore — via the Hub or the command line.