On this page

Open-Source PLM for Robotics

Dokuly, Cascadia PLM's open core and selected OdooPLM add-ons are open-source product lifecycle management (PLM) candidates for self-hosting. Start with Dokuly for a compact product and document record, Cascadia for branch-based review, or OdooPLM if you already plan to run Odoo 19.0 Community. In each case, test whether the edition preserves the approval of exact hardware and firmware selections and can reconstruct the release after later changes.

Odoo licences its own PLM application as part of Enterprise. OmniaSolutions offers OdooPLM as a third-party server-module suite with its own licences and dependencies. Its desktop computer-aided design (CAD) client is proprietary. Sources reviewed on 20 November 2026. Odoo edition evidence · OdooPLM licensing evidence

If your first question is who should own the change and release record, start with the broad robotics PLM guide. This article focuses on source ownership, module boundaries, self-hosting and evidence from a fair evaluation.

What counts as open source in this comparison?

Source-code visibility alone does not establish open-source rights. The Open Source Initiative's definition, reviewed on 20 November 2026, includes redistribution and modification rights and excludes restrictions against commercial fields of use.

Table 1. Distinctions to record before treating a product as an open-source option.

Description What it establishes Buying check
Open-source software An applicable licence permits use, modification and redistribution subject to its terms. Read the licence for the exact release and all required modules. Confirm the workflow exists in that distribution.
Source-available software You can inspect some source. Terms may restrict use, distribution or modification. Read the applicable licence for the exact repository and release.
Open-core product An open-source core is offered alongside separately licensed capabilities. List the features and dependencies your release exercise needs, including anything outside the open distribution.
Free tier or trial Some access costs nothing under a service or product plan. Check deployment rights, data export and plan conditions separately. Price does not establish an open-source licence.
Community add-on A third-party module extends a Community platform. Check its licence, target major version, dependencies and maintenance independently of the platform's name.

Cascadia uses an explicit open-core and dual-licence model. Its open core is a valid candidate. Its commercial connectors and advanced audit package remain outside this comparison. OdooPLM's reviewed server modules use open-source licences, while its separate proprietary client remains a distinct buying decision. A free hosted account would not change either boundary.

Comparison methodology, source dates and commercial interest

The audience is robotics founders and engineering, manufacturing and operations leads moving from prototypes to low-volume production who are assessing self-hosting or source ownership. The three named projects have identifiable repositories, licences and relevant workflows.

We compare change requests and engineering change orders (ECOs), attributable approval, item and bill of materials (BOM) revision history, recoverable release snapshots, audit and export scope, verification evidence links and deployment responsibility. All primary sources cited for this comparison were reviewed on 20 November 2026. Tagged documentation is preferred where available. Claims about repository code are identified as inspected source, with no claim that it ran successfully.

No product was installed or trialled. The WP-200 case is fictional, and the protocol below is a proposed evaluation with expected outcomes. There are no observed vendor results, performance comparisons, prices or numerical scores. Missing evidence remains unknown.

Arc is the proposed publisher and sells engineering software, so it has a commercial interest in the topic. Use the existing buyer-guide methodology to keep criteria and evidence comparable. This article uses qualitative acceptance conditions for the robot change and does not import aerospace weights or assign a vendor ranking.

Which editions and releases were checked?

The licence abbreviations below are GNU General Public License (GPL), GNU Lesser General Public License (LGPL) and GNU Affero General Public License (AGPL). All three are open-source licences with conditions that the selected deployment and any modifications must honour.

Table 2. Candidates and the version of the evidence inspected for each. Source-review date for every row is 20 November 2026. Candidate source notes

Candidate and inspected version Licence evidence Relevant workflow evidence Boundary to retain
Dokuly, public self-hosted repository, tag 1.0.0. Release published 11 April 2026. The tagged LICENSE contains GNU General Public License version 3 text. Tagged engineering change order documentation describes affected items, Draft/Review/Released states and recorded quality-assurance reviewer, releaser and release date. Affected items are released separately before or alongside the ECO. Administration documentation allows release-state overrides. Test release consistency and privileged corrections.
Cascadia PLM, AGPL open core, tag v0.6.0. Release published 7 October 2026. Tagged LICENSE applies AGPL version 3 or later. LICENSING.md distinguishes the open core and commercial edition. Tagged change management and versioning describe ECO branches, revision assignment on release and baseline tags. Native CAD connectors, single sign-on and the compliance/audit pack are separately licensed. Ordinary approval history is distinct from signed approvals and a tamper-evident audit archive.
OmniaSolutions OdooPLM, selected server modules on Odoo 19.0 Community. Add-on branch pinned at commit a68a27514131fea0c1eb42bd3f8885eea0ff1363, dated 20 November 2026. Core plm manifest declares LGPL-3. Selected extension manifests declare AGPL-3, with or-later grants in their headers and licence texts. Inspected revision mixin and activity_validation source define engineering revisions, lifecycle controls and linked change activities. The source review covers the specified Odoo 19.0 add-ons. Test compatibility separately for Odoo 20.0. The desktop CAD client is proprietary.

