Self-hosted company OS, Claude Code and Codex agents in departments

Hi HN, I am Dimitris. This is a company OS that I built and use to run my business and anyone can install it and self host it for free. Think of it as Claude Code, Cowork and the cloud sessions in one self hosted application.It is a Multi-tenant application by design where many people can collaborate on the company agents with 4 different modes of collaboration, and it runs with your Anthropic or OpenAi subscription or even with local models.Every agent can run on Claude Code or Codex CLI running as a persistent process on your server in a kernel sandbox (bubblewrap) with network isolation always on (pasta), with its own workspace, memory, schedules and tools. The same agents can also be configured to run identical on any remote computer through one outbound WebSocket (no inbound ports, no VPN needed).The agent already have lots of built in features, as an example they can answer and place phone calls through Twilio or your own Asterisk, they can edit videos and excel, word, ppt files and preview them directly inside the chat with collabora and many more.Trying it is one install script and a docker compose, no signup. The license is Fair Source, all the code is public and self hosting is free up to 5 users. 1.6.0 went out today.AI Disclaimer: large parts of OtoDock are written using OtoDock itself, running Claude Code.I would love people to read the code, take a look in the sandbox model, and tell me what would stop you from running this on your own hardware.GitHub: https://github.com/OtoDock/oto-dock Website: https://otodock.io

Hacker NewsToolAISource
0Sign in to voteCopy link

FL score

62

out of 100

Verdict

VALIDATE

high confidence

Competition

No competitor data yet

Trend

No signal yet

Self-hosted workflow automation platform that runs AI agents across departments with built-in collaboration, sandboxing, and integration capabilities.

The pain

Companies need to run AI agents internally without vendor lock-in, data leaving their servers, or dependency on cloud subscriptions. Teams struggle to coordinate AI work across departments. Existing solutions (Make, Zapier, n8n) lack native AI agent capabilities; AI platforms (Claude Projects, OpenAI) lack self-hosting and multi-department orchestration.

The gap

No mature open-source platform combines: (1) self-hosted AI agent execution with proper isolation, (2) multi-tenant collaboration modes, (3) department-level workflows, (4) support for multiple LLM backends, and (5) native integrations (Twilio, video editing, office files). The market has point solutions but not integrated stacks.

Build angle

Position as infrastructure for enterprises that need AI automation without cloud dependency. Focus on: security/compliance teams (data stays on-prem), regulated industries (healthcare, finance), and large orgs with existing server infrastructure. Emphasize the sandbox model and network isolation as differentiators. Build case studies showing cost savings vs. cloud AI platforms.

Strengths

  • Technical depth: kernel sandboxing, network isolation, and persistent agent processes show real engineering
  • Self-hosting removes major friction point for enterprise adoption
  • Fair Source licensing with free tier up to 5 users lowers barrier to trial
  • Multi-tenant design and 4 collaboration modes address real team coordination problems
  • Founder actively using it in production (not theoretical)
  • Supports multiple LLM backends (Anthropic, OpenAI, local models) prevents lock-in
  • Built-in integrations (Twilio, video, office files) show practical thinking beyond basic automation

Risks

  • Positioning unclear: is this for SMBs, enterprises, or developers? Messaging conflates multiple use cases
  • Adoption friction: requires Docker, server infrastructure, and technical setup. Not plug-and-play for non-technical users
  • Market timing: n8n, Make, and others are rapidly adding AI capabilities. Unclear if self-hosting alone justifies switching
  • Monetization model untested: Fair Source with 5-user free tier may struggle to convert to paid. Enterprise sales cycles are long
  • Competition from established players: if Anthropic or OpenAI release self-hosted versions, this becomes obsolete
  • Documentation and community: GitHub shows active development but unclear if docs support non-technical users
  • Vendor risk: depends on Anthropic/OpenAI APIs for most use cases. Local model support is niche
  • Feature creep risk: too many integrations (Twilio, video, Excel) without clear focus. Depth vs. breadth problem

Questions about this idea?

FlyBot reads the scoring and gives you a second opinion on “Self-hosted company OS, Claude Code and Codex agents in departments”.

Open FlyBot