About DaxBax Neo

DaxBax Neo is a control panel for a team of AI agents running on your own servers. It shows what every agent is doing right now, lets you create or turn off agents, connect services and messengers to them, and assign them scheduled tasks — without logging into each server by hand over SSH.

An agent in Neo is a Claude Code (or Codex) instance running on your own server, shown in Neo as an “employee”: it has a name, a card, its own connections, and — if you turn it on — its own browser and its own topics in Telegram. The agents themselves run on your servers; Neo is how you manage and watch them, not a service that does the work for you somewhere in the cloud.

What it’s made of

• Servers — the machines your agents actually run on. You connect a server once, and Neo can then run one or several agents on it.
• Agents — individual AI “employees”, each with its own context and connections.
• Projects — shared context for several agents at once: who you are, what you do, who your clients are. Any agent attached to a project sees that description in its own instructions.
• Integrations — messengers (Telegram, MAX) and your own services (REST API, webhooks, MCP servers) that an agent can use.
• Scheduled tasks — what an agent does on a schedule, without you.
• Sessions — agents’ live terminals, and their browser sessions when you ask an agent to sign in somewhere under your own account.

Who this documentation is for

People who actually use Neo: setting up servers and agents, connecting services, watching tasks and what agents are doing. This is not an API reference — Neo has no public API for third-party integrations the way an ordinary SaaS product does with a token. Everything is managed through this interface.