Practical overview
When it fits
Use OpenCompany when a job needs continuing background activity across connected tools and can be divided between a lead and focused specialist agents.
Who it is for
- People automating recurring email, calendar, messaging, coding, or coordination work
- Developers and operators who want desktop or self-hosted control of AI employee workflows
- Teams designing multi-agent roles around defined jobs
Documented uses
- Coordinate a lead agent and specialist agents around an ongoing job
- Connect agents to email, calendars, messages, browser work, code, payments, and GitHub
- Run background work triggered by events or schedules
- Review generated work and approve replies before they are sent
- Inspect and edit an employee's workspace, memory, and plain-text skills
Requirements & limits
Desktop builds are documented for Windows, macOS, and Linux. Terminal, Docker, and source-based setup are also described. The project states that users can bring their own API keys or run models locally, and that there is no subscription or usage limit.
- The system is designed around ongoing employees and multi-agent delegation rather than a single conversational assistant.
- Tool connections are central to the workflow, but provider support and authentication details are not specified in the available evidence.
- Local and self-hosted deployment options are documented, including Docker and headless-machine installation.
- The project provides a no-code canvas for assembling teams, while source-based development requires Bun 1.4+ and Python 3.12.
- The desktop builds are not code-signed, so operating-system security prompts may appear during installation.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Install OpenCompany with Docker
Set up a self-hosted OpenCompany instance and open its local interface.
Before you start
- Docker
- A cloned copy of the public OpenCompany repository
Steps
Clone the OpenCompany repository.
Change into the repository directory.
Run the documented Docker Compose build and startup command.
Open the local interface at http://localhost:5678 and register the owner account.
Expected outcome
A Docker-built OpenCompany container is started with its data stored in the documented Docker volume.
Guide limitations
- This guide covers self-hosting setup only, not configuring an AI provider or running an employee.
- The documented port is published on the host machine only.
Create an AI employee from the desktop app
Set up an employee from a plain-language job description and connect an AI provider.
Before you start
- A supported desktop build for Windows, macOS, or Linux
- An AI provider connection or locally run model
Steps
Download and install the desktop build for the computer.
Launch the app and describe the job for the first employee on Home.
Connect an AI provider when prompted, or add one in Settings > Connectors.
Review the drafted employee setup and press Hire.
Expected outcome
An employee setup is created from the described job and can be connected to the documented workflow tools.
Guide limitations
- The evidence does not specify supported AI providers or authentication configuration.
- This recipe does not document the complete process for running a job after hiring.
Compare options for Agent orchestration
These projects document a common task and share a project role. This is a source-based comparison, not an execution benchmark or a guarantee of interchangeability.
| Project | Documented purpose | Platform | Access and requirements |
|---|---|---|---|
| Opencompany — zeenie-ai | Coordinate a lead agent and specialist agents around an ongoing job | Desktop, Self-hosted | Desktop builds are documented for Windows, macOS, and Linux. Terminal, Docker, and source-based setup are also described. The project states that users can bring their own API keys or run models locally, and that there is no subscription or usage limit. |
| Agentic AI Helpdesk Platform | Classify tickets by issue domain and category, and estimate urgency and complexity. | Cloud, Docker, Web | |
| Tgo | Configure multiple AI agents for different customer-service scenarios and connect supported LLM providers. | Docker, Self-hosted, Server | The repository describes Tgo as open source and provides self-hosting instructions. Its README lists minimum server requirements of four CPU cores and 8 GiB of RAM; local development setup lists macOS, Linux, and WSL2. |
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 4 October 2026
- Original website title
- zeenie-ai/OpenCompany · Official homepage title · retained in its source language

