ooda for teams
Claude Code for your whole organization.
Give every designer and developer their own cloud environment with Claude — while you keep control over access, infrastructure, and what gets published.
One invite code, one dashboard, zero local setup.
The problem with personal deploys
Your team is building prototypes and internal tools with Claude Code. They're publishing to personal Netlify and Vercel accounts, sharing links in Slack, and nobody knows what's live where.
When someone leaves, their sites stay up. When a prototype contains sensitive data, there's no kill switch. When leadership asks "what has the team shipped?", you're searching chat history.
ooda for teams gives you a single place to manage all of it.
How it works
Admin creates an organization
Set up your org with one command. Configure your Claude API key or corporate gateway, set VM limits, and get an invite code to share with your team.
Members join with one command
Team members run npx ooda-cli and enter the invite code. No accounts, no config — they get a cloud VM with Claude Code ready to go in minutes.
Admin sees everything
The admin dashboard shows every VM, every published site, and every member. Unpublish a site, delete a VM, or regenerate the invite code to revoke access — all in one place.
Centralized control,
individual autonomy
Org-wide access control
One invite code for the whole team. Regenerate it instantly to revoke access for anyone who hasn't connected yet. See who's joined and when.
Admin dashboard
See all VMs, published sites, and members in one view. Unpublish any site or destroy any VM with one click. No more rogue prototypes living on personal hosting accounts.
Shared API key or bring your own
Provide a shared Anthropic API key so nobody needs their own, or let members use their personal Claude subscriptions. Supports corporate LLM gateways and AWS Bedrock out of the box.
Zero setup for members
No accounts to create, no API keys to manage, no environment to configure. Members run one command, enter the invite code, and they're building. Works on any machine with Node.js.
Publishing under one roof
Every prototype publishes to *.ooda.run — no personal hosting accounts needed. Admin can see, share, or take down any published site from the dashboard.
Works with your auth
Route through your corporate LLM gateway, use Bedrock with custom headers, or configure a token helper script. Set it once in the org config — every member inherits it automatically.
One dashboard for everything
See who's building what, which sites are live, and manage access — all from a single admin view.
Acme Design checkout-redesign
Sarah Chen · 2 hours ago
brand-guidelines-tool
Marcus Obi · 4 hours ago
onboarding-flow-v2
Priya Sharma · yesterday
Built for teams who ship fast
Workshops & hackathons
Spin up 100 cloud environments in minutes. Everyone gets the same setup, same tools, same Claude model — no "I can't install Node" support tickets. Tear it all down when you're done.
Design teams
Designers prototype directly on the codebase without touching the repo. Published prototypes live on ooda.run where they can be shared, reviewed, and taken down — no stale Vercel deploys floating around.
Enterprise & regulated environments
Route Claude through your corporate LLM gateway. Use your own API keys, Bedrock endpoints, and custom auth — all configured once at the org level. Members never see or manage credentials.
FAQ
How does billing work?
ooda for teams is free. You bring your own Claude subscription (API key or corporate gateway) and sprites.dev account. We just orchestrate it.
Can we use our company's existing Claude setup?
Yes. ooda supports corporate LLM gateways, AWS Bedrock, custom headers, and token helper scripts. Your admin configures it once, and every team member gets it automatically when they join.
What happens to VMs when they're not in use?
VMs go cold after inactivity and can be woken instantly when someone reconnects. Admins can delete any VM from the dashboard at any time.
Can we control what gets published?
Yes. All published sites are visible in the admin dashboard. Admins can unpublish any site instantly, and regenerating the invite code prevents new members from publishing.
Do team members need to install anything?
Just Node.js 20+. They run npx ooda-cli, enter the invite code, and they're in. No accounts to create, no config files to manage.
How many people can be in an organization?
No limit on members. You set a max number of concurrent VMs per org to control infrastructure costs.