Keep it online
Sites are permanent by default. Use this mode for a continuously available development lab, internal tool or long-running test environment.
Disposable does not mean short-lived
Running SpawnWP long-term.
A SpawnWP site can stay online for months or longer. “Disposable” describes the ability to reset, rebuild or destroy an environment — not an expiration date. Long-running sites need the same deliberate updates, backups and monitoring as any self-hosted WordPress server.
The short answer
Permanent when you need it. Disposable when it helps.
Let it expire
Choose a lifetime when the environment is a demo, experiment or short task. The expiry timer removes the site when its lifetime ends.
Keep the workflow reproducible
Blueprints, snapshots and scripted operations make it easier to recover or recreate a site without treating one server state as irreplaceable.
Hardening baseline
Operate the server like infrastructure you own.
Protect the control plane
Use a passkey or strong password plus TOTP, store recovery material safely and review authentication events. The cockpit orchestrates Docker and Nginx as root, so keep it on a server dedicated to SpawnWP workloads.
Limit network exposure
Allow public HTTP/HTTPS and restrict administrative SSH to trusted sources in the provider firewall. Databases, Mailpit, Adminer and PHP services stay behind the private or authenticated boundaries.
Patch deliberately
Keep the host, SpawnWP control plane, WordPress core, plugins, themes and base images current. Take a snapshot before changes and review release notes when updating SpawnWP.
Watch the boring signals
Check TLS renewal, disk space, service health, logs and credentials. A quiet long-running server still needs routine attention.
Backups and recovery
A snapshot is a rollback point, not a disaster plan.
The cockpit and make snapshot command create local database and file snapshots for quick recovery. Keep important snapshots and the credentials report off-server on a schedule, and periodically restore one on a disposable copy to verify that the recovery path works.
Do not use a disposable environment as the only copy of valuable content. When a finished site belongs in a separate production workflow, export or publish it using the migration process you choose.
Know the boundary
Long-running is not the same as managed hosting.
SpawnWP provides
Self-hosted isolated stacks, an authenticated cockpit, TLS setup, snapshots, restore, updates and lifecycle controls on infrastructure you operate.
You still provide
The VPS, DNS, firewall policy, off-server backups, WordPress application maintenance, monitoring and the production publishing decision.
Choose staging for release rehearsal
Use a production-connected staging workflow when data shape, integrations and the final deployment path must match production. Keep exploration in a sandbox.
Keep sensitive workloads separate
Public demos and unrelated production services should not share a SpawnWP host. A cockpit compromise has host-level consequences.
Make the distinction clear
Build freely. Operate deliberately.
Start with the sandbox model, then follow the security and operations guidance when a site needs to stay online.