Development / 01

Give every branch its own Odoo.

Build isolated environments from production-shaped templates, then let people, CI pipelines, and coding agents install, test, inspect, and rebuild without competing for one staging database.

Get Started Read the Quick Start

$ oduflow client create_environment

branch: feature/picking-agent

template: customer-production

odoo: 19.0

OK environment ready

database + filestore + repository + MCP

Bring your intelligence

Any agent.
One Odoo workspace.

Choose the agent that works for you. Connect it through MCP, CLI, or API to the same running Odoo: code, database, filestore, logs, and tests. Your project stays ready when your choice of agent changes.

Claude Code, Codex, OpenCode, an agent in your editor, or your own automation. These are examples. The workspace is yours.

Connect your agent
Your agentYour editorYour automation

MCP / CLI / API

A running Odoo, ready for work.

  • Code and the correct branch
  • Database, filestore, and installed modules
  • Tests, logs, shell, and browser feedback
  • A context that belongs to the project

One repeatable loop from branch to verified change.

  1. 01

    Branch

    Point Oduflow at a repository and branch. The environment receives its own code checkout and identity.

  2. 02

    Clone

    Start from a reusable PostgreSQL template and a copy-on-write filestore instead of restoring another full dump.

  3. 03

    Apply

    Pull code and let Oduflow decide whether modules need installation, upgrade, or a service restart.

  4. 04

    Verify

    Run tests, inspect logs, execute shell commands, and query Odoo through one operational interface.

Real data without another full copy

Keep named database templates per client, project, or Odoo version. PostgreSQL templates and layered filestores make production-sized development practical.

Safer production-derived environments

Disable outgoing mail and run team-level plus repository-level sanitization before a clone becomes available to developers or agents.

A complete feedback loop for any agent

Through MCP, CLI, or API, an agent can apply modules, run tests, inspect logs, query Odoo, and check the UI in a browser. Every change can be checked against a running system.

One server, separated teams

Share the underlying infrastructure while keeping team environments, templates, services, credentials, and port ranges isolated.

Partners. Clients. AI agents.

Join the work.
Keep the context.

A client reproduces a problem. An agent prepares a change. A partner joins the same running environment to review it. The branch, database, and filestore stay with the project through every handoff.

Share a dashboard link with a trusted collaborator and revoke it when the work is done. Scoped MCP credentials give an agent access to a specific development environment.

Explore sharing and access

Repeatability

Keep the setup with the code.

Use reusable database templates and copy-on-write filestores for parallel work. Define the environment and supporting services in a versioned Stack manifest, then validate, plan, and apply it on your Oduflow server.

The next developer or agent starts with a reproducible project, including its dependencies and configuration.

Read about Stacks

Human + agent operations

Agents get tools. Operators keep control.

The dashboard, CLI, REST API, and MCP tools operate the same environments. Choose a scoped credential for work inside one environment, or operator access for managing its lifecycle. Production MCP uses separate credentials.

  • Install and upgrade Odoo modules
  • Run module tests and retrieve container logs
  • Execute scoped shell, SQL, and Odoo operations
  • Create auxiliary services and reusable templates
  • Rebuild or delete disposable environments cleanly

95 Odoo tools at your AI agent's fingertips

The current MCP surface spans development environments, Odoo ORM, services, image builds, production deploys, backups, and recovery. Every tool is also available from the CLI.

Open the complete MCP reference
24
Odoo Operations
9
Environment Management
7
Template Management
8
Auxiliary Services
5
Service PostgreSQL Databases
8
Volumes
3
Service Presets
4
Container Image Builds
1
Repository Auth
4
Extra Addons
19
Production Hosting
2
Agent Instructions
1
Feedback

Take the next step into production.

Deploy verified changes on your own infrastructure, with dedicated production operations, backups, and recovery.

Explore Production