title: Production checklist description: What to set up before you move real users to your app, and what Ployz doesn't do for you yet.

Ployz is young and changing quickly. Before you move real users to your app, work through this list. Each item links to the page that does it.

Before you move real users

• Back up your data. Add a mirror to each volume you can't lose, so it has a backup on another of your servers that you can restore. A mirror isn't offsite, so also dump your databases on a schedule and keep the dumps off your servers. See Back up a database. Or keep your hosted database and point your app at it.
• Add a health check. Without one, a new replica gets traffic a few seconds after it starts, ready or not. See Deploy without downtime.
• Run two replicas on two servers. With one replica on one server, one failure takes your app down. Add a second server, then run more replicas. A service with a volume runs one replica, on the volume's server.
• Set CPU and memory limits. Otherwise one busy service can use all of its server's CPU and memory and starve the others. See Scaling.
• Wait for CI. A push deploys at once, even when your tests fail. See Wait for CI.
• Use your own domain. Generated addresses are for getting started. See Add a custom domain.
• Look after your servers. Ployz doesn't install OS updates or harden your servers. Log in with SSH keys, not passwords, and turn on automatic security updates (unattended-upgrades on Ubuntu). If you add a firewall, keep these ports open. A reboot stops the services on that server until it's back.
• Watch your app. Ployz Cloud checks every service with a public address and shows its uptime next to its metrics and logs. It emails your organization when a service goes down and when it's back up. Choose who gets those in Notifications.

What Ployz doesn't do yet

• No automatic failover. If a server dies, the services that ran only there stop, and a database on it is down until the server is back. See When a server goes down.
• No rollbacks. To go back, revert the commit and push, or change the setting back and deploy.
• No Docker Compose files. Add each container as its own service.
• No autoscaling. You choose the number of replicas.
• Three roles. An organization has owners, admins and members, with no finer permissions. See Invite people.

Rollbacks are planned.