page:migrate:render web service:django

Migrate Render web service: Django

Summary

Move Django 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.

Representative Queries

• Migrate Render web service: Django
• Where can I host Django built with Django?
• I need a component-scoped export/import or reconfiguration procedure for Django, with compatibility checks, verification and rollback.

Resource Requirements

• primitive:compute
• primitive:postgres

Infrastructure Requirements

Compute

• Status: verified
• Summary: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.

Postgres

• Status: verified
• Summary: Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.

Framework

Django

Workload

Django

Migration Source

Render web service

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

Workflow 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
   pip install into .ample/python from requirements.txt, then waitress serving project.wsgi from run.py reading PORT on the python-3.12 template. Pass the exported variables with --env; keep the source running.
   Command: ample deploy . --name --public --start "python3 run.py" --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.

Examples

• Django pattern fixture (destination)
  Verified destination basis: Django compute.
  Source Reference: tests/deploy-canaries/django-patterns

Success Checks

• Destination app responds on its public URL.
• Configuration-secrets check from the destination example.
• Relational-records check from the destination example.
• 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.
• Verified on the python-3.12 template at s-1vcpu-1gb; region, compliance and request-duration limits are unknown.

Cost Estimate

• Currency: USD

• Monthly Amount: 10.0

• Components:

  • app server, size: s-1vcpu-1gb, quantity: 1.0, monthly amount: 5.0
  • managed PostgreSQL database, size: s-1vcpu-1gb, quantity: 1.0, monthly amount: 5.0

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

Evidence Summary

• Kind: canary_run
• Summary: Destination side verified: the Django pattern fixture deployed on Ample (pip install into .ample/python from requirements.txt, then waitress serving project.wsgi from run.py reading PORT on the python-3.12 template) and its checks passed (the app built, started and answered on its public HTTPS URL with encrypted configuration delivered).
• Observed At: 2026-09-20T03:31:44Z
• Last Verified At: 2026-09-20T03:31:44Z

Formats

• HTML: Link
• Markdown: Link
• JSON: Link

Next Actions

• Browse the catalog index
• Search published recipes by intent, stack and constraints
• Prepare a side-effect-free deployment plan for an authorized project
• Read the existing agent authentication setup
• Browse Render web service
• Browse Django
• Browse Migrate compute