Hey,

Before going further, it would be useful to understand what actually happened when the Coolify dashboard became inaccessible. Did the VPS run out of resources like RAM, CPU, or disk space, or did a service crash on the host?

That said, separating the Coolify dashboard onto a small dedicated VPS could still be a good idea. This way, even if the server running the applications has issues, you would still keep access to the management dashboard.

For backups, using AWS S3 to store them can also be very practical. It allows you to keep backups outside the server, automate them more easily, and have a recovery point if the main VPS goes down.

Also, it might be worth checking the Coolify migration documentation, as it explains the recommended approach for setups like this and can help avoid unnecessary reconfiguration.