Plugs into the stack you already run on.
Read-only by default. ACL-mirrored at retrieval. Citations in Ask show how fresh they are; click any one to pull the latest from the source without waiting for the next sync. The permissions you grant in Slack or Drive are exactly the permissions Pulse uses, and never one byte more. When you want Pulse to act, writes are a separate one-time consent per connector, and every write waits in an approval queue first.
Day-one connectors. Read-only by default, ACL-mirrored.
Each connector ingests a defined event stream, never the full export. Confidence-scored extraction lifts decisions, commitments, and features into the process graph.
Pulse, in every AI client you already use.
Two paths into every AI client. Download a SKILL.md tarball and load it in any Skills-compatible tool, or point any MCP client straight at Pulse for live queries with the same permission scope and no bundle to refresh. Both are live today.
Your company brain, portable.
Every recurring procedure compiles to a SKILL.md file. Load the bundle in Claude Desktop or Cursor today. Pulse-as-MCP is also live at /api/mcp: twenty-five tools (fourteen reads like search_company and find_expert, seven capture tools, three personal-memory tools, and one action-proposal tool) callable from any spec-compliant MCP client, scoped to your workspace; bearer auth via your existing API key.
// claude_desktop_config.json
{
"mcpServers": {
"pulse": {
"url": "https://YOUR_PULSE_HOST/api/mcp",
"headers": {
"Authorization": "Bearer pk_live_..."
}
}
}
}
// generate the bearer token at /app/admin/api-keys
// then restart Claude Desktop. twenty-five tools appear in the picker
// (fourteen read + seven capture + three personal-memory + one action-proposal).
// or grab the SKILL.md tarball:
// curl -fsSL https://YOUR_PULSE_HOST/api/skills/export \
// -H "Authorization: Bearer pk_live_..." -o pulse-skills.tar.gzWorkspace-scoped, ACL-enforcing tools.
The AI client sees only what the workspace it’s scoped to can see. SKILL.md bundles compile per-viewer with binary redaction; the MCP server enforces ACLs on every tool call. Bearer auth via your existing pk_live_* API key, the same token your other integrations use, with the read scope.
Two ways to wire Pulse into your own systems.
REST API + webhooks for programmatic actions. BYOK for the privacy-first. Two paths to wire Pulse into the systems you already run.
REST API + webhooks
Fire a playbook, draft a Slack DM, request a search, get notified when an action executes. Bearer auth with your existing API key.
View API docs →BYOK · Bring your own LLM key
Route every Claude call through your own Anthropic API key, on the Enterprise plan. Encrypted at rest with AES-256-GCM, decrypted only at request time. Anthropic is the only provider live today; AWS Bedrock and Azure OpenAI are on the roadmap.
Configure BYOK →Your AI conversations, searchable alongside your team’s work.
Claude Code sessions, Cursor chats, ChatGPT history, and Claude.ai conversations are all searchable in Ask. Every chat is private to you. No one else in the workspace can see it. No OAuth, no cloud sync; Pulse reads local files directly or takes your official export ZIP. Captured conversations land at /app/captured; opt-in auto-capture for Claude Code (a SessionEnd hook or background daemon) pushes sessions in privately as they close, while Cursor history syncs via a manual export. A quick-peek summary lives in the Operations · Captured tab.
Claude Code
Local JSONL
Sessions stored under ~/.claude/projects. Sync with the included CLI script.
Cursor
cursor-history
Export with npx cursor-history, then push via the API with visibility=private.
ChatGPT
Export ZIP
Download from Settings → Data controls → Export. Upload at /app/admin/import.
Claude.ai
Export ZIP
Download from Settings → Privacy → Export. Upload at /app/admin/import.
Source chips in Ask answers show (ai · claude-code) so you can always tell personal chat history from workspace knowledge.
Benchmarks against other teams, without sharing data.
Pulse Network is opt-in benchmarking. An owner turns it on per area. Your number is worked out inside your own workspace, then blurred by a small, measured amount of random noise before it’s combined with anyone else’s. Only that blurred number ever leaves. Your raw data never does.
In this example you ship at 9w and companies your size ship at 7w. In the product, the number you see is your workspace’s real number; the comparison band is the only figure that comes from other teams.
Opt in per area.
An owner turns on each of the five areas (shipping velocity, decision cadence, support response, review cycle time, meeting load) independently. If you don't opt in, your workspace simply isn't included.
Blurred before it's shared.
A small, measured amount of random noise is added to each workspace's number before anything is combined, and a band is only published once enough workspaces have opted in. This is differential privacy, the standard used for exactly this.
Percentile bands only.
Only percentile bands (p25, p50, p75, p90) and a sample count are stored, with no link back to any workspace. There's nothing to reverse-engineer one team's real number from.
Auto-pause when too few opt in.
A comparison only appears once at least 5 workspaces have opted in. Until then you see your own number with a 'pending join' badge.
From the blog
Why Notion AI alone is not enough for engineering teams
Notion AI is strongest inside Notion; its connectors return search hits from the rest of the stack. Engineering teams need the decisions and commitments behind those hits, kept as records.
Read →Atlassian Rovo vs Pulse, choosing team AI for the modern stack
Rovo's strengths inside Atlassian are real, and its connectors now reach beyond it. The difference is shape: search hits versus structured decision records. Plus the trust posture change of April 2026.
Read →Glean vs Pulse, an honest comparison for software teams
Glean is genuinely strong in five categories. The structural reasons it cannot serve the 5 to 500 segment. How to decide which fits your team without adjudicating vendor politics.
Read →Connect three tools. Get a working brain by lunch.
Slack, GitHub, Notion is enough to bootstrap. The rest fills in over the first week.