How it works
- App Store
- Google Play
- Zendesk
- Intercom
- Gong
- GitHub
- Bluesky
- SQL
- Webhooks
- + any REST or MCP
Your infrastructure
- Studio
- AI agents via MCP
- Slack
- Jira
- Linear
- Warehouse
obsei is one Python process (or container) that you run. Everything in the dashed box happens on your machines; data only leaves it for endpoints you configure and allow.
-
Collect. Sources fetch new feedback from app stores, helpdesks, call tools, warehouses, communities, files, webhooks or any REST or MCP server. Each record gets a stable id, so re-runs only process new or changed feedback.
-
Redact. Before anything is stored or sent to a model, emails, phones, cards, IBANs and national IDs for seven regions are replaced with tokens such as
<EMAIL>, optionally names too. Authors become salted pseudonyms. -
Classify. A local classifier, a decision model or your own chat model labels sentiment, intent, urgency and custom fields, each with a probability. Unsure answers go to a stronger model or to a human, and spam can be dropped here. Models only see redacted text, and the egress policy blocks public endpoints unless you allow them.
-
Theme. Records are embedded and grouped into stable themes with trends and near-duplicate detection. Themes from fewer than k people (default 5) are hidden.
-
Store. Everything lands in an encrypted DuckDB file.
obsei forget,obsei exportand the audit log cover access, erasure and retention. -
Act. Sinks deliver new feedback to Slack, Jira, Linear, GitHub, webhooks, Parquet or SQL. People use Studio and Slack; agents use the MCP server, where anything they propose waits for a person to approve it.
Who sees what
Section titled “Who sees what”| Who | Themes | Redacted quotes | Pseudonyms | Raw text |
|---|---|---|---|---|
| Studio viewer | ✓ | |||
| Studio analyst, Ask | ✓ | ✓ | ||
| AI agents (MCP) | ✓ | ✓ | ||
| Your model | ✓ | |||
| Sinks | ✓ | opt-in | ||
obsei export (CLI) |
✓ | ✓ |
Text is stored only after redaction; personal data the detectors miss (names without
obsei[names], addresses) is stored as written. Roles are set per token or through your SSO proxy;
see Server and access.
Run modes
Section titled “Run modes”| Command | Use |
|---|---|
obsei try |
Preview redacted records; nothing stored or sent |
obsei run |
One pass of every pipeline, from cron or CI |
obsei serve |
Scheduled pipelines, webhooks, Studio and MCP over HTTP |
obsei mcp |
MCP over stdio for a local agent |