Skip to main content

​
Equabot Overview

Equabot is the AI engine behind the Equa platform. It powers Equanaut, the AI assistant that helps teams manage equity, cap tables, documents, and day-to-day operations through natural conversation.
Equanaut is the user-facing assistant. Equabot is the underlying infrastructure — the gateway, agent runtime, and multi-channel messaging layer that makes Equanaut work.

​
What Equabot Does

Equabot connects AI agents to the messaging channels and tools your team already uses. It handles:
  • Multi-channel messaging — WhatsApp, Telegram, Discord, Slack, iMessage, and more
  • Agent orchestration — Session management, multi-agent routing, and model failover
  • Tool execution — Browser automation, code execution, file handling, and 220+ custom skills
  • Platform integration — Direct connection to the Equa API for cap table, member, and document operations
  Equa Platform (app.equa.cc)
        │
        ▼
  ┌───────────────────────────┐
  │     Equabot Gateway       │  Agent runtime + WebSocket control plane
  │                           │
  │  ┌─────────┐ ┌─────────┐ │
  │  │ Sessions │ │  Tools  │ │
  │  └─────────┘ └─────────┘ │
  └───────────┬───────────────┘
              │
              ├─ Equanaut (web chat in Equa)
              ├─ WhatsApp / Telegram / Discord
              ├─ Command Center (expanded Equanaut, full-page)
              ├─ macOS app / iOS / Android nodes
              └─ CLI (equabot ...)

​
How It Fits Into Equa

LayerComponentRole
User-facingEquanautAI assistant sidebar in the Equa web app — the default conversational interface
User-facingCommand CenterExpanded full-page Equanaut with progressive disclosure into agent monitoring, gateway configuration, and platform details
InfrastructureEquabot GatewayAgent runtime, session management, channel routing
PlatformEqua ServerBackend API for equity, members, documents, billing
The Equa UX follows an autonomous-first design philosophy. Equanaut runs continuously, managing organizations, tasks, and operations autonomously around the clock. Most of the time, teams do not need to interact with Equanaut at all — it handles routine work in the background. When interaction is needed, the default experience is a simple chat interface: users ask Equanaut to “add a new team member” or “show me the cap table,” and the request flows through the Equabot Gateway, which invokes the appropriate tools against the Equa Server API — with permission checks, confirmation dialogs, and audit logging at every step. The Command Center extends this chat-first experience on demand. It starts as a blank page with only a welcome message and quick actions. As users send messages, a full chat interface appears. From there, users can progressively expand into optional sidebars for task priorities, agent status, and system health — or switch to a full dashboard view with monitoring, gateway configuration, and platform details. Equanaut and the Command Center share the same underlying agent session; the Command Center is simply the expanded, full-page mode of the same assistant, not a separate tool.

​
Key Capabilities

​
Multi-Channel Gateway

Equabot connects to messaging platforms so teams can interact with Equanaut from wherever they work:
  • WhatsApp — via WhatsApp Web (Baileys)
  • Telegram — Bot API via grammY
  • Discord — Bot API via discord.js
  • Slack, iMessage, Mattermost — built-in and plugin channels

​
Agent Sessions and Routing

Each conversation gets its own session with isolated context. Multi-agent routing lets you assign different agents to different channels or users — useful for separating production support from internal operations.

​
Tool Execution

Equanaut can perform actions on your behalf through a controlled tool system:
  • Read operations execute immediately (viewing cap tables, listing members)
  • Write operations require confirmation before executing
  • Destructive operations require double confirmation
All actions respect the user’s existing RBAC permissions and are logged in the audit trail.

​
Model Providers and Failover

Equabot supports multiple AI model providers with automatic failover:

​
Getting Started

​
For Equa Platform Users

Equanaut is built into the Equa web app. No separate setup required — just sign in at app.equa.cc and open the Equanaut chat panel.

​
For Developers and Self-Hosted Setups

If you are running your own Equabot Gateway: Runtime requirement: Node 22+ 
npm install -g equabot@latest
equabot onboard --install-daemon
equabot gateway --port 18789

​
Dashboard (Control UI)

The Gateway includes a browser-based Control UI for chat, configuration, sessions, and monitoring.

​
Documentation

Platform Guides

Cap table management, ESOP, agreements, team members, and more.

AI Concepts

Agent architecture, sessions, memory, streaming, and model routing.

Channels

WhatsApp, Telegram, Discord, Slack, iMessage — setup and configuration.

API Reference

Platform and Gateway API endpoints.

CLI Reference

Complete command-line reference for Equabot.

Gateway Operations

Configuration, security, troubleshooting, and deployment.