Laravel hosting · Vallic Cloud
Laravel hosting · Vallic Cloud
Laravel hosting with the scheduler, queues and migrations handled.
Laravel on machines no other customer shares, deployed from Git: migrations once the release is live, the scheduler every five minutes, queue workers kept running, and Valkey for sessions and cache.
On Vallic Cloud
What runs your Laravel 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 php artisan schedule:run every five minutes, without a crontab of yours.
Caches
Rebuilds them with php artisan optimize:clear from the console, a button rather than a shell.
Kept between releases
public/storage, storage/app, storage/logs and storage/framework, so a deploy never loses what the site wrote.
Why here
The parts of Laravel that run without a request.
Migrations after the release is live
php artisan migrate --force runs on the machine as a deploy step, then the caches. A release that never answers /up rolls back.
The scheduler, without a crontab
schedule:run every five minutes by default, or every minute if vallic.yaml says so.
Workers, not cron
queue:work runs as a worker the platform keeps alive, and restarts on every deploy.
Variables under Laravel’s own names
DB_HOST, DB_DATABASE, REDIS_HOST and the rest arrive as Laravel reads them. There is no .env to commit.
Storage that survives deploys
public/storage, storage/app, storage/logs and storage/framework are kept outside the release.
Support from people who build applications
Our team builds and runs PHP applications for a living, and a ticket reaches them.
Moving a Laravel application here.
Add a vallic.yaml, set APP_KEY as a secret variable or derive it from the environment as the handbook shows, import the database with vallic db import, and deploy.
Rather we did it? Our team moves applications as part of what it does.
Questions
Do I commit a .env?
No. Commit .env.example as usual. Each environment gets its own values as variables, under the names Laravel reads.
Do queued jobs survive a restart?
Point the queue at Valkey and turn its persistence on in vallic.yaml, or use the database driver.
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.
