Laravel Cloud - Early Access Docs
Welcome to Laravel Cloud Early Access! We’re excited to partner with you to build the future of shipping with Laravel.
Docs Navigation
The docs are broken down into the following sections:
Home
Provides overview of Cloud, the Early Access Program & GA timeline.
Getting Started
Overview of key concepts of Cloud and how to access the platform.
Guides
In-depth documentation on specific parts of the platform.
Troubleshooting
Covers common sticking points such as domain verification and Git integration
FAQs
Common questions which will be updated based on your feedback.
Changelog
All notable updates to Cloud, published weekly.
Support
How to get technical support & provide feedback to the team
Onboarding into Cloud
You will receive an email with an invite code to your inbox with login details to Cloud. Please read the docs to get yourself set up. We recommend beginning with Getting Started.
Communicating with the Laravel Team
If you encounter any issues, filing a
Support ticket is the best way to ensure it gets addressed by the team.If you’d prefer to talk live, please use our office hours link to schedule time that works for you & your team.
Roadmap to General Availability
Milestone | Alpha (EA-1) | Beta (EA-2) | General Availability |
Timing | Nov-Dec ‘24 | Jan ‘25 | TBD |
Reliability Rating (see scale below) | Low | Medium | High |
Pricing | Free (fair use) | Free (fair use) | Standard Billing |
Reliability Readiness Scale for Laravel Cloud
Purpose: To communicate recommended customer workloads based on Cloud’s reliability stage. Use this rating scale to determine what types of applications are suitable for each release phase, taking into account your app’s level of criticality and your risk tolerance for service interruptions.
- Low (Evaluation)
-
Recommended Use: Development, staging, or trial environments only.
-
Description: Ideal for experimental or low-impact applications where potential downtime or service limitations are acceptable. Suitable for exploring platform features but not for business-critical apps.
-
Stage: Alpha – The platform is still in active development, with limited guarantees of stability.
There may be changes or migrations made during this phase that require applications, organizations, and/or users to be recreated in part or in whole. We will give as much prior notice as possible before deploying breaking changes.
- Medium (Non-Critical Production)
-
Recommended Use: Non-essential production workloads or applications with minimal impact in case of downtime (e.g., internal tools, analytics dashboards, supplemental queue workers, or backup services).
-
Description: Suitable for production apps that can handle temporary disruptions. The platform offers a higher level of stability, but users should avoid deploying highly critical applications.
-
Stage: Beta– The platform is more stable, but service interruptions are still possible as enhancements continue. No guarantees on platform uptime or support response times.
- High (Mission-Critical)
-
Recommended Use: Any application, including high-impact, mission-critical workloads requiring maximum uptime and minimal risk of interruption.
-
Description: Fully supported for all types of applications, with comprehensive reliability measures in place. Users can confidently deploy essential production apps and sensitive workloads.
-
Stage: General Availability (GA) – The platform is fully tested, and reliability is ensured for all use cases.
Feature Pipeline
Name | Description | ETA |
---|---|---|
Logs | A searchable database of your environments’ latest application and network logs to help with debugging and observability. | Shipped |
Metrics | Basic graphs to monitor CPU & RAM utilization, network traffic, and average response times | Shipped |
Cache | Redis API compatible KV storage that can be used as a cache, queue, and/or session driver. | Shipped |
PHP Extensions | Enhance list of PHP extensions supported by default | Shipped |
Object Storage | Create public or private S3 compatible buckets for cost-efficient file uploads & downloads. | Jan ‘25 |
User Roles | Assign users roles like “Developer” or “Finance Manager” to limit access within your Cloud organization | Jan ‘25 |
Billing & Usage Dashboard | See and manage your Cloud plan, resource usage, and past invoices | Jan ‘25 |
Support Other Regions | Roll out Cloud to other AWS regions so you can choose the region that’s closest to your users | Jan ‘25 |
MySQL Database | Managed MySQL databases and backups | TBD |
Was this page helpful?