You should be able to leave without asking us. This page says what keeps running without Pushify, what you can take with you today, and what we promise if we shut the hosted service down. Where something is missing, it says so.

1. Notice before a shutdown

If we shut down the hosted service at pushify.dev, we will tell every account owner by email and on this site at least 90 days before. For those 90 days the dashboard, the API and every export on this page keep working. Pushify is MIT licensed and its code stays public on GitHub, so you can keep running it yourself after that.

2. What keeps running without Pushify

On servers you connected, apps and databases are plain Docker containers started with --restart unless-stopped, behind nginx on the same server, with certbot renewing certificates there. Nothing on the server calls back to Pushify to stay up.

What stops with the control plane:

deploys, scheduled jobs, database backups, health checks and autoscaling;
apps that are asleep: the wake-up request goes through Pushify, so turn sleep off before you leave.

On Pushify’s infrastructure, things go away with the service: managed servers (they live in Pushify’s Hetzner account), sites on Pushify’s shared hosting, and *.pushify.dev addresses.

3. Taking your things

Code stays in your Git repository; Pushify only reads it.
Environment variables: pushify env pull writes a .env file. Values marked secret come out masked (ab****yz), so keep your own copy of secrets, or read them on your server with docker inspect.
Databases: download any backup from the database page. They are standard formats: pg_dump and mysqldump (gzip), a mongodump archive, Redis dump.rdb. Restore them with the usual tools.
Logs: runtime logs download from a project’s Logs tab. Build logs can be read but not downloaded.
Managed servers: download the root SSH key from the server page and copy off what you need. They cannot be moved into your own Hetzner account. They are deleted when you delete them, and powered off when your plan ends or your balance runs out.
Servers you connected: deleting one removes Pushify’s SSH key; the security page has a script that removes the rest.

4. Moving to self-hosted Pushify

The same software runs on your own machine with one command:

curl -fsSL https://raw.githubusercontent.com/pushifydev/pushify_backend/master/selfhost/install.sh | bash

Then connect your servers again over SSH, recreate your projects from the same repositories (a pushify.yaml in the repo carries its settings), paste your .env, and restore your database backups. There is no importer yet. Managed servers and automatic subdomains need accounts of your own (a Hetzner API token, a domain). The self-hosting guide covers the setup.

5. Not there yet

No button to delete your account or organization: email [email protected] to have it deleted.
No export of project settings or a generated pushify.yaml.
Uploaded static sites cannot be downloaded; keep the original files.
Built images stay on the server that built them; they are not pushed to a registry you own.
Secret environment variables are masked in exports.