# October Cloud Documentation

# Welcome to October Cloud

The official hosting platform for [October CMS](https://octobercms.com). Let us worry about infrastructure, and you just focus on making your website amazing.

## Mission Statement

Operating servers or using shared hosting can be a logistical and security nightmare. We're here to help. Let us handle complexities like:

- Integrating workflows between developers, designers, and content teams
- Database provisioning and backups
- Custom domains and SSL certificates
- Push-to-deploy with zero downtime
- Object storage and content delivery networks
- Security updates

We'll provide everything you need for a world-class experience with October CMS.

## Dedicated Resources

Unlike shared hosting, our platform creates dedicated resources that are yours, and yours alone. Say goodbye to "noisy neighbor" problems for good.

- Web server
- Database
- Object storage
- Caches
- Queue workers

Everything belongs to you.

## Project Status

October Cloud is currently in a private beta. More information will become available as we work towards general availability.

If you'd like to participate in beta, please [join the waitlist](https://octobercms.cloud)!

Last updated: 2026-08-09

---

# October CMS

Our platform is built specifically for [October CMS](https://octobercms.com), and is deeply integrated with it to create the best possible experience. We'll handle both local and production environments.

You just focus on making your website amazing.

## Local Development

We recommend using the [official October Cloud runtimes](https://github.com/octobercms/runtimes). These Docker images are the shared foundation for production deployments, and a [dev container](https://containers.dev/) configuration is included in the October CMS codebase by default—no special setup is required to use them.

Open your project in a dev container for the same PHP, Node, Nginx, and tooling stack that October Cloud runs in production. In other words: **If it works on your machine, it will work on production.**

Just install a container engine like [Docker](https://www.docker.com/get-started), [OrbStack](https://orbstack.dev/download), or [Podman](https://podman.io/get-started), and you're good to go!

Day to day, treat your repo like any other Git project: branch, commit, and push. You can develop with VS Code, Cursor, Claude Code, or even GitHub Codespaces. Use any setup you're familiar with.

> [!NOTE] 💡 Tip
> Don't worry if you're new to dev containers. Almost every IDE supports them out of the box. It's usually just a matter of clicking "yes" when opening the project.

## Backend Editor

The backend editor is a first-class citizen of the October Cloud — not a side path. Content editors, designers, and developers can make changes live in the admin area without leaving the browser or setting up a local environment.

When a backend edit is saved, October Cloud reconciles that change into Git, and everyone stays on the same page.

## Reconciliation

Source control is one of the oldest problems in content management. October has an amazing backend editor. Our platform fully supports the editor, so your team can work however they prefer.

Developers can use Git, and content teams may use the backend. We'll make sure they don't step on each other's toes. We call this feature "reconciliation".

**You'll never lose a change again.**

At a high level, your Git repository remains the source of truth. Backend edits will automatically open a pull request, and commits will trigger a deployment.


```
┌────────────────────┐          ┌────────────────────┐
│ Local development  │          │   Backend editor   │
└─────────┬──────────┘          └─────────┬──────────┘
          └───────────┐       ┌───────────┘
                      ▼       ▼
                ┌──────────────────┐
                │  Reconciliation  │
                └────────┬─────────┘
                         ▼
                ┌──────────────────┐
                │  Push to deploy  │
                └──────────────────┘
```

## Licensing

October Cloud provides and manages the license for your project. All plugins and themes are supported, including private and paid versions.

You can manage your plugins and themes on [October CMS →](https://octobercms.com/account/project/dashboard)

Last updated: 2026-08-10

---

# Applications

Applications represent the heart of your October CMS website. It's the central hub for all of its related resources like domains and databases.

## Creating applications

Applications can be created by personal accounts, or belong to an organization. Once created, an application cannot be transfered ownership.

To create an application navigate to the desired owner's overview page and click the green "Create application" button.

From here, choose the repository containing your October CMS application, and click "Create application"

## Initial deployment

The initial deployment will create several resources. These are only built on the first deploy, so it may take a bit longer than secondary deploys.

- Database
- Storage bucket
- Platform domain
- SSL certificate
- Content delivery network
- Load balancer rules

Once your initial deployment is complete, you can preview it using your platform domain at `<your‑app>.octobercms.cloud`

## Deployment triggers

For new applications, push‑to‑deploy will be enabled by default. If you'd like to handle deployments manually, this feature can be disabled in "Settings".

When a [reconciliation](https://docs.octobercms.cloud/october#reconciliation) pull request is open, push‑to‑deploy is paused until that pull request is merged. Once merged, push‑to‑deploy resumes automatically.

## Environment variables

Environment variables can be edited in "Settings". There are two entries: custom variables and injected variables. Custom variables normally override injected ones, though some injected variables cannot be overridden:

| Variable                | Reason                                        |
| ----------------------- | --------------------------------------------- |
| `CMS_DB_TEMPLATES`      | Required for template editing                 |
| `CMS_DB_ASSETS`         | Required for theme asset editing              |
| `FILESYSTEM_DISK`       | Platform-managed                              |
| `AWS_ACCESS_KEY_ID`     | Platform-managed                              |
| `AWS_SECRET_ACCESS_KEY` | Platform-managed                              |
| `AWS_DEFAULT_REGION`    | Platform-managed                              |
| `AWS_BUCKET`            | Platform-managed                              |
| `AWS_URL`               | Platform-managed                              |
| `AWS_ENDPOINT`          | Platform-managed                              |
| `ASSET_URL`             | Platform-managed                              |
| `THEMES_ASSET_URL`      | Platform-managed                              |
| `LOG_CHANNEL`           | Platform-managed                              |
| `LOG_LEVEL`             | Platform-managed                              |
| `OCTOBER_CLOUD_APP`     | Required for communication with October Cloud |
| `OCTOBER_CLOUD_SECRET`  | Required for communication with October Cloud |

## Build and deploy scripts

Application can define a build and deploy script in "Settings"

The **build script** runs during the image build, before the application is deployed. Use it for compile-time work, such as installing frontend dependencies or compiling assets.

The **deploy script** runs when a build is complete and before traffic is switched to the new image. Use it for release-time tasks, such as running database migrations or clearing application caches.

Last updated: 2026-08-12

---

# Databases

Every application provisions a Serverless Postgres 18 database powered by [Neon](https://neon.tech).

## Manual Connection

In "Settings", you'll find a deep-link sign-on button for your database. Clicking it opens a connection deep link that compatible clients—such as [TablePlus](https://tableplus.com)—can use to connect with your credentials already filled in, so you don't have to copy host, user, and password by hand.

## Monitoring

Settings also includes monitoring tools for disk space, CPU usage, and memory usage.

## Backups

Automated backups are included by default, with daily snapshots retained for 7 days.

Last updated: 2026-08-09

---

# Storage

Every October Cloud application is provisioned with dedicated object storage for media, uploads, and other files.

## S3 bucket

Each application receives its own S3 bucket during the [initial deployment](/applications#initial-deployment). The bucket is managed by the platform and connected to your application automatically—no manual configuration is required.

October CMS uses this bucket for theme assets, media library files, and other content stored through Laravel's filesystem.

## Content delivery network

Storage is served via a CDN powered by [CloudFront](https://aws.amazon.com/cloudfront/). When a visitor requests a file, it is served from an edge location close to them rather than from a single origin server.

This provides several benefits:

- **Speed** — Files load faster for users around the world because they are cached near the requester.
- **Security** — Traffic is served over HTTPS with platform-managed certificates.
- **Global reach** — A globally distributed network reduces latency for international audiences and handles traffic spikes without overloading your application.

## Monitoring

Storage usage can be monitored at `octobercms.cloud/<org>/<app>/storage`. This page shows metrics such as available capacity and current usage for your application's bucket.

## Capacity

Higher capacity options will be made available closer to general availability. October Cloud is currently in [private beta](/#project-status), and storage limits may change as pricing and plans are finalized.

Last updated: 2026-08-10

---

# Domains

Connect custom domains to your October Cloud applications.

## Domains page

The domains page can be opened from the **Domains** block on your application's homepage, or directly at `octobercms.cloud/<org>/<app>/domains`.

From here you can manage your platform domain and connect custom domains.

## Platform domain

Every application is provided a platform domain at `<app>.octobercms.cloud`. This domain is available after the [initial deployment](/applications#initial-deployment) and can be used to preview your site before connecting a custom domain.

The platform domain can be changed from the domains page if you need a different subdomain.

## Custom domains

Enter the domain on the domains page and add the generated `CNAME` records at your provider. Once verified, traffic is routed to your application with a platform-managed SSL certificate.

Use a `www` subdomain as your primary domain (for example, `www.acme.com`). Apex domains are not supported at this time because they must keep `SOA` and `NS` records.

Point the apex (`acme.com`) to `www` with a 301 redirect at your registrar.

> [!NOTE]
> A 301 redirect from the apex to `www` does not hurt SEO. Search engines treat this as normal domain canonicalization and pass ranking signals to the `www` version.

Last updated: 2026-08-26

---

# Deployments

Deploy new releases and manage application deployments on October Cloud.

## Push-to-deploy

Unless disabled, deployments are triggered automatically when you push to the main branch of the connected repository. Push-to-deploy is enabled by default for new applications and can be turned off in **Settings** if you prefer to deploy manually.

Push-to-deploy is temporarily disabled while a [reconciliation](/october#reconciliation) pull request is open. You can review and merge the branch from **Settings**; once merged, push-to-deploy resumes automatically.

## Rollbacks

Rolling back to a previous deployment triggers a new deployment using the code from that earlier release. Your application is redeployed with the selected version rather than reverting in place.

You may optionally roll back the database along with the code. This uses [Neon's](https://neon.com/blog/pitr-deep-dive) point-in-time recovery (PITR) to restore your data to the state it was in at the time of the selected deployment. Additional controls for data rollbacks and disaster recovery will be added in a future release.

## Build and deploy scripts

Applications can define [build and deploy scripts](/applications#build-and-deploy-scripts) in **Settings**. The build script runs during the image build; the deploy script runs before traffic is switched to the new release in the same [command context](/commands) as the command runner.

Last updated: 2026-08-10

---

# Organizations

Organizations let teams collaborate on October Cloud applications under a shared account. Use an organization when multiple people need access to the same applications, such as developers, designers, or agency clients.

## Owners

Every organization has exactly one owner. The owner is the account that created the organization and is responsible for billing and membership.

The owner has full access to all organization applications and can perform actions that are restricted to them alone. See [Permissions](#permissions) below.

## Members

Organizations can have any number of members. Members are invited by the owner and gain access to all applications within the organization.

Once added, a member can work with organization applications the same way the owner can for day-to-day operations—there is no per-application access control within an organization.

## Permissions

Members have full privileges within an organization's applications. This includes:

- Triggering deployments
- Managing domains
- Editing environment variables
- Viewing logs
- Running commands
- Configuring databases, storage, and other application resources

The following actions are restricted to the organization owner:

- Inviting new members
- Deleting an application

All other application management tasks can be performed by any member.

## Pricing

Organization pricing has not been determined yet. October Cloud is currently in [private beta](/#project-status), and pricing details will be announced closer to general availability.

Last updated: 2026-08-10

---

# Commands

Run Artisan commands on your October Cloud applications.

## Command runner

The command runner is available at `octobercms.cloud/<org>/<app>/commands` and can also be opened from the top bar navigation under **Commands**.

Use it to run one-off Artisan commands against your application, such as clearing caches or running database migrations outside of a deployment.

## Restrictions

Long-running Artisan commands are not permitted. This includes commands that would block indefinitely or require an interactive session, such as:

- `horizon`
- `horizon:listen`
- `queue:listen`
- `queue:work`
- `reverb:start`
- `schedule:work`
- `serve`
- `tinker`

For background processing, use [queue workers](/queue-workers) instead. For recurring tasks, use [scheduled tasks](/scheduled-tasks) instead.

## Deploy scripts

Each deployment runs its [deploy script](/applications#build-and-deploy-scripts) in this same command context. Anything you can run manually in the command runner can also be used in your deploy script.

Last updated: 2026-08-10

---

# Logs

View and inspect application logs.

Last updated: 2026-08-09

---

# Queue Workers

Configure queue workers for background job processing.

Last updated: 2026-08-09

---

# Scheduled Tasks

Set up scheduled tasks and cron jobs for your applications.

Last updated: 2026-08-09

---

# Support

Get help with October Cloud.

Last updated: 2026-08-09

---

# Changelog

Release notes and platform updates.

Last updated: 2026-08-09

---

# Security & Abuse

Security practices and how to report abuse.

Last updated: 2026-08-09

---

# Terms of Service

Terms of service for October Cloud.

Last updated: 2026-08-09

---

# Privacy Policy

October Cloud ("October Cloud," "we," "our," or "us") provides a cloud hosting platform for October CMS applications.

This Privacy Policy explains how we collect, use, disclose, and protect personal information when you visit our websites, create or use an October Cloud account, use our hosting and related services, or otherwise interact with us (collectively, the "Services").

## Scope

This Privacy Policy applies to personal information that October Cloud collects and processes for its own purposes, including information about our customers, account holders, organization members, website visitors, and people who communicate with us.

October Cloud customers may use the Services to host websites and applications that collect or process personal information about their own users ("Customer Data"). When we process Customer Data on behalf of a customer, the customer determines the purposes and means of that processing and October Cloud acts as a service provider or data processor on the customer's behalf.

Customers are responsible for providing appropriate privacy notices to their users and for ensuring that their use of the Services complies with applicable privacy and data protection laws.

If you have a question or request concerning personal information collected by a website or application hosted on October Cloud, you should generally contact the operator of that website or application directly.

## Information We Collect

The information we collect depends on how you interact with the Services.

### Information You Provide

We may collect information you provide directly to us, including:

* **Account information**, such as your name, email address, username, and authentication information.
* **Organization information**, such as organization names, organization membership, roles, and permissions.
* **Billing information**, such as billing addresses, subscription information, transaction history, and payment status. Payment card information may be collected and processed by our payment providers rather than directly by October Cloud.
* **Support and communications**, including messages, bug reports, support requests, feedback, and any information or attachments you choose to provide when communicating with us.
* **Application and configuration information**, including information you provide when creating, configuring, deploying, or managing applications through the Services.

### Information From Third-Party Services

When you connect a third-party service to October Cloud, we may receive information necessary to provide that integration.

For example, if you connect a source code hosting provider, we may receive information such as your account identity, repositories you authorize October Cloud to access, repository metadata, branches, commits, and other information necessary to deploy and manage your applications.

We may also receive transaction and payment information from our payment providers, such as payment status, transaction identifiers, billing information, and fraud or risk information.

### Information We Collect Automatically

When you use the Services, we may automatically collect information such as:

* Internet Protocol (IP) addresses;
* browser and device information;
* dates and times of requests;
* pages and features accessed;
* authentication and security events;
* application and deployment events;
* system configuration and infrastructure metadata;
* performance and diagnostic information;
* resource usage; and
* logs generated in connection with operating, securing, troubleshooting, and maintaining the Services.

### Analytics and Cookies

We use cookies and similar technologies to operate the Services, maintain sessions, remember preferences, provide security features, and understand how the Services are used.

We use Google Analytics on our public websites and within authenticated portions of the Services. Google Analytics may collect information about how you interact with the Services, including pages viewed, features used, approximate location, device and browser information, referring pages, and other usage information.

We use this information to understand how people use October Cloud, evaluate and improve the Services, diagnose usability issues, and make product and business decisions. Google may process information collected through Google Analytics in accordance with its own privacy practices.

## Customer Applications and Customer Data

October Cloud provides infrastructure used by customers to host their own websites and applications. Those applications may process information about their visitors and users.

In providing the Services, October Cloud and its infrastructure providers may process information associated with traffic to customer applications, including IP addresses, HTTP request information, timestamps, diagnostic information, application logs, and other information necessary to route traffic, operate infrastructure, maintain security, diagnose problems, and provide the Services.

Customers control the content and personal information processed by their applications and are responsible for determining what information their applications collect and how that information is used.

October Cloud does not control the privacy practices of applications hosted by its customers.

## How We Use Personal Information

We may use personal information to:

* provide, operate, maintain, and improve the Services;
* create and administer accounts and organizations;
* provision, deploy, host, and manage customer applications;
* authenticate users and manage permissions;
* process subscriptions, payments, and billing;
* provide customer support;
* communicate about deployments, billing, security, service changes, and other administrative matters;
* monitor the reliability, performance, and usage of the Services;
* detect, investigate, and prevent fraud, abuse, security incidents, and unauthorized activity;
* troubleshoot and resolve technical problems;
* enforce our agreements and policies;
* comply with applicable laws and legal obligations; and
* protect the rights, property, and safety of October Cloud, our customers, our users, and others.

We may also create aggregated or de-identified information that does not reasonably identify an individual and use that information to analyze and improve the Services.

## How We Share Personal Information

We may disclose personal information in the following circumstances.

### Service Providers

We use third-party service providers to operate October Cloud. These providers may process information on our behalf for purposes such as:

* cloud infrastructure and hosting;
* databases and data storage;
* content delivery and networking;
* source code integrations;
* payment processing and billing;
* email delivery;
* analytics;
* monitoring, logging, and error reporting;
* security and fraud prevention; and
* customer support and business operations.

We provide these service providers with information only as reasonably necessary for them to perform services on our behalf.

### Organization Members

If you use October Cloud as part of an organization, certain information about your account and activity may be available to the organization's owners, administrators, and other authorized members.

### Professional Advisors

We may disclose information to professional advisors such as attorneys, accountants, auditors, insurers, and financial institutions when reasonably necessary for the services they provide to us.

### Legal and Safety Reasons

We may disclose information when we reasonably believe disclosure is necessary to:

* comply with applicable law, regulation, legal process, or lawful government request;
* enforce our agreements or policies;
* investigate fraud, abuse, or security incidents;
* protect the security or integrity of the Services; or
* protect the rights, property, or safety of October Cloud, our customers, our users, or others.

### With Your Direction or Consent

We may disclose information to other parties when you direct us to do so or otherwise provide your consent.

## Third-Party Services

The Services may integrate with or contain links to services operated by third parties.

Your use of those services is governed by the applicable third party's terms and privacy practices. October Cloud is not responsible for the privacy practices of services that we do not operate or control.

## Data Retention

We retain personal information for as long as reasonably necessary to provide the Services, maintain legitimate business records, comply with legal obligations, resolve disputes, enforce agreements, and protect the security and integrity of the Services.

Retention periods may vary depending on the type of information and why we process it.

When information is no longer reasonably necessary, we may delete or anonymize it. Information may remain in backups for a limited period after deletion from active systems.

## Data Security

We use reasonable administrative, technical, and organizational safeguards designed to protect personal information against unauthorized access, disclosure, alteration, loss, or destruction.

No system for transmitting or storing information can be guaranteed to be completely secure, and we cannot guarantee the absolute security of information processed through the Services.

Customers are also responsible for appropriately configuring and securing their accounts, credentials, applications, and application data.

## International Data Processing

October Cloud is based in the United States.

We and our service providers may process and store information in the United States and other countries where we or our service providers operate. These countries may have privacy and data protection laws that differ from those in your country of residence.

Where required by applicable law, we will use appropriate safeguards for international transfers of personal information.

## Your Privacy Rights

Depending on where you live, applicable law may provide you with rights regarding your personal information, which may include the right to:

* access personal information we hold about you;
* correct inaccurate personal information;
* request deletion of personal information;
* obtain a portable copy of certain personal information;
* object to or restrict certain processing; and
* withdraw consent where processing is based on your consent.

These rights may be subject to limitations and exceptions under applicable law.

We may need to verify your identity before fulfilling a request.

If your request concerns personal information processed by an application hosted by an October Cloud customer, you should contact that customer directly. Where appropriate, we will assist our customers in responding to requests concerning Customer Data.

## Children

The Services are not directed to children, and October Cloud does not knowingly collect personal information directly from children in connection with the creation or administration of October Cloud accounts.

Customers are responsible for ensuring that applications they operate using the Services comply with applicable laws concerning the collection and processing of children's personal information.

## Changes to This Privacy Policy

This Privacy Policy is subject to change. We may update it from time to time to reflect changes to our Services, practices, or legal obligations.

When we make changes, we will update the "Last updated" date at the bottom of this policy. If changes are material, we may provide additional notice where appropriate or required by law.

## Contact Us

If you have questions about this Privacy Policy, our privacy practices, or would like to exercise a privacy right, contact us at [privacy@octobercms.cloud](mailto:privacy@octobercms.cloud).

Last updated: 2026-08-12