Moving Payload Admin from Vercel to Coolify
A migration retrospective on moving Payload Admin to Coolify while keeping the public site and Blob on Vercel, with diagrams for releases and cutover.
I moved Payload Admin off Vercel because its CPU usage was consuming the allowance shared with the rest of the site. The public site, Blob storage, and the existing database stayed in place. Only the Admin runtime moved.
What moved
Why Coolify and Infisical
The horizontal axis shows how easy each option was to set up and use for routine releases. The vertical axis shows the pressure this workload put on my hosting budget. The positions are qualitative. I assumed the same VPS for all three self-hosted options and counted maintenance time under convenience.
Vercel was easy to operate, but Admin's CPU usage put pressure on the shared allowance. The three self-hosted options had comparable server costs. Coolify fit my existing Release workflow best because its Compose API and native Infisical integration replaced the deploy and secret-sync scripts I maintained.
Infisical covered the need to read application configuration by environment. Vault's dynamic credentials and leases suit systems that need those capabilities.
From Release to running container
The digest identifies the exact build. Coolify resolves secrets at deployment time, so rotating an application secret does not require rebuilding the image.
What a health check missed
In this migration, a successful sync left an empty runtime file, an incomplete connection string selected an empty database, and a working login page hid a bad redirect. I also had to recover or regenerate sensitive values that Vercel could not export.
Cut over in two steps
I kept an independent way to reach the dashboard during the gateway switch. After the public checks passed, I retired the old deploy path and disabled the old Vercel Admin compute endpoint. Blob stayed available to the site. Backup and restore checks for Coolify, Atlas, and Blob are the remaining follow-up.
Discussion
Sign in with GitHub to comment. All language versions share this discussion.
View discussions on GitHub