What changed—and why it matters.

A month-by-month view of Oduflow's evolution, distilled from the release notes into the value delivered across development and production. Updated through v1.84.0, released September 23, 2026.

Read the complete changelog

Product timeline

Newest first. Every linked version opens its complete technical release notes on GitHub.

  1. 12 releases

    A connected development and production lifecycle

    Production and development now share a practical delivery cycle, with separate access controls, stronger recovery safeguards, and annual commercial licensing.

    • Create development environments from production data, publish reusable templates, and promote a development environment into a new production.
    • Share a single-environment dashboard with trusted collaborators and revoke access when the work is done.
    • Give production its own MCP credentials and use the OduMCP integration for business-data access, approval plans, and audit records.
    • Protect production storage with WAL monitoring and recovery controls, and add authenticator-based two-factor login to the dashboard.
    • Keep project infrastructure reproducible with declarative Stacks, write-only team secrets, and unified template imports from Odoo, S3, or local files.
    • Inspect license holders, annual validity periods, and renewal status in the dashboard. PolyForm Noncommercial source terms and alternative commercial agreements retain the same code, features, and public updates for every plan.

    Releases

  2. 6 releases

    Any-agent workflows and repeatable daily operations

    Developers and agents gained easier ways to reproduce project infrastructure, reuse environments, and automate operations against a remote Oduflow server.

    • Run OpenCode alongside the existing hosted agents and define development environments and services in versioned Stack manifests.
    • Call the live MCP tool surface through the built-in remote CLI, including scoped access to one environment.
    • Reuse an environment by switching branches, choose an environment name independently of its branch, and edit its configuration from the dashboard.
    • Manage persistent PostgreSQL databases for auxiliary services, preserve template environment variables, and publish incremental template snapshots.
    • Keep agent context focused with concise apply and test summaries, while retaining detailed output for inspection when needed.

    Releases

  3. 9 releases

    Production hosting joins the development platform

    Oduflow added persistent production hosting alongside isolated development environments, with deployment verification, backups, and recovery on the same self-hosted platform.

    • Run production on a dedicated PostgreSQL cluster with custom domains, verified deployments, automatic code rollback, S3 snapshots, and cluster-wide point-in-time recovery.
    • Run an isolated coding agent for each team, with persistent workspaces and both terminal and browser chat interfaces.
    • Give agents scoped MCP credentials for one environment instead of exposing team-wide access or long-lived secrets.
    • Serve multiple teams safely with per-host OAuth, authenticated dashboards, hardened proxy trust, and stronger tenant boundaries.
    • Move real Odoo.sh projects more reliably with resumable uploads, Enterprise and extra-addons support, native database neutralization, and flexible template imports.
    • Expose only the service routes you intend, while dependency changes and long-lived MCP sessions now synchronize and restart predictably.

    Releases

  4. 6 releases

    Public release and a sharper daily workflow

    The public release made local development faster, operations safer, and the dashboard more comfortable for long working sessions.

    • Edit live-mounted projects directly—including non-Git folders—while Oduflow detects and applies only the changes that matter.
    • Let environments stop when idle, wake on demand, and clean themselves up without touching protected work.
    • Manage service volumes, networking, environment variables, and lifecycle operations from the same agent-native workflow.
    • Start from safer defaults with unique database credentials, host-aware PostgreSQL tuning, and clearer agent guidance.
    • Work in a redesigned, accessible dashboard with light mode, larger type, clearer status, and more useful logs.

    Releases

  5. 2 releases

    Faster setup and deeper agent control

    Getting started became nearly automatic, while agents and operators gained a broader, more dependable set of tools inside each environment.

    • Start in MCP-friendly stdio mode and let Oduflow initialize itself on first run instead of following a separate bootstrap sequence.
    • Use a larger, refined MCP toolkit with cached long-running results and clearer commands for common Odoo development work.
    • Apply configuration changes during upgrades and rebuild environments from the dashboard with current container images.
    • Operate with safer sanitization, more reliable team-aware actions, and clearer search results when diagnosing an environment.

    Releases

  6. 3 releases

    The platform foundation

    The first releases established the core promise: production-shaped Odoo environments that are fast to create, isolated by default, and controllable by people or agents.

    • Import reusable templates from running Odoo systems and create development environments without repeatedly copying full databases and filestores.
    • Keep environments separated with dedicated PostgreSQL credentials and layered database sanitization for safer production-derived data.
    • Give agents purpose-built access to files, SQL, admin recovery, repositories, and environment lifecycle operations through MCP.
    • Debug from the dashboard with interactive SQL and Odoo consoles, structured sync results, and readable colored logs.
    • Handle large dumps without memory spikes, deploy with Docker, and follow structured documentation and version-specific Odoo guides.

    Releases

Browse every release on GitHub