Ghostable + Laravel Cloud | Ghostable                            Ghostable ✕ Laravel Cloud

 Hydrate Laravel Cloud builds with Ghostable.
==============================================

 Have Laravel Cloud pull fresh env vars from Ghostable before you cache config, keeping deployments current without provider tokens or manual edits.

 [ Get started for free ](https://ghostable.dev/register) [ View the docs   ](https://docs.ghostable.dev/v2/digging-deeper/deployments#laravel-cloud)

 ![Laravel Cloud logo](https://ghostable.dev/images/logos/laravel-cloud.svg)

  Why teams connect Ghostable with Laravel Cloud

 Built for Cloud

### Runs in your build commands

Add `npx ghostable deploy cloud` ahead of config:cache so every deploy pulls envs straight from Ghostable.

 Single Source

### Ghostable stays canonical

Store variables in Ghostable and let Cloud receive the latest values—no stale .env files or copy/paste drift.

 Env Isolation

### Staging and production stay separate

Use Cloud environment secrets per stage so each deploy command writes only to the intended environment.

  Set up in minutes

 Turn on Laravel Cloud syncing and forget about manual updates.
----------------------------------------------------------------

1. 1 Add your deployment token

    In Laravel Cloud → Environments → Settings → General → Custom environment variables (reveal secrets), add GHOSTABLE\_CI\_TOKEN and GHOSTABLE\_DEPLOY\_SEED from Ghostable.
2. 2 Insert the deploy command

    Under Settings → Deployments → Build commands, run `npx ghostable deploy cloud` before config:cache.
3. 3 Deploy and cache config

    Trigger a deploy—Ghostable writes env vars into Cloud, then your config cache picks them up.

 [ Try it now ](https://ghostable.dev/register) [ View the docs ](https://docs.ghostable.dev/v2/digging-deeper/deployments#laravel-cloud)

  FAQs about Ghostable & Laravel Cloud

    How does Ghostable authenticate in Cloud?      With your deployment token and deploy seed stored as Cloud secrets—no Cloud API keys required.

    Do I still need to ship .env files?      No. The deploy command pulls environment values from Ghostable and writes them in Cloud before you cache config.

    How do I keep staging and production separate?      Use separate deployment tokens per Cloud environment and run the command in each environment’s build steps to keep values isolated.

 More integrations

### Explore other providers

 Browse the growing lineup—new integrations land here as soon as we ship them.

 [ ![Vanta logo](https://ghostable.dev/images/logos/vanta-icon.svg)

Vanta

View integration

   ](https://ghostable.dev/integrations/vanta) [ ![Laravel Forge logo](https://ghostable.dev/images/logos/forge-icon.svg)

Laravel Forge

View integration

   ](https://ghostable.dev/integrations/forge) [ ![Laravel Vapor logo](https://ghostable.dev/images/logos/vapor-icon.svg)

Laravel Vapor

View integration

   ](https://ghostable.dev/integrations/vapor)

 [All integrations](https://ghostable.dev/integrations)