Pay for the team in the workspace.
Share individual tools for free.
Team and Pro bill the people who belong to the workspace. App-only guests can access up to two specific tools for free, so occasional collaborators stay lightweight without turning invite links into a shadow workspace.
Free
For proving that your next little internal tool deserves a place to land.
- 2 workspace members
- 3 live tools
- Free app-only guests on 2 tools each
- Full CLI + MCP server
- Tool Storage for app data
- Auth, data guard & hosting included
- Community support
Team
For small teams turning agent-built apps into shared, governed workspace tools.
- Pay only for workspace members
- 25 live tools
- Free app-only guests on 2 tools each
- Full version history + one-click rollback
- Workspace env vault for shared credentials
- Custom domain
- Priority support
Pro
For companies standardizing how small internal tools reach real teams.
- Everything in Team
- 100 live tools
- In-browser AI editing — chat, live draft preview, one-click publish
- SSO / SAML
- Audit log of every deploy & query
- Staging environments per tool
- Managed database per app — bigger td.storage + a provisioned DATABASE_URL
- App database browser, API & CLI writes
- Custom share-page logo & URL
- App error logs with CLI & API access
- Scheduled jobs with run logs
- Public webhooks with delivery logs
- Usage analytics across the workspace
- Invoice billing & dedicated support
every plan includes workspace auth, hosting, platform env vars, and bounded app-only sharing
Bring an existing project into the Tooldrop contract.
Convert is the migration plan for apps that already have their own auth, database assumptions, cron jobs, or deployment habits. It gives builders and agents a narrow route-by-route path instead of a risky rewrite.
Auth
Replace app-owned login, sessions, and middleware with Tooldrop identity helpers.
Data
Move secrets to Tooldrop env vars and app-owned records to Tool Storage or a managed app database.
Cron jobs
Convert scheduled work to cron route handlers plus manifest schedules.
Webhooks
Expose public webhook URLs that forward into explicit app route handlers.
Deploy
Validate, preflight build, stage risky changes on Pro, then publish a clean version.
Keep the workspace paid. Keep app-only access free.
Most small internal tools have a core workspace team and a wider set of occasional users. Tooldrop charges the workspace members, then lets you invite specific viewers to a couple of tools without creating another billable seat.
Fair questions.
What counts as a workspace member?
Anyone assigned member, builder, or admin access counts as a paid workspace member on Team and Pro. Guests who only have access to specific tools do not count.
Can I still share tools for free?
Yes. App-only guests can access up to two specific tools in a workspace for free. Add them as workspace members when they need the launcher, team-visible tools, search, settings, or broader access.
Which coding agents work with it?
Any of them. Claude Code, Codex, and whatever ships next. Tooldrop is the workspace layer around the app, not the IDE. Every tool includes an agent contract and an MCP server so your agent builds against real conventions.
What is Tooldrop Convert?
It is the conversion plan for existing apps. The docs and agent guide walk through removing app-owned auth, moving secrets and app-owned state into Tooldrop, converting cron jobs, validating the contract, and staging risky changes.
Where does my data live?
Business data stays in your systems. Tools reach it through server-side clients configured by platform env vars. Small app-owned state such as saved filters, notes, and workflow flags lives in Tool Storage.
Do I need GitHub?
No. The CLI deploys straight from your machine, and Tooldrop stores the full source of every version — so you get history, rollback, and cloning without repos, branches, or merge anything.
Why do paid plans still have tool limits?
Tools create real hosting, storage, deployment, audit, and support surface. Team includes 25 live tools and Pro includes 100, so costs stay predictable on both sides.
What if we need more than 100 tools?
Talk to us. The self-serve Pro limit keeps the default plans simple, and larger workspaces can move to a custom allowance before the limit becomes operational friction.
What happens if we cancel?
Your tools stay live within Free limits and your data was never ours to hold. The source history is yours, and the credentials stay in your environment.
Start with the next loose tool.
Two workspace members and three tools cost nothing. That is enough to prove the pattern before you make it the default path.