OtoDock
OtoDock is a self-hosted platform for running a team of persistent, collaborative AI agents on infrastructure controlled by the customer. It connects Claude Code, Codex, customer API keys or local models to a multi-tenant dashboard for chat, automation, tools, phone calls and shared company workflows.
At a Glance
- Organizations and teams seeking a company-wide AI agent platform
- Small and growing teams licensing by seats
- Enterprise deployments requiring SSO, SLA or air-gapped operation
- Individuals wanting a self-hosted AI assistant
- +2 more
AI Tools by OtoDock
(1)
OtoDock
Self Hosted AI Agent Platform
Discussions
No discussions yet
Be the first to start a discussion about OtoDock
Latest News
OtoDock 1.6.0 released with GPT-6 Astra on Codex, local models across the platform, an expanded Direct LLM engine, caller identity/retention controls and use of a customer's own browser.
OtoDock 1.5.0 released with remote machines, phone calls, live voice conversations, departments, shared knowledge libraries and a 3D company map.
OtoDock 1.4.0 released with agent-created agents, 1 GB uploads and sync, Claude Opus 5, cross-engine chat continuation and improved remote/terminal capabilities.
OtoDock 1.3.0 released with additional agent platform capabilities and tooling, documented in the public changelog.
Products & Services
Docker-installable, fair-source platform for running persistent AI agents on customer-controlled infrastructure. It provides a live dashboard, multi-tenancy, agent workspaces and memory, delegation, meetings, scheduled tasks, webhooks, files, documents, artifacts, voice, phone and security controls.
The public source repository for OtoDock, licensed under FSL-1.1-Apache-2.0 (with an Apache 2.0 future grant), containing the platform, Docker Compose deployment and supporting services.
Public documentation covering installation, first run, architecture, security, remote machines and self-hosted operation.
Enterprise deployment and support offering with custom terms for 100+ seats, volume licensing, air-gapped deployment, SSO/OIDC, priority support and an SLA.
Market Position
OtoDock positions itself as a self-hosted, multi-tenant company OS for persistent AI agents rather than a single-user chat product. Its differentiators are customer-controlled infrastructure and credentials, BYO Claude/ChatGPT subscriptions or local models, kernel-sandboxed agents, team/department/delegation primitives, phone and remote-machine operation, and fair-source licensing; this contrasts with primarily hosted AI workspaces and developer agent frameworks that do not combine these company-operations features in one deployable platform.
Leadership
Founders
Dimitris Mourtzis
The author and developer behind OtoDock; his GitHub profile says he is building OtoDock and lists Athens as his location. The repository's author note says he started OtoDock after wanting to use Claude Code beyond the terminal and connect it to his services.
Founding Story
OtoDock started with Claude Code. Dimitris Mourtzis wanted to use it beyond the terminal and connect it to his services, so he built a platform around that idea; it then became the place where his own agents work. The initial vision was a fair-source, self-hostable company OS in which teams could run persistent agents with their own data, credentials and infrastructure.
Business Model
Revenue Model
Self-hosting is free for up to five users; growing teams license the same software by seats. Enterprise customers receive custom terms, volume licensing, air-gapped options, SSO and support/SLA. Customers separately supply their own Claude/ChatGPT subscriptions, API keys or local models.
Pricing Tiers
Up to 5 users; self-hosted; free forever.
4–15 users; all features; email support.
16–50 users; all features; priority support.
51–100 users; all features; SLA.
100+ users; custom terms, air-gapped option and SSO.
Target Markets
- Organizations and teams seeking a company-wide AI agent platform
- Small and growing teams licensing by seats
- Enterprise deployments requiring SSO, SLA or air-gapped operation
- Individuals wanting a self-hosted AI assistant
- Security- and privacy-sensitive organizations that need infrastructure and credentials under their control
- Developers and technical teams using Claude Code, Codex, MCPs and local models
- Personal assistants for individuals and employees
- Customer support agents
- Social media and content operations
- Business analysis and reporting
- Monitoring and system administration
- Software engineering and coding agents