aidrop.itDocs

Taking your work with you

How to export everything from aidrop.it: clone your code with your Team's Git credential, have your agent copy the database, and why images are not included.

Updated

Let your agent build this

Copy one prompt and paste it into Claude Code, Codex or Cursor. Your agent builds what this page describes and puts it online on aidrop.it.

See the prompt
Make me a complete copy of my work on aidrop.it. Do not delete or change anything.

List my Projects, Services and repositories. For each aidrop.it repository, give me the clone command and the credential to clone it with. For each PostgreSQL database, take a copy: for a small one, read the table definitions and then every table in pages with shared_database_query and save them as files; for a larger one, explain how to deploy a small Service that runs pg_dump and sends the file to storage I own, and ask me where that is.

This task comes from the aidrop.it guide "Taking your work with you": https://docs.aidrop.it/taking-your-work-with-you. Read that page if you need more detail; it says what to ask me for, what it costs and what will not work.
Use the aidrop.it MCP tools (server: https://aidrop.it/mcp). If you do not have them, stop and tell me to connect them first, as described at https://docs.aidrop.it/quickstart#1-connect-your-agent.

Nothing here needs aidrop.it’s permission or a support request. You can take your code with Git and your database through your agent, at any time. It is written down because a way out that only exists if you ask is not much of a way out.

Your code

Your repository lives in your Team’s own Git service at git.aidrop.cloud, and you hold a credential for it. Ask your agent: repository_get answers the clone URL and the push credential for any repository on that service, and repository_create answered the same when it made one. Then clone as you would any repository:

git clone https://git.aidrop.cloud/<team>/<repository>.git

The credential reaches every repository in your Team’s service, so one clone loop takes all of them. If you connected a GitHub repository instead, it was always yours and aidrop.it only ever read it.

This is the usual case for an app that started in a builder. If you moved an app from Base44 or Replit or host a Lovable app here, its code sits on your own GitHub, so there is nothing to export.

Your database

aidrop.it takes daily snapshots. For a move to another provider or an independent copy in storage you control, ask your agent to export the database.

There are two ways, depending on size:

  • Read it over MCP. shared_database_query runs any SQL statement against the database server, or against one database inside it, and answers CSV. One statement is stopped after 30 seconds and its answer cut at 64 KB, so the agent takes a copy table by table, in pages, with the table definitions from information_schema. This suits a small database. The MCP tool reference lists the call and its limits.
  • Run pg_dump from inside the Project. pg_dump is PostgreSQL’s own export tool. The database sits on a private network with no public port, so nothing outside the Project reaches it. Every Service attached to it, though, is handed a connection string that works from there. Have your agent deploy a small Service that runs pg_dump with that connection string and sends the file over HTTPS, a container’s only way out, to storage you own, such as an S3 bucket.

Run that second Service on a schedule and it is your backup policy. A cron job is the plain-words name for a task that runs on a timer.

Either way this export is yours to keep, independently of aidrop.it’s daily snapshots. Choose its retention period in your own storage.

Two things worth knowing before you need them:

  • The cache has no copy to take, because by design it holds nothing that survives a restart. The queue keeps a volume, but what it holds is work in progress rather than a record, so there is nothing to hand over either. Databases, caches and queues explains what each one keeps.
  • Deleting a database, cache or queue (shared_resource_delete) asks for confirmation and cannot be undone. Take the copy first.

Your images, and why they are not on this list

aidrop.it builds your source into a container image and keeps it in a registry service of your own. You cannot pull it, and that is deliberate rather than an omission.

An image is derived from your code: it is what a build produces, not something aidrop.it holds on your behalf. With the repository and the database you have both inputs. Any builder, such as docker build with the Dockerfile your repository already carries, produces the same app again. Issuing you registry credentials would add an account, a way to revoke it and a rate limit to maintain, in exchange for a file you can rebuild yourself.

If your repository has no Dockerfile because aidrop.it inferred the build, service_get reports the runtime settings it built under: the port, the health path and the build path. That is the whole of what the build knew.

What aidrop.it keeps after you leave

Deleting a Service removes its container and its address. It also detaches the Service from every database, cache and queue without deleting them, because another Service may still be using one. The repository stays, and can still be cloned.