WordPress hosting · Vallic Cloud
WordPress hosting, deployed from Git.
WordPress on machines no other customer shares, with wp-cli in every release, uploads kept between deploys and Valkey for the object cache. One console for environments, backups, your team and support.
On Vallic Cloud
What runs your WordPress site
You choose
Runtime
Database one of
Cache one of
You can add
Reverse proxy
Search
Time series
Background work
The default, unless vallic.yaml names another version.
Done for you
Scheduled
Runs wp cron event run --due-now every hour, without a crontab of yours.
Caches
Rebuilds them with wp cache flush from the console, a button rather than a shell.
Kept between releases
wp-content/uploads, so a deploy never loses what the site wrote.
Why here
What production runs is what was reviewed.
Deployed, not edited live
The release is read-only. Plugins and themes arrive from the repository or from Composer and are deployed, so production runs exactly what was reviewed.
WordPress cron on time
wp-cli runs WordPress’s schedule every hour without a visitor to set it off, or as often as vallic.yaml says.
Uploads outlive every release
wp-content/uploads is kept outside the release, so a deploy never loses a file.
A cache flush after every restore
After a backup is restored the platform runs wp cache flush, so the object cache never serves what the restore replaced.
Past one web server
Logins are signed cookies, and the object cache can live in Valkey with the Redis Object Cache plugin, so every server sees the same site.
Support from people who build sites
Our team builds and runs sites for a living, and a ticket reaches them.
Moving a WordPress site here.
Commit the site with its plugins and themes, add a vallic.yaml and the wp-config.php from the handbook’s WordPress page, import the database with vallic db import, and deploy.
Rather we did it? Our team moves sites as part of what it does.
Questions
Can I install plugins from the dashboard?
No, deliberately: the release is read-only. Add a plugin to the repository, or require it with Composer, and deploy. WordPress’s automatic updates are off for the same reason.
What changes in wp-config.php?
It reads the database, the salts and the site’s address from the environment instead of having them committed. The handbook has the whole file.
Do you charge per request or per visit?
No. Machines are billed by the month, and traffic past what a machine includes by the terabyte.
Where can it run?
In any of the platform’s datacentres. The configurator shows each one’s machines and prices before you sign up.