Production / 02
Deploy and operate your live Odoo with dedicated production infrastructure, verified updates, and configurable backups and recovery. Give agents separate access to production operations and controlled access to business data.
01 snapshot requested
02 commit applied
03 modules upgraded
04 health verification passed
Deploy manually or enable updates from a GitHub webhook. Oduflow applies module changes, checks the service, and records what happened.
Deploy manually or trigger from a GitHub webhook.
Update the production checkout and apply the required Odoo changes.
Confirm the deployed service responds before accepting the release.
Keep the commit, actions, and outcome in your deployment history.
Oduflow automatically attempts to restore the previous checkout and restart the service. The result, including a failed rollback, stays visible in deployment history.
Code rollback does not reverse a database migration. Restore a configured snapshot explicitly, or use cluster-wide point-in-time recovery for a wider incident.
Production runs in a dedicated PostgreSQL cluster and container, separate from the development database cluster. It receives a dedicated domain through Traefik with Let's Encrypt, a production-tuned Odoo configuration, and persistent containers that are not managed by the development idle reaper.
Oduflow is self-hosted and its source is available for review. Your operators can inspect the code path that touches repositories, databases, backups, credentials, and deployment decisions instead of trusting an opaque control plane.
infrastructure: yours
source review: available
mandatory phone-home: none
production kill switch: none
Configure S3-compatible storage for scheduled and on-demand snapshots: a PostgreSQL dump, deduplicated filestore, and the deployed commit SHA. With backups configured, Oduflow also takes a snapshot before each deployment.
DISASTER RECOVERY
WAL-G continuous archiving and base backups support cluster-wide point-in-time recovery when a database incident cannot be solved by reverting application code.
Automatic deploy rollback restores code only. Database recovery remains an explicit operational decision.
Any agent. Explicit access.
Development and production MCP use different credentials. Grant production access deliberately, while development agents work through their own tools and scoped environments.
Through the OduMCP integration, agents can read business data and prepare specific changes for approval in Odoo. Model and field policies, Odoo access rules, and audit records stay with the business system.
Explore production accessThe agent prepares an exact change plan.
An authorized person reviews it in Odoo, or an explicit auto-approval policy applies.
The agent executes the approved plan; the addon enforces permissions and records the operation.
Requires the configured OduMCP addon and its policies. These approvals cover business changes in Odoo. Infrastructure deployments and restores use Oduflow's production access controls.
The health endpoint checks the production and development PostgreSQL clusters, Traefik, S3 access, disk capacity, and failed rollback state.
Choose a license for your commercial use and support needs. Solo includes Production. Selling managed hosting or a white label platform requires an Enterprise agreement.
We will review topology, deployment, backup, recovery, security, and support requirements with your technical team.
Discuss Your Setup