Skip to content

Your Laravel app. The server work, done.

Push once. We deploy the app, then keep PHP, queues, the scheduler and the services underneath it running on servers you own.

PHP, workers and the scheduler.

  1. PHP upgrades

    PHP upgrades are handled on a schedule, with compatibility checks first. Your application and its packages stay yours.

  2. Queues and Horizon Beta

    Workers restart onto the fixed runtime, including long-running jobs.

  3. The scheduler and the record

    Scheduled tasks keep running. The activity log records server changes, automatic updates and reboots.

Major versions are server work too.

One repository. A working stack.

We read the repository first.

PHP runtime, handled

composer.json

from your composer constraint

PHP + extensions

PHP and extensions matched to your composer constraints.

Queues and workers

Queue configuration

driver, and how many workers

Queue workers

Supervised workers, gracefully restarted on every deploy.

Scheduled tasks

Application schedule

on, if you have one

schedule:run

Define scheduled tasks in code. strackt keeps the scheduler running.

Database & cache, auto-detected

Database and cache config

from your database config

Database + cache

Provision the database and cache your application uses.

Review the detected proposal before deploying. Node is used only when your repository needs to build assets.

The deploy plan builds dependencies and assets, runs migrations and switches the release. Edit the plan when your app needs a custom step. Returning to a previous application release does not undo database changes; database recovery uses an available service snapshot. The release sequence · Recovery choices.

Pull-request previews and deploy feedback are GitHub-only today. The complete capability overview · Ongoing server responsibilities · The update policy.