The tagged commit for Dokuly 1.0.0 is 547fb1a9cfbcda2bc6e4ddc03fdc7ad06bbb6f70. The tagged commit for Cascadia v0.6.0 is 6f89879bc8df3bb4837b56d18d5f5f7bf51a4dee. The Dokuly and Cascadia release pages establish the publication dates above. Record your eventual application commit, container digest, database version, modules and configuration alongside these references. A moving branch or image tag cannot identify a repeatable evaluation.

Odoo Community, OdooPLM and Enterprise PLM are different stacks — The reviewed OdooPLM core depends on base, board, product, mrp, stock_account and web_hierarchy. These named modules are present in the public Odoo 19.0 source. In particular, web_hierarchy is LGPL-3 in that major version. The core's manifest and immediate module dependencies were checked. A full transitive deployment and compatibility test remains to do.

Table 3. The OdooPLM server modules relevant to this release exercise, pinned to the same 20 November add-on commit. OdooPLM source note

Module Manifest version and licence Direct dependencies and purpose
plm 19.0.1.0.57, LGPL-3 base, board, product, mrp, stock_account, web_hierarchy. Engineering items, documents and BOM lifecycle.
plm_engineering 19.0.1.0.1, AGPL-3 plm. Engineering BOM representation.
activity_validation 19.0.1.0.6, AGPL-3 mail, plm. Engineering change requests and orders using activities.
plm_web_revision 19.0.1.0.1, AGPL-3 plm. Revision actions through the web interface.
plm_compare_bom 19.0.1.0.2, AGPL-3 plm. Comparison of two BOMs.
plm_pack_and_go 19.0.1.0.3, AGPL-3 plm, with external Python package base64io. Download of BOM structure files.

The repository's root AGPL licence does not relicense the LGPL core. Use the per-module manifests and full LGPL and AGPL licence texts to establish the operating and modification obligations for the selected stack. AGPL's network-use conditions matter when serving a modified version to users. The proprietary desktop CAD client is explicitly identified in the pinned README.

Do not assume every extension in the suite runs on Community because the extension itself is AGPL. For example, plm_pdf_workorder_enterprise depends on mrp_workorder, and the pinned README identifies it as an Enterprise variant. It is outside the Community stack defined here.

Odoo's upstream mrp_plm module belongs to the Enterprise product. The official edition matrix puts PLM in Enterprise, and a public first-party Odoo engineering record identifies versioned BOM change behaviour and files under odoo/enterprise/mrp_plm. The Odoo 19 Enterprise licence text requires a valid subscription and restricts redistribution. Odoo's public engineering-change documentation and approval documentation describe that upstream app. They do not demonstrate the behaviour of OmniaSolutions' plm or activity_validation modules. Exact Enterprise module code and dependencies were not accessible in this review, so they remain unverified. Enterprise PLM is excluded from the open-source candidate set. Odoo edition and module evidence

How do the candidates review and preserve a robot change?

Table 4. Documented or inspected mechanisms and the corresponding evidence to obtain in a trial. Every row uses the candidate and version defined in Table 2. Unknown means this review did not establish the behaviour. Candidate source notes

Candidate Change and approval mechanism Release, audit and export evidence Unresolved WP-200 test
Dokuly 1.0.0 ECO documentation groups affected revisions and records the quality-assurance reviewer, releaser and date. Document revisions and assembly revisions have release states. BOM export produces the current table as comma-separated values (CSV). Can one product manifest consistently freeze all affected items, selected firmware, attachments, approvals and serial applicability? Inspect a later administrative correction and historical export.
Cascadia v0.6.0 open core ECO branches isolate changes. The lifecycle engine records transitions and votes with configurable approvers. Versioning resolves item states at commits or tags. BOM exports include hierarchy, quantities, revision and state, with a separate affected-items CSV. Does approval remain tied to the exact inspected content if an in-review item changes? Can a historical export preserve selected file versions, firmware, evidence and decisions beyond the CSV structure?
OdooPLM on Odoo 19.0 Community, selected modules The inspected revision mixin controls engineering identity, revision and lifecycle. activity_validation represents linked change requests and orders, user activities and completion checks. The README documents chatter tracking and revision comparison. plm_pack_and_go downloads structure files. Do required technical dispositions block release of the exact changed items, survive activity completion and appear in a recoverable archive? Does Pack and Go select historical files, and what release or approval metadata needs a separate export?

