Welcome to Bopsy
A workspace where your business runs AI agents over its own knowledge and tools.
Bopsy gives a business a workspace with AI agents that answer from the business's own files, and show the file the answer came from. You connect the places your knowledge already lives, choose which members and agents may use each part of it, and talk to the agents in the app or in the chat tools your team already uses.
The pieces
- Workspace. One per business. It has members with roles (owner, admin, member), and it runs on one machine of your choosing: a hosted machine that sleeps when idle, or a Linux server of your own.
- Agents. AI assistants that work for the workspace. An admin installs them, gives each one a job, and decides which knowledge and tools it may use. You bring your own AI provider key (Anthropic, OpenAI, or an OpenAI-compatible router).
- Knowledge. The searchable text Bopsy keeps for your files: documents you upload, recordings it transcribes, and folders synced from Google Drive. Knowledge is organised in areas, and an admin decides who can see each area.
- Channels. Where agents answer: the app, Telegram and Google Chat.
- Integrations. Business tools agents can read: Google Drive, HubSpot and GoHighLevel.
How an answer works
- Someone asks a question, in the app or in a channel.
- The agent searches the knowledge areas it is allowed to use.
- It answers from the passages it found and cites each one, so the reader can open the file.
If the knowledge doesn't support an answer, the agent says so rather than guessing.
Where your data goes
- Files you sync from Google Drive stay in Drive. Bopsy keeps the text it needs to search them, not the files, and its Drive access is read-only.
- Each workspace's agents run on that workspace's own machine. Your AI provider key is stored there, on the machine, not in the Bopsy control plane.
- What we keep, and for how long, is set out in the privacy policy.