Slack
Mention the agent in any channel. It picks up context from threads, reads files, replies in line.
- Public + private channels
- Thread-aware replies
- File + image attachments
- Slash commands and shortcuts
AI coworkers that live in your Slack and WhatsApp, run real code in their own compute environment, connect to 3,000+ tools, and ship the work — not a chat reply.
Most AI tools explain the work.
Openrift does the work.
May closed up 18% MoM — driven by 4 mid-market closes in SG/MY. Burn held flat despite the ops hire. Pipeline weighted at SGD 1.2M with three enterprise in legal review. Runway shortens by a month from April; conservative new-deals model puts it back at 16 by July.
Agents are not a tab you open. They live where your team already talks. You mention them, they work. They follow threads, ask clarifying questions, hand back finished outputs in the same channel.
Mention the agent in any channel. It picks up context from threads, reads files, replies in line.
Half your team runs on WhatsApp. Agents reply in business groups, accept media, send PDFs back.
For regulated or enterprise environments. Same agent, same context, surfaces in Teams channels.
Half your SEA team
lives on WhatsApp.
Founders on the road. Ops leads in the warehouse. Vendors who never installed Slack. Agents reach them where they already are — business groups, DMs, voice notes, document replies.
Not a chatbot
with a typing cursor.
Each Openrift agent runs in a dedicated cloud sandbox. It executes real code. Hits your tools through real APIs. Renders real outputs. The Slack reply is the surface — the work happens underneath.
Workspace boundary is a hard technical boundary. Your compute, your data, your secrets. Never mixed.
Every engagement gets a dedicated compute environment. No data crosses tenants.
Python, Node, shell. Installs packages. Runs SQL. Hits APIs. Builds and ships artefacts.
Logs into web UIs when an API doesn't exist. Scrapes, fills forms, downloads files.
Writes PDFs, spreadsheets, charts. Persists working state across sessions.
Spins up internal tools and dashboards. Returns a live URL your team can visit.
Audits, exports, report builds that run minutes to hours. Pings back when ready.
If your stack has it, agents probably can too. Native integrations for the big platforms; custom connectors built during deploy for the regional, niche, or internal systems.
Reads the channels you invite it into. Picks up vocabulary, names, recurring questions.
Each repeatable workflow becomes a documented skill the agent can re-run on command.
Decisions, naming, conventions — captured. Searchable. Auditable.
Multi-step procedures with confirmation gates. Versioned. You can read what it will do.
Agents are eager. We make sure they ask. Anything irreversible — external sends, prod deploys, money moves — pauses for human confirmation. You always know what happened, and you can stop it instantly.
Before sending external emails, deploying to prod, moving money, agents stop and ask.
Every action taken, every tool call, every output rendered. Searchable forever.
One command pauses the agent. One disconnects it from a tool. No tickets, no waiting.
Define what the agent can see and do, channel by channel. Default-deny posture.
Hard tenant boundary. Your data never crosses into another engagement. Period.
Full workspace wipe on request. Removes stored data, learned context, integration history.
One week with your team. Map the workflows that hurt. Quote the deploy.
Bespoke agents in your Slack and WhatsApp. Tools connected. First workflows live.
Monthly retainer. Tune. Add workflows. Widen the rift.
Thirty-minute call. We look at your ops, decide if there's a fit, and quote the discovery.