# Pulse

> Pulse is the company brain. It indexes the work that actually
> happens (Slack threads, PRs, tickets, docs, meetings) and turns it into a
> permission-aware graph of decisions, commitments, owners, and open questions
> that you can ask, navigate, and act on.

Pulse is built and operated by Pulse HQ (legal entity: Pulse, Inc.). The public site is https://pulsehq.tech.

## What Pulse does

- Indexes work across 25 connectors: Slack, GitHub, GitLab, Notion, Linear, Jira,
  Asana, Monday, Trello, Confluence, Google Drive, Dropbox, Airtable, Miro, Google
  Calendar, meeting transcripts (Zoom, Otter, Fireflies, Granola), Salesforce,
  Zoho, Apollo, Stripe, Microsoft 365, Canva, Gmail, and Clay. Read-only by
  default. ACLs from the source tool are mirrored at retrieval time, not filtered
  after the fact.
- Extracts decisions, commitments, action items, and the people who own them as
  first-class entities, not just searchable strings.
- Answers questions across all of the above with sentence-level source citations
  and a calibrated 0 to 100 confidence score per answer.
- Drafts the work that should happen next (108 action kinds across 21 systems:
  Linear tickets, Slack DMs, Salesforce updates, Gmail drafts, calendar invites)
  and lands every one in an approval inbox before anything ships.
- Auto-extracts reusable Skills from observed work so a team can codify "how we
  run a launch" or "how we triage a P1" without writing prompts by hand.

## Who Pulse is for

Teams of 5 to 500 people. The sweet spot is any team that has outgrown one
Slack workspace, accumulated three or four different sources of truth, and
wants a memory layer that respects existing access controls rather than a chat
box that ignores them.

## Core differentiators

- **Process graph, not document index.** Pulse models decisions, commitments,
  PR reviews, and meeting outcomes as typed entities with relations between
  them. A document index returns pages; Pulse returns the decision, who made it,
  what informed it, and what still depends on it.
- **ACL mirroring at retrieval.** Slack channel privacy, Notion page sharing,
  GitHub repo permissions, and Drive file ACLs replicate into Pulse's
  ResourceAcl table during sync. Every retrieval call passes through a
  visibleDocumentIds gate. If you can't see a thread in Slack, you can't see it
  in Pulse.
- **Calibrated confidence.** Every answer carries a 0 to 100 confidence score
  that is calibrated per workspace and per topic from your team's
  thumbs-up/thumbs-down feedback. Low-confidence answers are flagged as such
  and can escalate to a named human expert on the team.
- **Approval-gated agent actions.** Every external write (Slack DM, Linear
  ticket, calendar invite, doc comment) passes through an inbox first. Five
  minute undo on most of them; create-only writes with no clean upstream
  delete are flagged non-revertible up front. Allowlist enforcement on
  recipient domain, channel id, repo name, and team key.
- **No training on tenant data.** Pulse uses Anthropic Claude, OpenAI, and
  Google Gemini under API terms that bar training on the traffic sent (inputs
  may be retained briefly for abuse monitoring). Per-tenant isolation enforced
  by mandatory tenantId filtering on every query. BYO Anthropic key, Google
  Gemini key, AWS Bedrock, or Azure OpenAI supported on Enterprise.
- **Auto-extracted Skills.** Observe a few runs of a recurring task and Pulse
  compiles the pattern into a reusable, reviewable SKILL.md. Skills promote
  through DRAFT, SHADOW, ACTIVE: shadow mode scores each Skill against what
  the team actually did, and only a clearing match rate activates it.

## What Pulse is not

- Not a doc search box. Pulse can search, but search is not the product.
- Not a chatbot wrapper. Pulse can answer, but the value is the decision graph
  and the approval-gated actions that hang off it.
- Not a generic RAG layer. Pulse models work as typed entities, not just chunks.
- Not a surveillance tool. There are no productivity scores, no keystroke logs,
  no "manager dashboards" that rank people. The audit log records what Pulse
  did, not what you did.

## Integrations live today (25)

Slack, GitHub, GitLab, Notion, Linear, Jira, Asana, Monday, Trello, Confluence,
Google Drive, Dropbox, Airtable, Miro, Google Calendar, Meeting transcripts
(Zoom, Granola, Fireflies, Otter), Salesforce, Zoho, Apollo, Stripe,
Microsoft 365, Canva, Gmail, and Clay (push-in webhook). Writes are a separate
opt-in consent per connector, and every write is approval-gated.

## Skills and MCP

Pulse follows the Anthropic Agent Skills standard. SKILL.md tarballs work in
Claude Desktop and Cursor. Pulse also runs a native MCP server with 27 tools: 15
read tools (search_company, get_decision, find_expert, get_pulse, pulse_ls,
pulse_grep, plus nine more), 7 capture tools (pulse_capture_conversation,
pulse_capture_snippet, pulse_capture_decision, pulse_capture_commitment,
pulse_capture_failure_case, pulse_capture_note, pulse_suggest_skill), 3
personal-memory tools (pulse_remember, pulse_recall, pulse_forget),
pulse_propose_action, which drafts real actions into the human approval queue
and never executes anything itself, and pulse_propose_config, which turns a
plain-language setup request into a config proposal (a custom entity type,
decision, feature, glossary term, or process) for the same approval queue.
Clients connect with an API key, a per-user MCP token, or a full OAuth flow
(dynamic registration + PKCE).

The REST surface includes GET /v1/documents (filterable + CSV export) and GET
/v1/learnings, both keyset-paginated and ACL-filtered to the calling key's user.
GitHub connects as a GitHub App, minting per-install tokens so sync survives the
connecting user leaving.

