Server capabilities preserved
Route handlers and server-only environment values stay on the trusted side of the app.
Next.js repo → operational toolYour Next.js app is ready.
Now make it operational.
Deploy the App Router project from your repository with server environment variables, route handlers, logs, and version history intact—then put workspace identity in front of the whole experience.
✓App Router and route handlers✓Server secrets stay server-side✓Jobs and webhooks available✓Preflight builds and rollbacks
your project
# keep the code where it is
$ npx tooldrop init
✓ project contract validated
✓ workspace identity connected
✓ version bundle created
live → tooldrop.app/a/team-tool
Signed in. Permission checked. Ready for the team.deploy history
v3 · ready · 42s
The handoff
Three moves from useful code to useful software.
No rebuild in a proprietary editor. ToolDrop wraps the operating responsibilities around the project you already have.
- 01
Add the platform contract
Keep the Next.js repository and declare the app identity, resources, environment, and runtime features.
npx tooldrop init - 02
Prove the production build
Validate the gateway guard, server imports, routes, jobs, webhooks, and required environment before release.
tooldrop deploy --preflight-build - 03
Operate it with the team
Publish the live version, invite users, inspect logs, and roll forward without losing deployment history.
tooldrop deploy
What changes after deploy
The code stays yours. The operational mess does not.
Identity at the gateway
A signed workspace identity reaches the app without adding another standalone login system.
Operations in one place
Releases, logs, rollbacks, scheduled jobs, and webhooks live with the app.
free workspace · no cardThe next deploy can be the one your team actually opens.
Start on Free, publish a real app, and move to Team or Pro only when the workspace needs more scale and controls.