For Dokuly, a Released item is documented as locked in ordinary editing, but an administrator can override its state. Demonstrate who can perform that correction, what record remains and how the original release pack is preserved. The ECO guide's instruction to release affected items before or alongside the ECO warrants a deliberate consistency check. It is not evidence of an atomic product-wide release.

For Cascadia, the documented In Review state locks the list of affected items but permits editing existing working copies. Its workflow guide describes fresh votes after backwards rework transitions. That does not, by itself, answer whether a vote becomes invalid when content changes without such a transition. Configure the required approvers and test the exact review-to-release behaviour. Core vote and transition history should not be described as regulated digital signatures. The tagged Advanced Auditing page explicitly excludes signed votes, a hash-chained audit trail and signed release PDFs from the AGPL edition.

For OdooPLM, inspect the activity configuration and actual permissions in the proposed installation. The source contains a privileged activity-validation override. Record whether technical sign-off, release of product and document revisions, and completion of the change record are separate steps. Check which activity and chatter records the product manifest preserves.

Verification references can be managed without assuming a full test-management product. Dokuly reference documents, Cascadia's file vault, and OdooPLM's engineering document records give an evidence-storage or linking route to evaluate. Preserve the exact TV-027 reference and its configuration applicability. A link to a report does not establish that another hardware stack passed it.

Try the same approval and release protocol in every candidate

WP-200 is the fictional warehouse picking robot used across this series. Its orderable items are WP-200-J, the JAW robot, and WP-200-V, the VAC robot. Both contain one CH-110 A chassis and one bought complete CTL-310 B controller. There are no prebuilt grippers. Firmware is a non-stocked installation reference on the controller.

REL-WP-01 was approved on 30 October 2026. It covers JAW A and the originally qualified VAC A. Five JAW A serials, WP-001 to WP-005, were built on 6 November. Actuator availability prompts ECO-027, approved on 18 November. REL-WP-02 is issued on 19 November. At the 20 November planning snapshot, batch B-2412 has 12 planned JAW B serials, WP-006 to WP-017, and 8 planned VAC A serials, WP-018 to WP-025. Material issue is planned for 14 December. Earlier robots retain their original as-built release, with no retrofit.

Table 5. The three expected release lookups. All quantities are one per selected robot, and all outcomes are illustrative acceptance conditions.

Identity to look up Required configuration and BOM Required component, drawing and firmware selection
Built serial WP-003 REL-WP-01, CFG-JAW A, BOM-JAW A GR-J210 A, containing ACT-410 A and ENC-510 A, with DW-GR-J210 A and FW-310 1.4.0 on CTL-310 B.
Planned serial WP-010 REL-WP-02, CFG-JAW B, BOM-JAW B, ECO-027 GR-J210 B, containing ACT-420 A and ENC-520 A, with DW-GR-J210 B and FW-310 1.5.0 on CTL-310 B. TV-027 covers the specified JAW B verification.
Planned serial WP-020 REL-WP-02, retained CFG-VAC A, BOM-VAC A GR-V220 A, containing one bought PMP-430 A, with FW-310 1.4.0 on CTL-310 B. No jaw encoder and no JAW firmware transfer.

TV-027 is the approved fictional verification reference for gripper fit, encoder counts and direction, and encoder fault response on the exact JAW B stack. It does not claim complete robot qualification. Neither ACT-420 A nor firmware 1.5.0 is an unrestricted substitute for the earlier configuration.

