Skip to content

Deploy a Laravel app and its PostgreSQL database with your AI, over MCP (2026)

Your AI already knows how to write Laravel. Connected to while over MCP, it also deploys your app, in France, with its PostgreSQL database backed up every day and a Laravel Dockerfile ready to go.

By Aloïs Oddon, co-founder of Nextmap. Facts checked on November 19, 2026.

View as Markdown

Deploy a Laravel app and its PostgreSQL database with your AI, over MCP: host a Laravel app and its PostgreSQL database in France, put in production by Claude Code, Cursor or Codex over HTTPS, with the database backed up every day

The short version. Over MCP, your AI deploys your Laravel app and its PostgreSQL database with while, a French PaaS, with a Dockerfile ready to build. What matters, like deleting a database, waits for a person’s approval.

Prerequisites

  • A Laravel app, with its composer.json and its artisan file.
  • An AI that works in a terminal: Claude Code, Codex, Cursor or Gemini CLI.

Step 1: Give your AI this message

Open your AI in your app’s folder and paste this message into it:

The message to give your AI
Connect to while with my account (while.sh/agents), then put my app on while.

Without an account, your AI deploys your app as a trial, in one request. To keep it, open the link it gives you and create your account.

With your account, your AI adds while’s MCP server itself. If it asks you to, restart it. On the first call to while, a page opens in your browser. In Claude Code, if it doesn’t open, type /mcp, choose while, then Authenticate. On that page, choose your app, or “A new app”, then click Authorize.

Step 2: Open your app

Your AI gives you your app’s address, for example https://mon-appli.while.cloud, over HTTPS.

What your AI does

It writes while.yaml at the root of your app:

while.yaml
apiVersion: while/v1
project: mon-appli
services:
  - name: web
    port: 8080
    health:
      path: /up
databases:
  - name: main

while recognizes Laravel by its composer.json and its artisan file, and your AI gets a Dockerfile ready to build: the Composer dependencies, Apache serving the public folder, and a user without admin rights. Your AI adds it to your app. If your pages load their assets with Vite, the Dockerfile builds them too, and your pages load them over HTTPS.

At startup, the migrations run, then Apache serves your pages. Laravel reads the database address from DB_URL1, which the Dockerfile fills in from DATABASE_URL. The /up route in Laravel 11 and later tells while that your app is ready2. On an older version, your AI adds it. Your AI also generates the APP_KEY key and stores it in while’s secret vault.

What your AI does to put a Laravel app and its PostgreSQL database in production on while: the while.yaml file, the build and tests, the HTTPS address, the PostgreSQL database backed up every day and a person's approval, in France
Your AI writes while.yaml, while builds and serves the app over HTTPS, and the previous version stays ready.

Run your queues

You, to your AI: Add a worker for the email queue.

Your AI declares a worker, with the same image and the php artisan queue:work command. Your jobs wait in the PostgreSQL database, which is backed up every day.

Store uploaded files

You, to your AI: Store the files our customers upload.

Your AI adds S3-compatible storage to while.yaml and connects Laravel’s s3 disk to it. Your files survive every deployment.

Run an artisan command every night

You, to your AI: Run the export command every night at 3 am.

Your AI declares a scheduled job that runs your artisan command at the set time, with the same code and the same database. If it fails, your AI is notified.

Restrict your app to your colleagues

You, to your AI: Restrict the app to people in the company.

Your AI makes the service internal:

while.yaml
    access: internal

Then it asks for the Access role for your domain, @acme.com, on this app, and a person in your organization approves it.

Once your Google Workspace or Microsoft 365 is connected to while, on the Pro plan, your colleagues sign in with their usual account, and your code receives their name and email address, with no sign-in page to write.

Move to your own domain

You, to your AI: Put the app on app.acme.com.

Your AI declares the domain, you add the DNS records it gives you, and the HTTPS certificate follows.

See a new version before you deploy it

You, to your AI: Show me the new version before you deploy it.

Your AI opens a preview, at its own address, with its own data. You look at it, then your AI puts it into production.

Go back to the previous version

You, to your AI: Go back to the previous version.

In the 30 minutes after a production release, the previous version comes back in a second. After that, it takes a few seconds. Once the previous version is back, your AI reads what broke in while’s logs, fixes it and deploys again.

In the docs: PostgreSQL databases, Scheduled jobs, Internal access, Custom domain, Previews and Versions and rollback.

Next steps

Sources

  1. Laravel, database configuration (DB_URL), accessed November 2, 2026
  2. Laravel, the /up health route, accessed November 2, 2026

Questions

Do I need to write a Dockerfile?

No. while recognizes Laravel, and your AI gets a Dockerfile ready to build, with Apache and PHP. If your project already has its own, that one builds the image.

Are my migrations applied?

Yes, at every startup, with php artisan migrate --force.

What about queues?

Your AI adds a worker, with the same image and the php artisan queue:work command.

MySQL or PostgreSQL?

while’s database is PostgreSQL, and Laravel connects to it without any change to your code.

Where is my app hosted?

In France, by Nextmap, a French company.

Give your AI the message, and it takes care of the rest

Give this to your AI

Read while.sh/agents and help me get started with while.

Copy the message

In 3 minutes, with no sign-up, the tool has its own address. To keep it, create your account.

For a company project, write to the while team: hello@while.sh