Open Computer Orchestration

Open Computer Orchestration (OCO) is an open-source management platform for administrators overseeing mixed fleets of computers and mobile devices. It is best suited to organizations prepared to host and maintain their own Linux server. Its breadth is useful, but the server and browser requirements make it a more deliberate choice than a hosted service.

Overview

OCO brings Linux, macOS, and Windows computers together with Android and iOS devices in a web-based management system. Its scope runs from inventory and software deployment to patching and operating-system installation, making it relevant to teams that want more than a tool for pushing applications.

Deployment records include each job’s exit code and command output, giving administrators a practical way to review results. Policies, installed-software lists, custom reports, and fine-grained roles and permissions add oversight for organizations that need to control both what is installed and who can manage it. Commercial support, environment-specific adjustments, and custom report development are available by arrangement.

OCO is self-hosted on premise, though users can request a cloud-hosted trial. The server can run on any Linux distribution and uses MariaDB, Apache2, and PHP 7.3 or newer. The documented admin client supports Chromium-based browsers and Firefox from version 80. Those requirements are manageable for teams with Linux administration capacity, but they are a real operational consideration for organizations seeking a service that requires little infrastructure care.

See our Application Deployment Software list for more options in the category.

Key features

• Inventory, deployment, and patching: OCO combines device inventory with software deployment, scheduled deployments, third-party app patching, and remote app removal. That breadth can consolidate routine fleet work; deployments use an agent, so administrators should account for deploying and maintaining it.
• Job-level records: Exit codes and command output for each software job help teams investigate whether a deployment succeeded and what it did, rather than relying only on a success indicator.
• Policies and access control: Policy management, installed-software lists, and fine-grained roles and permissions suit organizations that need differentiated administrative access and consistent software rules.
• Operating-system installation: Automated OS installation extends OCO beyond application rollout, particularly for teams that also manage computer provisioning.
• Reports and automation: Custom reports and a JSON-RPC API support organization-specific oversight and workflow automation. Extensions add scheduled Wake On Lan and kiosk shutdown, automatic package creation, and PC installation workflow automation.

Pricing

OCO has a free plan and a free trial. Free (up to 20 devices) costs nothing for 20 managed devices, making it a useful fit for small deployments or evaluation. The project page says a license is required to manage more than 20 computers in a commercial environment, so commercial growth beyond that threshold is not simply an extension of the free tier.

Enterprise license costs €299 a year, billed per device for one year, and applies to additional devices beyond the 20 free devices. Individual conditions are available on request. The per-device annual term matters when budgeting a larger fleet; organizations needing tailored terms can discuss them with the vendor. The project also offers a cloud-hosted trial by request.

Platforms

The management scope covers Linux, macOS, and Windows computers, plus Android and iOS devices, through a web interface. OCO itself is self-hosted, with a JSON-RPC API for customization and workflow automation. Its server depends on Linux, MariaDB, Apache2, and PHP 7.3 or newer, while the documented admin client requires Chromium-based browsers or Firefox version 80 or newer.

Who it's for

OCO is a strong fit for organizations managing mixed computer and mobile fleets that want inventory, patching, deployment controls, OS installation, and reporting in one self-hosted system. It is especially compelling where open-source software, job-level deployment output, or API-driven automation matters and the team can operate the required server stack.

It is less suitable for small teams that want to avoid server administration, or for commercial fleets exceeding 20 computers that are not prepared to license additional devices. Teams should also confirm the documented browser support against their admin environment before committing.

Pros and cons

• Pro: Broad coverage across desktop and mobile operating systems, with inventory, remote removal, scheduled deployment, and third-party patching in the same system.
• Pro: Per-job exit codes and command output give administrators useful diagnostic evidence when software rollouts need investigation.
• Pro: Open-source, self-hosted operation plus a JSON-RPC API and extensions allow organizations to shape workflows around their environment.
• Con: Self-hosting requires a Linux server with MariaDB, Apache2, and PHP 7.3 or newer, adding infrastructure responsibility that hosted-first teams may not want.
• Con: Commercial management beyond 20 computers requires a license, and the enterprise fee is billed per device for one year.
• Con: Admin client support is documented for Chromium-based browsers and Firefox from version 80, which may constrain teams using other browsers.

Alternatives

For a broad comparison of deployment tools, start with our Application Deployment Software directory.

• FileWave is worth comparing if its Community Edition’s free allowance of up to 15 computers, 15 tablets, and 15 Chrome devices better matches a smaller mixed-device fleet.
• OPSI may suit teams wanting a free Community plan with unlimited devices and core features, accepting its one-worker-process limit.
• ManageEngine Patch Manager Plus is an alternative for teams whose needs fit its free edition allowance of 20 workstations and 5 servers.
• AppPorter is another option to compare for application deployment across its listed desktop and mobile platforms.
• Pckgr RMM is an alternative for macOS and Windows environments seeking a per-device monthly Pro plan.
• Action1 is worth considering for teams seeking a free plan covering 200 endpoints across Linux, macOS, and Windows.
• WAPT is another option to compare for deployment across its listed Linux, macOS, and Windows platforms.
• Tanium Deploy may suit organizations already using a Tanium license that includes Deploy and Tanium Core Platform servers.

Verdict

Choose OCO if you need open-source, self-hosted management spanning computers and mobile devices, and value its combination of deployment records, policies, automation, and OS installation. Its main trade-off is operational: you must run the server stack, and commercial fleets beyond 20 computers need a per-device annual license. Look elsewhere if avoiding infrastructure work or that licensing step is a priority.