Start from your repository
Use aidrop Git or connect GitHub. Your agent edits on your machine and pushes with git, so the source stays in the workflow you already use.
Deploy an existing app
and keep shipping it from your AI agent
Connect the repository you already use. Your agent records how the app builds and runs, works through deployment blockers and leaves a live service that the next session can inspect.
7-day trial · No credit card · aidrop Git or GitHub
ADAPTED FOR AI DEVELOPMENT
Give the agent the facts it needs to ship
Source code can omit the decisions that keep an app running. aidrop puts those decisions beside the service, where your coding agent can read and update them.
Make the runtime explicit
Record the build method, port, health check and required value names. The next build uses the same settings unless you change them.
Give failures to the agent
The build record shows the stage that stopped and keeps the log. Your agent can change the code, push and run the build again in the same session.
Leave a working service behind
The repository link, runtime settings, address and build history stay with the service. A later agent session can inspect them before making a change.
THE ADAPTATION WORK
Turn hidden setup into a repeatable deploy
The first build tests the real revision against the runtime. Each gap becomes a code or configuration change your agent can make with you.
Connect the current code
Choose an aidrop Git repository or a GitHub repository. aidrop follows the branch that the service tracks and builds an exact revision from it.
State how the app should run
Your agent records the port, health path, size, build method and the names of the values the app needs. It asks you when the code does not settle a decision.
Fix the first deployment
The build and runtime checks expose the real blockers. Your agent reads the result, updates the repository and builds again until the app serves traffic.
Keep the deployment path
Future changes use the same repository and runtime settings. Each successful build updates the service while its address and earlier build records remain available.
THE NEXT CODING SESSION
A new chat can start from the deployed app
Connect Claude Code, Codex or Cursor to the Team. The agent can read the service record, inspect the latest build and see the address before it changes the repository.
You can ask for the next feature and include the deployment in the same task. The agent pushes the change, starts the build and reads the result through MCP.
ASK YOUR CODING AGENT
“Add CSV export to the admin app, deploy the change and tell me when the public address has updated.”The agent can inspect the service, change the code, push, build and poll the result.
ASSISTED MIGRATION
Plan complex data and runtime changes first
An existing database, files written to local disk, several processes or raw network dependencies need design work before deployment.
Tell us what the app does, where it runs and where its data lives. We define the scope before any migration work starts. Hosting uses the published plans. Migration work has its own quote.
Tell us about the appWhat does adapting an app for AI development mean?
Your coding agent gets a repeatable path from the repository to a running service. The service records the build method, port, health check, required value names, current address and build history. A later session can inspect that state before it changes the code.
Does aidrop rewrite my app?
No. Your coding agent changes the source when you ask it to. aidrop builds the revision it receives, runs the app and records the result. The first deployment may expose code or configuration that needs work, and the agent can fix those blockers with you.
Can I keep the repository on GitHub?
Yes. Install the aidrop GitHub App and choose the repository it can read. Your repository stays on GitHub. You can also use your Team's aidrop Git when the code starts on your machine.
Can every app deploy without changes?
No. Apps that write durable files to local disk, open raw connections to external database ports or depend on several host processes need another design. The first build gives your agent a concrete failure and log instead of a guess.
When should I ask for migration help?
Talk to us before moving production data, replacing a complex deployment or changing several services at once. We define the scope before any work starts. Hosting uses the published plans. Migration work has its own quote.
Know the hosting boundaries
The app runs with a read-only root filesystem and temporary scratch space. External connections leave over HTTP or HTTPS, so a raw connection to an external database port needs another design.
The app is public after its first successful deployment. aidrop keeps no database backup copies. Plan application access and database exports before moving production data.
Read the runtime and data limits