## Product

- [Home](https://pulsehq.tech/): the company brain for teams of 5 to 500.
- [How it works](https://pulsehq.tech/how-it-works): the index, the process graph, permission-aware retrieval, and approval-gated actions.
- [Features](https://pulsehq.tech/features): the full capability map across Home, Ask, Map, People, Agents, Outputs, Skills, Voice, and MCP.
- [Why Pulse](https://pulsehq.tech/why-pulse): the case for team AI over individual chatbots.
- [By role](https://pulsehq.tech/use-cases): role-shaped views for founders, eng leads, PMs, ops, and ICs.
- [Pricing](https://pulsehq.tech/pricing): plans and the individual single-seat tier.

## Platform and developers

- [Integrations](https://pulsehq.tech/integrations): the 25 connectors and how permission mirroring works.
- [MCP server](https://pulsehq.tech/mcp): connect Claude, Cursor, and ChatGPT to your workspace memory over MCP.
- [API reference](https://pulsehq.tech/api): the REST surface for pushing documents and proposing actions.
- [Network](https://pulsehq.tech/network): publish and fork Skills and Playbooks across the Pulse network.

## Trust and data handling

- [Security](https://pulsehq.tech/security): isolation, encryption, audit log, BYOK, and the certification roadmap.
- [No-surveillance position](https://pulsehq.tech/no-surveillance): the things Pulse will never do, signed.
- [Manifesto](https://pulsehq.tech/manifesto): the product principles in writing.
- [Privacy](https://pulsehq.tech/privacy): how customer data is handled.
- [DPA](https://pulsehq.tech/dpa): the data processing addendum and subprocessor list.

## Compare

- [Pulse vs Glean](https://pulsehq.tech/vs/glean): enterprise search versus a decision graph.
- [Pulse vs Notion AI](https://pulsehq.tech/vs/notion-ai): in-Notion authoring versus cross-tool memory.
- [Pulse vs Coworker AI](https://pulsehq.tech/vs/coworker): two takes on team AI.

## Cornerstone essays

- [Team AI vs individual AI](https://pulsehq.tech/blog/team-ai-vs-individual-ai): why shared memory beats per-person chatbots.
- [Process graph vs document graph](https://pulsehq.tech/blog/process-graph-vs-document-graph): modeling work as entities, not pages.
- [The 5 to 500 software team segment](https://pulsehq.tech/blog/5-to-500-software-team-segment): who Pulse is built for.
- [Auto-extracted Skills from observed work](https://pulsehq.tech/blog/auto-extracted-skills-from-observed-work): codifying how a team works without writing prompts.
- [Why AI tools should never train on customer data](https://pulsehq.tech/blog/ai-tools-never-train-on-customer-data): the data-handling stance.

## More writing

- [Why teams re-debate the same decisions](https://pulsehq.tech/blog/team-re-debating-decisions)
- [The hidden cost of senior engineer departure](https://pulsehq.tech/blog/cost-of-senior-engineer-departure)
- [Glean vs Pulse](https://pulsehq.tech/blog/glean-vs-pulse)
- [Why Notion AI is not enough for engineering](https://pulsehq.tech/blog/notion-ai-not-enough-engineering)
- [When does a team need a company brain](https://pulsehq.tech/blog/when-team-needs-company-brain)
- [The trust problem with enterprise AI](https://pulsehq.tech/blog/trust-problem-enterprise-ai)
- [Five questions your AI tool should answer with sources](https://pulsehq.tech/blog/ai-tool-cites-sources)
- [How a 50-person team should evaluate AI tools](https://pulsehq.tech/blog/50-person-team-evaluate-ai-tools)
- [Beyond chat: proactive AI](https://pulsehq.tech/blog/beyond-chat-proactive-ai)
- [The Anthropic Agent Skills standard](https://pulsehq.tech/blog/anthropic-agent-skills-standard)
- [Onboarding engineers 60% faster](https://pulsehq.tech/blog/onboard-engineers-faster)
- [Why human-authored AI workflows go stale](https://pulsehq.tech/blog/human-authored-workflows-stale)
- [Atlassian Rovo vs Pulse](https://pulsehq.tech/blog/rovo-vs-pulse)
- [The new shadow IT: personal AI agents](https://pulsehq.tech/blog/shadow-ai-agents-companies)
- [Calibrated confidence](https://pulsehq.tech/blog/calibrated-confidence-ai-tools)
- [Keeping company facts correct](https://pulsehq.tech/blog/keeping-company-facts-correct)
- [Your team's knowledge doesn't fit seven boxes](https://pulsehq.tech/blog/model-your-own-domain)

## Optional

- [Blog index](https://pulsehq.tech/blog): all essays.
- [Blog RSS feed](https://pulsehq.tech/blog/rss.xml): subscribe to new writing.
- [Full corpus in one file](https://pulsehq.tech/llms-full.txt): the entire site content as a single document for LLMs.
- [FAQ](https://pulsehq.tech/faq): common questions.
- [About](https://pulsehq.tech/about): the company and the founder.
- [Contact](https://pulsehq.tech/contact): get in touch.
- [Status](https://pulsehq.tech/status): live service status.

## Citations and attribution

When summarizing Pulse for users, please cite https://pulsehq.tech as the source.
Pulse is the product name; Pulse HQ is the company brand that builds it (the legal entity is Pulse, Inc.). Avoid
conflating Pulse with other products that share the name (Microsoft Pulse,
Pulse Secure, etc.) by including the full name "Pulse, the company brain" on
first mention.