Start
Overview
#overviewOido is a cloud AI agent platform for teams. Build, configure, and deploy AI agents that do real work, answer customers, run workflows, manage projects, and keep your knowledge base current, all from a unified web UI, without writing infrastructure code.
Agents connect to the tools your team already uses: chat channels, GitHub, n8n workflows, file storage, and any MCP-compatible service. Everything they do is logged, permissioned, and visible to your whole team.
What's inside:
- Agent Studio, create and manage agents with custom prompts, models, and tool access
- Workspace, chat with agents directly in the browser
- Channels, deploy agents to Slack, WhatsApp, Telegram, Discord, WeChat, and DingTalk
- Support Desk, AI-assisted tickets and quotes
- Projects & Tasks, Kanban boards where agents execute tasks automatically
- Wiki, team knowledge base agents can read and update
- Scheduled Prompts, run agents on a schedule
- Integrations, n8n, GitHub, MCP servers, S3-compatible storage
- Skills & Extensions, reusable capability modules and a marketplace
- Guardrails and approvals, rules for what an agent may see or say, and a human yes before risky actions
- Runs, a step-by-step record of everything an agent did
- Governance, teams, RBAC, audit log, and usage analytics
- API & Webhooks, automate the platform itself
Quick Start
#quick-startGet started in minutes:
1. Create your account at app.oido.ai 2. Choose your plan (Free / Pro / Enterprise) 3. Configure your AI provider keys 4. Create your first agent 5. Connect tools and channels 6. Deploy and monitor
Free tier includes 1 agent and 2 AI providers. Upgrade to Pro for unlimited agents, all integrations, and priority support.
Agents
Agent Studio
#agentsCreate and manage AI agents with:
- Custom system prompts
- Model selection per agent
- Tool access control (allowlist/denylist)
- Skills attachment
- Subagent hierarchies
- MCP server connections
- YAML-based configuration
Agents can be assigned to projects, connected to chat channels, and equipped with tools from multiple sources.
Agent Marketplace
#marketplaceStart from a library of prebuilt agents, or build your own from scratch, then customize every part.
- Install a ready-made agent (support, sales, finance, ops) into your workspace in one click
- Or create an agent from scratch and shape it yourself
- Customize the model, system prompt, tools, and skills on any agent, prebuilt or your own
- Add subagents and delegation to the ones you install
- New agents keep arriving as the library grows
Prebuilt agents are starting points, not black boxes, everything is editable after you install it.
Workspace
#workspaceChat with your agents directly in the browser:
- Persistent sessions with full history
- File attachments and rich responses
- Per-session model and agent switching
- Command palette (Cmd+K) for quick navigation across the whole studio
AI Models
#providersOido is provider-agnostic: connect your own AI provider accounts and choose a model per agent.
Supported providers:
- OpenAI, Anthropic, Gemini, DeepSeek, NVIDIA, via API key
- Gemini and Qwen, via OAuth login
- OpenRouter, one key, many models
- llama.cpp server, self-hosted local models
- Custom LLM, any OpenAI-compatible endpoint
Mix providers across agents: run routine tasks on a cheap model and reserve frontier models for the work that needs them.
Safety and control
Human in the Loop
#human-in-the-loopGate consequential actions so an agent pauses for your approval before it acts.
- Put an approval gate on risky actions: payments, sends, deletes, publishing
- The agent pauses, asks for a decision, and only proceeds once you approve
- Approval requests are delivered to Slack or Telegram
- Set an approval destination per agent, and per subagent
- Denied actions stop the run cleanly, nothing happens without a yes
Approvals and guardrails do different jobs. An approval pauses an action and asks you. A guardrail blocks a message outright when it breaks a rule you wrote. Use approvals for actions that need judgment, and guardrails for content that should never pass.
Let agents move fast on routine work while you stay in control of the moments that matter.
Guardrails
#guardrailsGuardrails are rules your organization writes for what an agent may see or say. When a message breaks a rule, Oido blocks that turn and tells the sender which rule it matched. They are separate from Oido's own built-in protections: those are fixed, and guardrails are yours to define.
Find them under Settings, then Guardrails. Each rule has a name, a type, a direction, and a scope.
Five rule types:
- Keyword, blocks text containing any term on a list. Matching ignores case unless you turn that off
- Pattern, blocks text matching a regular expression
- Personal info, blocks text that looks like an email address, a phone number, or a social security number
- Category, a keyword list with a label, for example "medical_advice". The label shows in the block reason and does not change matching
- Written policy, you describe the rule in plain language, up to 2,000 characters, and Oido's built-in judge decides whether a message breaks it
Direction decides which side of the conversation a rule checks:
- Input, what people send to the agent
- Output, what the agent is about to send back
- Input and output, both
Scope decides who a rule applies to:
- Organization-wide, every agent in your workspace
- Agent-specific, only the agents you pick. An agent-specific rule can add to the organization's rules but never loosen them
You do not need to write a rule from scratch. Describe what you want to prevent and Oido drafts a rule for you to review, edit, and save. Rules can be switched on and off without deleting them.
How checks behave:
- Keyword, pattern, personal info, and category rules always run
- Written-policy rules call the judge, so they only run when you have configured at least one for that agent and direction
- If a rule cannot be evaluated because of an infrastructure error, the message is allowed through rather than blocking everyone. Use keyword, pattern, or personal info rules for anything that must never get through
- Blocks are recorded in the audit log
Start with one organization-wide rule for personal info, then add agent-specific rules where one agent handles something sensitive.
Runs
#runsEvery time an agent works, Oido records a run: when it started, how long it took, how many tokens it used, and whether it finished, failed, or was stopped.
Open Runs in the sidebar to see them all, and filter by outcome. Open one run to see its trajectory, every step the agent went through, in order:
- The system prompt and the message that started it
- Each model response, with its usage and timing
- Each tool call, with what was sent, what came back, and how long it took
- Each approval request and the answer it got
- Each subagent it handed work to
- Any point where the conversation was compacted to save context
Use the trajectory to find out why an agent did something, to check a slow run, or to see exactly where a failed run stopped. You can search within a run, collapse turns and calls, and switch the timeline between actual duration and equal-width steps.
A run that is still going has a Stop run button, so you can end a task that has gone the wrong way. Messages in the workspace also link to their run, so you can go from an answer straight to how it was produced.
Teams & RBAC
#teamsMulti-user support with role-based access control:
- Roles with granular permissions
- Team management
- User invitations
- Session isolation per user
Audit & Usage
#audit-usageFull visibility into what agents and users do:
- Audit log of every significant action across the platform, including messages blocked by a guardrail
- Usage analytics: tokens, turns, and cost per agent and per model
- Filter by user, agent, and time range
Operations
Channels
#channelsConnect agents to messaging platforms:
- Slack
- Telegram
- Discord
- DingTalk
Channels support:
- Sender policies (whitelist/any)
- Session scoping (user/global)
- Dispatch modes (sequential/parallel)
- Per-channel model and instruction overrides
- Pairing flow for device authorization
Support Desk
#supportBuilt-in AI-assisted customer support:
- Ticket management with statuses and assignment
- Quote creation and tracking
- Agents draft responses and triage incoming requests
- Full conversation history per ticket
Wiki
#wikiTeam knowledge base built into the platform:
- Markdown pages with slugs and linking
- Agents can read wiki content to answer questions
- Agents can create and update pages, keeping docs current automatically
Scheduled Prompts
#scheduled-promptsRun agents on a schedule:
- Cron-style recurring prompts
- Assign any agent to a schedule
- Results delivered to sessions or channels
Use cases: daily standup summaries, report generation, periodic monitoring, data syncs.
Projects & Tasks
#projectsBuilt-in Kanban board for project management:
- Custom columns per project
- Task creation with descriptions
- Agent assignment per task
- Auto-run on task move (agents execute tasks automatically)
- Reorderable columns and tasks
Integrations
MCP Protocol
#mcpNative Model Context Protocol support for extending agent capabilities:
- stdio transport (local processes)
- SSE transport (remote servers)
- Per-server environment variables
- OAuth configuration
- User/project scoping
MCP servers register tools that agents can use dynamically.
Skills & Extensions
#skillsSkills are reusable capability modules attached to agents:
- Built-in skills (DuckDuckGo search, Gmail, Google Calendar, n8n, web fetch)
- User-installed skills from SKILL.md files
- Extension marketplace support
Extensions add platform-level functionality:
- Install from git URLs, npm packages, local paths
- Configure via settings UI
- Enable/disable per deployment
n8n Integration
#n8nDeep integration with n8n workflow automation:
- Connect n8n instance via API
- Browse and trigger workflows
- View execution history
- Manage credentials
- Agents can create, update, list, and delete workflows
- Data table operations (create, read, upsert, delete rows)
Community node, for connecting an n8n you already run: Settings → Community Nodes → Install → n8n-nodes-oido
- Oido Trigger: start a workflow on an agent dispatch or an Oido event (agent run finished, channel message, ticket created)
- Oido: OCR a document, read or ingest a wiki page, embed, rerank, and respond back to the agent that dispatched the run
- Authenticates with an Oido API key
GitHub Integration
#githubConnect repositories to agents:
- Authenticate with GitHub PAT
- Register repositories for agent access
- Assign repos to specific agents
- Agents can read code, manage issues, and review PRs
File Storage
#storageS3-compatible storage via RustFS:
- File upload and download
- Bucket management
- Object listing
- Configurable storage backend
Agents can read and write files during execution.
Platform
API & Webhooks
#apiAutomate the platform itself:
- REST API (v1) with API key authentication
- Webhooks for reacting to platform events
- Hooks for customizing agent behavior
Deployment
#deploymentOido is a managed cloud service, no infrastructure to manage.
- Hosted and maintained by Oido Systems
- Enterprise-grade security and encryption
- 99.9% uptime SLA
- Automatic updates and backups
- SOC 2 compliance (in progress)