DATABASE_URL that fromDatabase filled in becomes a binding rather than a copied string. This guide takes you from a running Render service to the same app on InstaCloud, with its data. Your coding agent does most of it.
InstaCloud offers:
- Postgres with real branching. A branch opens as a copy-on-write clone holding all of the parent’s data, at its own connection string, so a feature or an agent task can run migrations nowhere near production.
- Built for coding agents. A CLI and an MCP server your agent drives directly, with an approval gate on the actions that matter.
- Flexible deployments. A GitHub repo with no Dockerfile needed, your own Dockerfile, or an image from any registry.
- Managed services alongside. Postgres, Redis, MySQL, MongoDB, and object storage in one project.
- Real support. An active community on Discord.
Migration steps
We will migrate Render’s own Django example, a Python web service with a Postgres database. The interesting part of itsrender.yaml, abridged. The full file also carries plan, databaseName, user and a startCommand:
1. Point a coding agent at your Render app
Your agent reads the service straight from Render’s API, so it needs your repo name and a Render API key, not a checkout. Give it the skill first:insta CLI, the insta skill, and the MCP server for every coding agent on this machine. The skill is what knows how to read a render.yaml and turn it into services.
2. Create a project
3. Ask your agent to migrate
Get a Render API key first, under Account Settings → API Keys in the Render dashboard. Your agent needs it to read your environment variables, which the Render CLI has no command for.Prompt