Skip to content

Laravel Cloud

Laravel Cloud builds and runs an app from your code repository. It manages the server setup and lets you attach separate services for saved records and uploads.

Visit Laravel Cloud

What do you need to deploy a Laravel app?

Laravel Cloud’s Laravel quickstart calls for Laravel 9 or newer, a supported PHP version and a GitHub, GitLab or Bitbucket account with access to your repository.

A repository holds your code. Cloud builds it and runs the chosen version. Set the app’s required settings and choose where it will keep records. Laravel Cloud also documents other frameworks and runtimes. This walkthrough follows the Laravel setup.

How do you plan a preview with separate records?

On paper, draw a fictional workshop booking app and its preview. Booking a sample time should change only the preview’s records.

  1. List the preview connections
    Draw a separate test database and a test bucket if the app accepts files. Keep outgoing email and payments disabled. Mark who should be able to open the preview.
  2. Check isolation before the first run
    Trace the app’s database, file, account and outgoing settings to the test destinations before any deployment or automatic database changes. A preview can be configured to reuse the target database or bucket, so a different address alone does not separate the data.
  3. Check the saved result
    On paper, submit one made-up booking and reopen the preview. The test record should still appear and the live records should be untouched. Leave the exercise on paper if you cannot verify the connections.

What does Laravel Cloud charge for?

On November 12, 2026, the current pricing documentation lists Starter at US$5 per month with US$5 in monthly usage credits. Cloud measures app and worker compute by each second a running copy uses.

Eligible app compute can pause when idle. Add the database, backup storage, uploaded files and any additional traffic charges to your estimate. MySQL storage and backup charges continue while a database sleeps.

Starter includes one preview automation per organization. That is one rule that can create several previews from the same target environment. A running preview and its connected resources can add usage.

Where do records and uploads survive a new release?

Use a persistent database such as managed MySQL or Serverless Postgres for records, and a separate storage bucket for uploads. A local SQLite file is unsupported for production data because the app filesystem can reset.

Choose a recovery window before you rely on a managed backup. Restoring a MySQL backup or a Postgres point in time creates a separate database cluster. Postgres point-in-time recovery can be turned off by setting its window to zero. A database restore does not recover objects in a separate bucket.

What should you take when you move the app?

Keep the repository, the build and startup settings, a database export and a copy of the files. Set up the destination’s secrets separately.

A managed MySQL snapshot is an internal copy. To get a portable copy of a historical snapshot, Laravel documents restoring it to a separate cluster and exporting it with a database tool. Keep records and uploads in distinct recovery steps, and verify both in an isolated destination before changing traffic.