Skip to main content

Introduction

Laravel Cloud offers a free trial with no credit card required. When you sign up, you receive $5 in one-time credits to spend on real infrastructure. Deploy an application, spin up a database, add a cache, and see how Laravel Cloud works before committing to a paid plan.

Getting started

Sign up at cloud.laravel.com with your name and email. After you verify your email, select the Free Trial.
You’re in! $5 in credits. No plan selection. No payment details. Credits are consumed as you provision and run resources. How far they go depends on what you deploy and for how long.

Available resources

During the free trial, you can use credits to provision the following resources:
ResourceLimit
Applications1
Environments1
Cluster1 app cluster, up to 512MB.
Regions (compute & WebSockets)Ohio (US East), Frankfurt (EU), Singapore (APAC)
Database1 Postgres (1/4 CU) and 1 Laravel MySQL (512MiB, 5GB storage)
Cache1 Laravel Valkey instance, 250MB
WebSockets1 cluster, 100 concurrent connections
Your app is served on a free .free.laravel.cloud vanity domain. Custom domains are available on paid plans.

Upgrading to a paid plan

You can upgrade at any time — including mid-trial. Head to “Organization -> Settings -> Billing” and “Change plan”. What happens when you upgrade:
  • You unlock the full set of features (compute, regions, databases, custom domains, and more).
  • Your application and configuration remain up and running.
  • Your vanity domain changes from .free.laravel.cloud to .laravel.cloud.
View plans and pricing

If credits run out

Once your free $5 credits are exhausted:
  1. Compute turns off immediately. Your app goes down. You can still log in and view your configuration, but you can’t create or modify resources until you upgrade.
  2. A 7-day grace period begins. Databases, caches, and other resources stay in place. Upgrade within this window and your app comes back as it was.
  3. After 7 days, everything is permanently deleted. This cannot be undone.
We’ll email you when credits are running low, when they run out, and when compute goes down.