Your Odoo team's
development workspace.
Invite your developers and functional consultants, connect your repositories, and open a ready Odoo dev environment in the browser. Code with an AI agent, spin up a preview instance, and ship through protected branches — all in one place.
From invite to merged, in one workspace.
The full cycle your team runs every day — no local installs, no shared passwords, no "works on my machine".
Add your team
Your workspace lives on its own subdomain and is invite-only. Add implementers, functional consultants and developers as members or admins — anyone else who signs in is turned away.
Connect the project's repository
The admin connects GitHub (GitLab is supported too). Members request push access to a repository with one click — it is granted for 7 days and revoked automatically. Or a member claims an open ticket, which grants access for them.
Launch a dev environment on a branch
Pick the repository, branch, Odoo version and edition, and a machine size. VS Code opens in the browser on a ready server, with the repo cloned and its own PostgreSQL database.
Build it with the AI agent
Describe the change in plain words, attach a screenshot, screen recording or voice note, and the built-in agent edits the code. It runs on your workspace's own Claude account, so usage is yours — and it knows which branches are locked.
sale_order.py and sale_views.xmlDeploy a preview instance
Start Odoo from the session's checkout, with your addons on the path and a database of its own, at a private preview URL over HTTPS. Share the link with the consultant or the client for testing.
odoo https://…preview…/web ●
postgres own database ●
The agent upgrades the addon and tests it
Each session has a server connection (URL, database, login) that follows your preview by default — or points at any staging server you enter. After every code change the agent restarts the preview, installs or upgrades the module over XML-RPC and checks the result, and tells you plainly what it tested.
✓ acme_sale_limit upgraded, views parsed
Commit and push to your branch
Stage, diff, commit and push from the Source Control panel, the VS Code terminal, or by asking the agent. Commits carry each member's own git identity.
$ git push origin feat/sale-discount-limit
✓ pushed 1 commit
main refused — protected branchReview, then merge
Open a pull request (or GitLab merge request) from the IDE, watch its CI checks, and merge. Protected branches mean members can't commit, push or merge into main — admins review and merge.
Everything an Odoo team needs
between the ticket and the merge.
A complete cloud development setup, tuned for Odoo addons — and flexible enough for the side projects around them.
VS Code in the browser
Full VS Code on a ready server, repo already cloned. Open it from any laptop or tablet and pick up where you left off.
Odoo-ready out of the box
Odoo 15 to 20, Community or Enterprise, with the right Python and dependencies for each version — no installer to babysit.
AI agent on your Claude
A coding agent inside every session, signed in with your workspace's own Claude account. Attach images, video or voice notes — video is turned into stills and a transcript.
Server connection for the agent
The agent gets your preview's URL, database and login, so it can install, upgrade and check modules itself. Point it at staging instead when you need to.
One-click preview deploys
Run Odoo from your branch at a private HTTPS URL with its own database. Non-Odoo projects (Django, Node, React, PHP, Go) deploy with your own build and start commands.
Source control built in
Stage, diff, commit, push and pull; create and switch branches; stash; cherry-pick between branches — without leaving the browser.
Pull requests & checks
Create GitHub pull requests or GitLab merge requests, follow their CI checks and merge from the IDE.
Machine sizes
2 vCPU · 4 GB, 4 vCPU · 8 GB or 8 vCPU · 16 GB per session — every size is available to every member of a workspace.
No idle reaping
Sessions and previews inside a workspace are never shut down for inactivity. Uncommitted work stays where you left it until you stop the session.
Claimable tickets
Any member opens a ticket against a workspace repo; any member claims it. Claiming grants them repo access and launches a session on it.
No per-seat quotas
Inside a workspace there are no session caps, deploy caps or daily AI allowances per member. Add the whole team.
Your own subdomain
Your team signs in at your workspace's own address, with HTTPS set up automatically.
Give everyone access.
Keep control.
The workspace admin decides who is in, which branches are locked, and which Claude account pays for the AI — and can see exactly where that usage goes.
- Invite and remove members, promote them to admin
- Protected branches per repository or for all repos, with patterns like
release/* - Connect the workspace's own Claude account — no fallback to anyone else's
- AI token usage per member for today, 7 and 30 days, including former members
- Repo access lasts 7 days and is revoked automatically, so access never lingers
- Long-lived demo previews — a 30-day "keep running" option can be enabled for your workspace
main, release/* locked on all repositoriesIsolated by design.
Every session and every workspace is separated at the operating-system and database level — not just in the UI.
- Invite-only: signed-in non-members get no access to the workspace's data
- Each session runs as its own Linux user with a private home and checkout
- Each session gets its own PostgreSQL role and database
- Claude credentials encrypted at rest, sent to the agent per turn only
- Repository grants expire after 7 days and are revoked hourly
Protected branches, enforced
Refused in the IDE's git actions, on PR merges, and by git hooks that also stop the terminal and the agent.
Scoped repo access
Members only see the repositories they have been granted — none of their unrelated personal repos.
Your AI, your bill
Workspace sessions only ever use the workspace's own Claude account. If it is disconnected, the agent stops.
Dedicated infrastructure
Runs on servers we operate, with HTTPS for your workspace and every preview.
One plan. The whole team.
A flat price per workspace — no per-seat fees, no per-session meters.
ERPHub Dev workspace
For Odoo partners and in-house teams of any size
- Unlimited members — developers, implementers and FCs
- Unlimited sessions and deployments, within fair use
- Your own workspace subdomain with HTTPS
- GitHub and GitLab repositories
- Built-in AI agent using your own Claude account
- Protected branches, 7-day repo access, member usage
- Claimable tickets for the whole team
- Odoo 15–20, Community & Enterprise previews
AI usage is billed by Anthropic to the Claude account you connect — it is not included in the workspace price.
Questions, answered.
Do my developers need anything installed locally?
No. Everything runs in the browser: VS Code, the terminal, the AI agent and the preview instance. A laptop or tablet with a modern browser is enough.
Which Odoo versions and editions are supported?
Odoo 15, 16, 17, 18, 19 and 20, Community or Enterprise. You choose the version and edition when you launch a session, and the preview runs your repository as custom addons.
Whose Claude account does the AI agent use?
Your workspace's own. The workspace admin connects it once from the admin page; every member's agent turns use it, and the admin can see token usage per member. If no account is connected, the agent won't run.
What can the agent actually do on our Odoo server?
Each session has connection details — server URL, database and login — that follow its preview instance by default. The agent uses them to restart the preview, install or upgrade the module it is working on over XML-RPC, and check the result. You can point it at another server, such as a staging copy, by editing those details.
How does repository access work for members?
Repositories come from the workspace admin's connected GitHub account. A member requests access and is added as a collaborator on that one repository for 7 days; requesting again extends it, and it is revoked automatically when it expires. GitHub sends an invitation the member accepts. GitLab repositories can be used for sessions and merge requests from the admin's connection.
Do protected branches stop every push?
They block commits, pushes and merges into locked branches from everything inside ERPHub Dev — the IDE, the terminal and the agent. A member pushing from their own computer with their own GitHub access is outside our reach; for that, also enable branch protection on GitHub.
Are there limits per member?
No per-seat quotas: inside a workspace there is no session cap, no deployment cap and no daily AI allowance. Fair use applies to the workspace as a whole.
What happens to my work if I close the browser?
Nothing. Sessions in a workspace are not shut down for inactivity — your checkout, uncommitted changes and preview stay put until you stop the session yourself.
Ship Odoo changes
as a team.
One workspace for your developers and consultants. $49/month, unlimited members.
Get a workspace