Give the work to a bot. Keep the decisions.
Opisense Bot runs long-lived AI teammates. Each has a job, its own computer and the apps it needs, and stops for approval where you draw the line. Run it in Opisense Cloud or on your own servers.
Reach them where work happens
Mention a bot in Slack or message it from your phone. It replies in the thread and keeps the context. Every bot is also in the web, desktop and mobile apps.
- SlackCloud and self-hosted
- TelegramSelf-hosted
- WhatsAppSelf-hosted
- iMessage & SMSSelf-hosted
More than a chat window
Each bot has its own computer, the apps it needs and a memory of how your team works.
Works in your apps
Connect Gmail, GitHub, Notion, HubSpot and more, or any MCP or OpenAPI tool source.
Learns by watching
Show a task once on its computer. The bot saves the steps as a reusable skill.
Remembers what matters
Bots keep what they learn about people, customers and preferences, and share it with the team.
Starts on its own
On a schedule, a webhook, a GitHub event or a change it watches.
Hands off work
Bots delegate to each other or to short-lived helpers, and work together in groups.
Calls when it needs you
When a decision can’t wait, the bot calls you in the app so you can talk it through.
One bot per job
Start from a role, then give it instructions, tools and a model. Each bot keeps its own history, memory and computer, so work picks up where it left off.
Account Manager. Prepares renewals, tracks usage and flags accounts at risk.
Account Manager
Prepares renewals, tracks usage and flags accounts at risk.
Works in
- Gmail
- HubSpot
- Drive
Autonomy you can account for
Bots act on real systems, so the boundaries are explicit: what needs approval, where work runs and who did what.
Approval where it matters
Choose which actions need a person to sign off. The bot waits, then continues once approved.
A computer per bot
Each bot works in an isolated computer with a browser, terminal and files. Shared team computers are opt-in.
Every action on record
Tool calls, approvals and messages are logged, so you can see who did what and when.
Run it our way or yours
The same bots and apps either way. Choose who operates the infrastructure.
Opisense Cloud
BetaWe run the servers, bot computers, upgrades and backups. Your team signs in and gives the first bot a job.
- Managed bot computers, nothing to install
- Web, desktop, iPhone and Android apps
- Slack and app integrations
- Your model provider, with an API key or supported subscription
Self-hosted
Run the full stack on servers you control. Data, bot files and the audit log stay inside your deployment.
- Docker Compose install on a Linux server or Mac
- Any model provider, including local models
- Docker computers by default, or a remote provider
- Telegram, WhatsApp and iMessage channels
- Deployment support from the Opisense team
| Compare | Opisense Cloud | Self-hosted |
|---|---|---|
| Operated by | Opisense | Your team, with Opisense support |
| Data stored in | Opisense Cloud | Your deployment |
| Models | Your API keys or a supported subscription | Any provider, OpenAI-compatible endpoint or local model |
| Bot computers | Managed by Opisense | Docker, E2B, Daytona, CreateOS or Boat |
| Channels | Slack | Slack, Telegram, WhatsApp, iMessage & SMS |
| Apps | Web, desktop, iPhone, Android | Web, desktop, iPhone, Android |
Opisense Bot docs
Set up bots, channels and approvals step by step.