# Migrate Render web service: Laravel

## Summary

Move Laravel compute from Render web service to Ample, one component at a time. Destination verified on Ample: the app built, started and answered on its public HTTPS URL with encrypted configuration delivered. Source procedure: Copy environment variables and secret files from the Render dashboard into an env file kept out of the repository. Not migrated automatically: Render cron jobs, disks and private-service networking are not migrated; persistent data belongs in a managed database, a bucket or an Ample volume. Cutover: Add the custom domain with `ample domain add`, update DNS from the Render target, keep the Render service until verified, then suspend it. Rollback: keep the source untouched until you confirm; nothing at the source is changed or deleted by this guide.

## Infrastructure requirements

- [Compute](/discover/primitive/compute): verified (Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.)
- [Postgres](/discover/primitive/postgres): verified (Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.)

## Prerequisites

- Authorized access to the Render web service source and its export tooling
- An inventory of every component in scope and out of scope
- A validated backup or copy before any cutover
- An Ample account token with servers:write, databases:read

## Exact tested configuration

- template: `php-8.5`
- runtime: `php`
- size: `s-1vcpu-1gb`
- install: `composer install --no-dev --prefer-dist --no-interaction --no-progress --optimize-autoloader`
- start: `frankenphp php-server --listen :$PORT --root public`

## Steps

1. **Inventory the source.** List what Render web service provides beyond the component you are moving. Out of scope here: Render cron jobs, disks and private-service networking are not migrated; persistent data belongs in a managed database, a bucket or an Ample volume.
2. **Source step 1.** Copy environment variables and secret files from the Render dashboard into an env file kept out of the repository
3. **Source step 2.** Translate the Render build and start commands (or `render.yaml`) into the repository's manifest or `--build-command`/`--start`
4. **Source step 3.** Note Render-only features in use: background workers, cron jobs, disks, private services
5. **Deploy on Ample in parallel.** composer install --no-dev from composer.lock, then FrankenPHP serving public/ (php-server with the index.php fallback) reading PORT on the php-8.5 template. Pass the exported variables with --env;

```
   ample deploy . --name <app-name> --public --env-file .env.production
   ```
6. **Validate before cutover.** Run the app's own checks and, for data, compare counts and checksums; the example checks are the pattern self-tests (/p/configuration-secrets, /p/relational-records).
7. **Cut over.** Add the custom domain with `ample domain add`, update DNS from the Render target, keep the Render service until verified, then suspend it.
8. **Rollback.** Point DNS or configuration back to the source. The source was never modified; deletion is a separate, user-executed step after validation.

## Tested examples

- **Laravel pattern fixture (destination)** (tests/deploy-canaries/laravel-patterns): Verified destination basis: Laravel compute.

## Success checks

- destination app responds on its public URL (`/` on the live URL, expect ample canary laravel patterns)
- configuration-secrets check from the destination example (`/p/configuration-secrets` on the live URL, expect see the pattern fixture checks)
- relational-records check from the destination example (`/p/relational-records` on the live URL, expect see the pattern fixture checks)
- data or object counts and checksums match the source

## Limitations

- Documentation only: nothing is executed automatically and no execution binding is offered.
- The source-side procedure is documented from Render web service's standard tooling and was not executed in this catalog's evidence; the destination side was verified with the pattern fixture.
- No full source-product parity is claimed: Render cron jobs, disks and private-service networking are not migrated; persistent data belongs in a managed database, a bucket or an Ample volume.
- Verified on the php-8.5 template at s-1vcpu-1gb; region, compliance and request-duration limits are unknown.
- Managed PostgreSQL 16 only; extensions, connection limits and backup or restore procedures on the managed side are not verified beyond the pattern checks.

## Cost estimate

Estimated 10.00 USD per month (size prices from pricing.toml at build revision a1b8c38919e59cd035ebabaced73cf84ece24371).
- app server x1 `s-1vcpu-1gb`: 5.00 USD
- managed PostgreSQL database x1 `s-1vcpu-1gb`: 5.00 USD

Destination always-on monthly price of the tested sizes; apps auto-pause when idle. Source costs are unknown to Ample.

## Verification evidence

- canary_run on 2026-09-20T20:36:21Z at revision `118ad1c6d7d23d4c2ce069254bab9ec9d37cd57b-dirty (CLI 118ad1c)`: Destination side verified: the Laravel pattern fixture deployed on Ample (composer install --no-dev from composer.lock, then FrankenPHP serving public/ (php-server with the index.php fallback) reading PORT on the php-8.5 template) and its checks passed (the app built, started and answered on its public HTTPS URL with encrypted configuration delivered). The source-side export from Render web service is documented from the vendor's standard tooling and was not executed by this catalog's evidence. (expires 2027-03-19T20:36:21Z)

Last verified: 2026-09-20T20:36:21Z

## Execution binding

No execution binding. This recipe is documentation only; nothing is executed automatically.