Platform
Six streams in. A company that explains itself out.
Bren reads chat, meetings, docs, project tools, code and manual reports, organises everything around your teams, people, projects and objectives, and turns it into briefs and answers for every altitude — with the permissions of the tool it came from.
Updates
Wins & failures
1 · Data streams
Reads where work already happens.
Least-privilege OAuth per tool. Admins decide which channels, projects, drives and repos are in scope, at connection and any time after.
| Stream | Tools | Direction | What Bren reads |
|---|---|---|---|
| Chat | Slack, Microsoft Teams, Gmail, Outlook | 2-way | Channels Bren is invited to, DMs with Bren, labelled email. Writes digests, alerts and answers back. |
| Meetings | Zoom, Google Meet, Slack Huddles, Google Calendar, Outlook Calendar | Incoming | Transcripts and recordings your tool already produces; calendar metadata for availability and leave. Bren never joins calls. |
| Documentation | Google Workspace, Microsoft 365, Notion, Confluence, Loom | Incoming | Documents shared with connected users; scoped drives, sites and spaces. |
| Project management | Jira, Notion, Trello, Airtable, Monday.com, ClickUp | 2-way | Projects, tasks, status changes, comments, dependencies. Writes summaries back, opt-in. |
| Code | GitHub | Incoming | PRs, reviews, commit messages, issues, releases. No source code stored. |
| Manual reporting | In-app forms, CSV, Google Sheets | Incoming | KR metrics that live nowhere else. |
2 · Company graph
Organised the way your company actually works.
Activity is attached to teams, people, projects, tasks and objectives — with time as the spine. That is what lets Bren answer "who owns the slipping dependency?" instead of just "where is the doc?"
Organisation → Teams → People
Every team has one parent and any number of children, and one lead. People have managers, reportees and optional mentor links. Imported from Slack/Teams groups, your directory, CSV or SCIM.
Projects → Tasks → Sub-tasks
Status, results and dependencies flow in from your project tool. Multiple owners per project. Dependencies across projects are tracked so slips propagate to the right people.
Objectives → Key Results
KRs link to the projects and tasks feeding them. Metrics come from integrations or manual reporting. Bren evaluates direction of travel and explains its reasoning with sources.
3 · Insights
Persona-based, cited, proactive.
Everything below is generated per person: an IC sees their team and dependencies; a VP sees momentum, risk and decisions needed across their org.
On demand
Ask Bren in the web app, Slack or Teams. Cited answers about projects, people, decisions, documents and goals.
Learn how it worksTime series
Daily digest for leads, weekly for managers and ICs, weekly leadership digest, monthly recap, quarterly / half-yearly / yearly snapshots, Year in Review.
Learn how it worksAlerts
Red flags, blockers, absent owners and slipping KRs — routed to the responsible manager with a suggested intervention.
Learn how it worksMonday Morning Brief
Last week, this week, what to block time for. Delivered before 9am local on your first working day.
Learn how it worksSecond Brain
The chronological company memory for onboarding, returning from leave, or inheriting a project.
Learn how it worksThink Out Loud
Refine a half-formed idea with company context; Bren asks the clarifying questions and drafts the brief.
Learn how it worksVisibility that mirrors reality: Participatory, Public, Selective.
Every project, task and objective has one of three visibility modes. Participatory (the default) shows it to owners, participants and their reporting managers. Public shows it to the whole company. Selective is Participatory plus the people or teams you add. Org admins can only make defaults stricter.
- Managers see direct and indirect reportees; peers see availability and shared work only
- A private Jira project or Slack channel stays private in Bren, whatever the mode
- Private notes are excluded from AI summaries by default and unreadable by admins
Mirrors Jira project and Slack channel permissions. Re-checked every sync.
Security & trust
Built to pass the security review before the pilot starts.
Bren is SOC 2 Type II audited and GDPR/CCPA compliant. Customer data is never used to train models. Permissions mirror every source tool.
- SOC 2 Type II (Security, Availability, Confidentiality). Report under NDA. ISO 27001 in progress.
- Encryption: AES-256 at rest, TLS 1.3 in transit. Private notes additionally envelope-encrypted per workspace.
- No training on your data. Model providers operate under zero-retention agreements. Bren never fine-tunes on customer content.
- Permission mirroring. Source-tool permissions re-checked on every sync (at most 15 minutes lag). Private channels stay private.
- Least-privilege OAuth. Admins scope Bren to specific channels, projects, drives and repos. Read-only mode available.
- Hosting: AWS, US by default; EU (Frankfurt) on Enterprise. Private-VPC deployment in your AWS account on Enterprise.
- Identity: Google/Microsoft sign-in (Team); SAML SSO (Business); SCIM provisioning and audit logs (Enterprise).
- Retention & deletion: export for 30 days after cancellation, then deletion; certificate on request. Custom retention and legal hold on Enterprise.
- Availability: 99.9% target on Business; contractual 99.9% SLA with credits on Enterprise. RPO 24h / RTO 8h (RPO 1h available on Enterprise).
- Not collected: keystrokes, screenshots, screen time, location, app usage, DMs between people, source code.
FAQ
Platform questions
Does Bren need admin access to our tools?
Slack, Teams, Google Workspace and Microsoft 365 apps need an admin to install, with least-privilege scopes listed per integration. Personal connections (your calendar, email, Zoom) are per user. Admins choose exactly which channels, projects, drives and repos Bren sees.
What if someone loses access to a channel or project in the source tool?
Bren re-checks permissions on every sync — at most 15 minutes lag — and removes their access to derived content on the next sync.
Does Bren record or join meetings?
No. It reads transcripts and recordings your meeting tool already produced (Zoom cloud recordings, Google Meet transcripts, Slack huddle notes). If recording is off, Bren only has calendar metadata.
How fresh is the data?
Event-driven where the tool supports webhooks (Slack, Teams, Jira, GitHub, Notion, Monday, ClickUp — seconds); polling every 15 minutes otherwise.
How does Bren avoid hallucinations?
Every claim in a digest or answer is grounded in a retrieved source and cited. If there is no source, Bren says so. Missing updates are reported as missing — never generated. Any segment can be expanded to the underlying messages, tickets and meetings.
Can we self-host?
There is no on-premises version. Enterprise offers a private-VPC deployment in your AWS account, plus US or EU data residency and customer-managed keys.
Which languages are supported?
English fully. Spanish, French, German and Portuguese in beta.
Is there an API?
API access and custom integrations are included in Enterprise. Team and Business use the 19 built-in integrations.
What happens to our data if we cancel?
Export in JSON/CSV for 30 days, then everything is deleted within 30 days of the end of the paid period. Deletion certificate on request.
See it on your org, not ours.
Start the 14-day trial and connect Slack or Teams in an afternoon — or book a 30-minute demo and we will map your teams, tools and rollout.