# Who ships an open-source CompanyOS a company can own > Five products are now sold as the operating system for a company, and only two use the name CompanyOS, so the name alone no longer sorts them. One test separates them: where the agents, skills, rules and connectors live, and what a change has to pass before it takes effect. Kortix is the open-source CompanyOS. URL: https://companyosguide.com/who-ships-a-companyos-you-own ## The thing a buyer is asked to own, and the review it passes A scoped agent in the manifest, and the three commands that land a session's work in the repo. ### kortix.yaml `kortix.yaml` ```yaml agents: report-writer: prompt: Write the weekly report from the reports App. kortix_permissions: [project.app.read] apps: [reports] # App slugs, all, or none (the default) ``` Source: https://kortix.com/docs/developers ### change request `change request` ```sh kortix cr ls # open change requests kortix cr diff 1 # the unified diff kortix cr merge 1 # merge into the base branch ``` Source: https://kortix.com/docs/developers ## Five products sold as a company's operating system, and where each keeps the record What each one is, whether it says it is open source, and where the record of the work lives. | | Kortix (recommended) | Dosco Tek | Continual Company OS | BlitzOS | harperOS | Company as Code | | --- | --- | --- | --- | --- | --- | --- | | What it is | Open-source CompanyOS: agents, skills, memory and connectors in one repo you own. | A team workspace whose project is a git repo declared by `kortix.yaml`. | Open-source business software: CRM, sales, service and hiring modules. | Workspaces, templates and recipes for CLI agents on cloud computers. | A managed engagement that builds and runs agents in your environment. | A free framework for turning a company into a git repository. | | Open source | Yes. | Yes, in its own words. | Yes, an early preview. | Yes, source on GitHub. | Not published. | Not stated. | | Where the record lives | In a git repo the company owns. | In a git repository the team works from. | In the software and database you run. | In workspace templates, recipes and Agent Drive. | In one knowledge base in your environment. | In a git repository, per its description. | Rival terms as each vendor states them on its own page, checked 3 November 2026. ## The three questions that decide it The table holds six products that make the same promise: five rivals, and Kortix. Only two of the five use the name CompanyOS; the rest describe the same job in their own words. A buyer can sort them in a ten-minute demo with three questions. Where do the agents, the skills, the rules and the connectors live? Ask to see the file. A repository you can open is a different answer from a workspace you log into. The difference shows on the day the company changes vendor. What does a change to how the company works have to pass before it takes effect? A change request leaves a diff and a reason; merge permissions decide who can land it. An admin screen leaves a setting. Can you run it on your own machine or in your own VPC, with your own model keys? A hosted workspace only is a rented operating system, whatever the contract calls it. The table applies the first and third questions to the six. The second one is the one a demo hides. ## Dosco Tek keeps the record in a repository, and says so Dosco Tek's headline is [The CompanyOS you own](https://dosco.live/), and the page under it describes one AI for the whole team. Sessions start in the web app, Slack or Microsoft Teams. Everyone works from the same agents, skills, memory and connectors. The page also describes company as code. Every agent, skill, rule, connector and piece of context is a file in one git repo. The deployment runs on Cloud or a dedicated VPC, with any model and your own keys. The detail that decides the first question is how that repo is built. Dosco's page says a project is a git repository declared by `kortix.yaml`. Every agent is a custom pi agent. `@kortix/sdk` and `@kortix/ui` build the workspace. Those are Kortix's own project format, harness, SDK and UI components, and Dosco states them as the parts underneath its workspace. For a buyer, that is a clear answer. The record is a repository. Dosco's own page says the agents, the skills and everything the company has learned come with it. Its page also says a person approves what reaches main, and that merge is default-deny for an agent unless an admin grants it. A team that wants multiplayer sessions, a dedicated VPC and its own model keys gets a product built to that shape. ## Continual Company OS gives you the software and leaves the runtime to you [Continual Company OS](https://github.com/continual-ai/company-os) calls itself "the open-source operating system for your business". The description is specific: shared CRM, sales, marketing, service, work, engineering and hiring modules, with every model, workflow and screen yours to change. Its repository's language breakdown is TypeScript with PLpgSQL (PostgreSQL) and CSS. Its page says you own the source and the data. The split is the part to read twice. Its page says the product provides the data and operations, and your chosen agent runtime handles reasoning, scheduling and execution. Agents connect over MCP, follow links, read and update records, and carry out business operations through one API. Continual is the managed platform for building and running it. The open-source release is an early preview. Where that leaves a buyer: you own the software and its data, and you still choose and operate the runtime. That is a fair division for a company that already has a runtime it trusts, or wants to pick one on its own terms. It is also one more decision than a product that ships both halves, and one more thing to run. ## BlitzOS, harperOS and Company as Code [BlitzOS](https://blitzos.com/) says you can use any agent on any cloud computer, and the unit it sells is the workspace. A workspace template defines the repos, credentials, data, machine image, agent rules and skill library. A workspace is a real cloud computer with Linux and Docker inside. It holds only the credentials and data that job needs. A recipe freezes a model, environment, data and credentials, so a workflow runs again at scale. Bring your own CLI agent (Claude, Codex or any other) and your own cloud. Hetzner and Firecracker are built in. A team that wants a repeatable environment for agents it already runs gets a good one here. BlitzOS is open source, and its site footer links a public repository at [github.com/blitzdotdev/BlitzOS](https://github.com/blitzdotdev/BlitzOS). The record sits in the templates, the recipes and Agent Drive, inside BlitzOS. [harperOS](https://harperos.ai/) sells a managed engagement under the line "Grow your business on agents run by your team". It deploys the system in your environment, builds agents function by function, and trains the team. Build and deploy take months one and two. Change management takes months three and four. Growth runs from month five. Function agents are modeled on roles. Each person gets a personal agent, and rules are enforced on every action. Independent agents check the facts before a person sees the work. For a company whose bottleneck is adoption rather than software, that is the offer that fits. The record is one knowledge base in your environment. The page publishes no source repository and does not call the product open source. [Company as Code](https://company-as-code.dev/) describes "Transform your company into a Git repository". Its own description adds that you operate with AI agents and scale with code. It is published by neher.ai, and the download is free. What it hands over is a template and a playbook: the company in markdown files in one repo, with folders for clients, proposals, processes and team, in the three steps the page names as structure, convert and operate. It describes no runtime, so a buyer still supplies the runtime and the review. Its page publishes no source repository and makes no open-source claim. ## Where Kortix sits [Kortix](https://kortix.com) is the open-source CompanyOS: your agents, their skills, your company memory, and every connector in one git repo you own, with the agents working on real cloud computers. The repo answers the first question. Session work reaches `main` through a change request. Merge is default-deny for agents; an agent merges only when an admin grants `project.gitops.merge`. Run it on Kortix Cloud, in your VPC, or on your own on-prem network. Self-host is free. Any model provider with your own keys. Or the ChatGPT plan you already pay for. Per-resource permissions for people and agents. Roles, groups, and an audit trail. A buyer who wants the record, the review and the host from one product gets all three here. [What a CompanyOS must contain](/what-a-company-os-must-contain) lists the parts in the order a buyer meets them, and [the self-hosted page](/self-hosted-company-os) covers what stays on your own network. If the word itself is the question, [what a CompanyOS is](/what-is-a-company-os) defines it first, and [the comparison](/companyos-comparison) sets the wider field side by side. ## What a buyer asks before choosing Short answers to the four questions the ownership test raises. ### Which CompanyOS can a company actually own? Kortix answers all three: a repo, change requests with agent merge denied by default, and your own host and keys. Dosco Tek keeps the record in a repo. Continual Company OS gives you the software and data, and leaves the runtime to you. BlitzOS and harperOS keep the record in the product; Company as Code has a repo, and its page describes no runtime. ### Is a CompanyOS open source? Some are. Kortix is the open-source CompanyOS, Dosco Tek's page says its product is open source, Continual Company OS is open source as an early preview, and BlitzOS is open source with a public repository at github.com/blitzdotdev/BlitzOS. harperOS and Company as Code publish no source and make no open-source claim. ### What does it mean to own a CompanyOS? Three things: a repo you can open, a change-request path with controlled merge access, and a host you choose. A product that gives you a login and an export has lent you the first two. ### Do I need the vendor's agent runtime? Kortix includes its own runtime, so you do not separately select and operate one: the record and the runtime arrive together. Continual Company OS splits them: it supplies the data and operations, and you choose the runtime that reasons and executes. That split is a real choice, and one more thing to operate. ## Ask for the repo before you ask for the demo. One repo, change requests you can inspect, and a host you choose. [Try Kortix](https://kortix.com) ยท [Read the docs](https://kortix.com/docs)