Use a private evaluation environment and assign the same responsibilities in every product. Name a change author, mechanical reviewer, electrical and firmware reviewers, verification reviewer and release authority. Record which responsibilities your team combines. Each step sets an expected result for a future test.

  1. Record the setup. Capture application tag and commit, image digest, database version, licence files, modules, permissions and workflow settings. Keep a copy of the input fixture and a result log identifying the operator and date.
  2. Establish the original release. Create or import the selected JAW A and VAC A records. Identify the REL-WP-01 approval, exact files and firmware references. Map WP-001 to WP-005 to their built JAW A release. Preserve the original data for comparison.
  3. Prepare ECO-027. Starting from the original release, revise the jaw gripper and drawing, replace the selected actuator and encoder, and reference FW-310 1.5.0. Keep VAC A unchanged. Record the reason, affected items and proposed applicability before submission.
  4. Review and reject incomplete material. In the evaluation copy, submit the change with the new firmware reference omitted. The firmware reviewer should be able to withhold acceptance and explain the missing compatibility record. Keep the rejection or hold and subsequent correction visible. Do not treat a document upload as technical approval.
  5. Test approval against changed content. Obtain the required technical decisions against an identified review snapshot. Then deliberately alter one controlled drawing or firmware reference in the test copy. Inspect whether the tool blocks the edit, invalidates the affected decisions or requires a fresh review. A passing process must prevent unreviewed content reaching the accepted release, even where an explicit manual control is required.
  6. Release the accepted configuration. Restore the intended JAW B selections, attach TV-027 and record required technical acceptance. Issue REL-WP-02 with the BOMs, configurations, source files and applicability. Check the status of each item and record any separate completion steps.
  7. Run the three lookups in Table 5. Give an independent reviewer WP-003, WP-010 and WP-020, without the author's explanation. Record the exact recovered values, release decision and evidence references. The two planned serials remain planned until manufacturing records what was actually built.
  8. Export and recover. Export the structure and selected files, plus the manifest, decisions, history and evidence references needed outside the application. Add controlled supplementary records if a native export omits them. Have the reviewer repeat the lookups from that archive, then verify a separate backup-and-restore exercise preserves the same release.

Table 6. A compact evidence log to complete during that future evaluation. No entries below report an observed product result.

Acceptance gate Evidence to retain Failure or uncertainty to record
Correct scope Old/proposed comparison, changed item identities, unchanged VAC selection and serial allocation. Incorrect variant inheritance, lost revisions or an undocumented manual mapping.
Attributable approval Actor, decision, timestamp, review snapshot and required technical dispositions. An approval that can release changed content without its acceptance, or an undocumented override.
Recoverable release Product manifest, exact BOM and file revisions, pinned firmware and TV-027 applicability. A historical lookup resolving current files or missing reference context.
Audit and exit Preserved rework decisions, subsequent corrections, exported history and independent recovery evidence. Missing metadata, closed activities that cannot be reconstructed, or a paid feature silently needed.
Operable self-hosting Version inventory, permissions, backup and restore result, upgrade replay and owner. Unpinned images, files omitted from backup, or an upgrade that changes historical selections.

A native CSV export can support the archive without being the whole archive. For example, Cascadia's documented BOM fields do not include the approval votes or verification reports. OdooPLM's file download and Dokuly's current-table CSV likewise need an explicit check of what survives. Record whether the missing context can be preserved reliably with a controlled supplementary manifest.

What operating work comes with self-hosted PLM?

Assign an application owner before treating hosting as a deployment preference. The team must maintain roles, updates, database and attachment storage, backups, restoration and a working review workflow for occasional contributors as well as daily authors.

The tagged Dokuly setup guide describes Django and PostgreSQL with Docker development paths. Confirm your production configuration and back up uploaded files as well as the database. Dokuly source note

For Cascadia, the tagged upgrade guide distinguishes released database migrations from the schema-push path used in development. Plan updates around pinned application and service versions, then repeat the release-recovery checks after migration. A backup that restores rows but loses the selected vault files is incomplete for this buyer job.

For OdooPLM, pin Odoo and the add-ons together, inventory their immediate and transitive dependencies, and rehearse upgrades with representative engineering history. A maintained Community platform does not establish that each third-party module supports the next major version. This guide's Odoo 19.0 evidence must not be combined with the separate open-source material requirements planning (MRP) guide, which evaluates a different version set, without a compatibility review.

Keep the engineering release and downstream material authority explicit. If inventory and build planning are the immediate need, use the open-source BOM comparison and MRP selection guide at that handoff. The broad BOM guide defines the manufacturer package to preserve.

Which candidate should a robotics team try first?

Try Dokuly when your initial scope is a compact product and document record with explicit quality-assurance and release responsibilities. Make the consistency of separately released items, privileged overrides and the full exported product manifest acceptance gates.

Try Cascadia's open core when isolated engineering-change branches, revisioned relationships and baseline recovery are central to your intended process. Check exact review-content acceptance, historical file resolution and archive completeness. Confirm whether any required signature or advanced-audit obligation would change the edition.

Try the specified OdooPLM stack when Odoo 19.0 Community is an intentional platform choice and your team can own the engineering add-ons. Test activity-based technical decisions, release gating and historical file export before relying on them. Confirm the licence and dependencies of every CAD connector and module in the workflow.

Complete the same protocol before selecting any of them. A successful evaluation leaves another engineer able to recover the original jaw robot, the revised jaw build and the unchanged vacuum configuration, with the approval and evidence explaining each selection.