Join the waitlist
Platform · Integrations

Plug in your stack.Tore takes it from there.

Connect your code, your error tracker, your issue tracker and the places your team talks. Tore reads what each one already knows, finds the cause in your code and prepares the fix for your engineer to approve.

Join the waitlistSee every integration

Tore opens soon. Join the waitlist and we'll email you the day you can start.

app.tore.ai/beacon-data/settings/connections
Example data
  • ConversationsBuilt inChats, emails and bug captures
  • CodeFiles, commits and deploys
  • Errors & metricsErrors, metrics and logs, read-only
  • Work trackingIssues, linked and kept in sync
  • ChatAlerts, replies and handoffs
  • CRM & help desksAccount context and past tickets
  • AI toolsYour inbox and investigations, over MCP
ToreWaiting for sources
Investigation· Beacon DataINV-311
  1. Error spike on report export, matched to 3 customer bug captures
    TypeError: cursor is null · 214 events in 20 min
    Priya · replayDan · consoleLena · network
  2. p95 latency jumped right after the 09:00 deploy
    /reports/export 380 ms → 2.4 s
  3. Root cause found in the code
    src/export/paginate.ts:57
    the page cursor is reset to null on every loop
  4. Fix written and tests run
    1 file, +1 −1 · 48 tests passed
Pull request prepared · waiting for your approval

Every tool already knows something.Nobody retypes it any more.

Each connection removes a step where a person copies something a machine already had.

Support and engineering see the same work

A conversation becomes a linked Linear or Jira issue, and the two stay in sync. Never duplicated.

Paste the Sentry link into a ticket by hand

Work the queue from Slack

Get notified, reply and act without a second tab open all day.

Keep the help desk open in another tab

The investigation reads your real code

Connect GitHub and every bug is traced to the file, the line and the commit.

Walk an engineer through the bug first

Switch without losing history

Import your conversations from Zendesk or Intercom and keep every customer's past.

Start over with an empty inbox

Everything it connects to,and what it does with each.

Grouped by the job the connection does. Pick a group to narrow the list.

  • Chat widget Conversations

    Built in. Customers chat from your app, and a bug report arrives with the replay, console and network log attached.

  • Email Conversations

    Forward your support address in. Replies land on the right thread and attachments are scanned.

  • GitHub Code

    Investigations read the real file and commit. The fix arrives as a pull request for your engineer to approve.

  • GitLab Code

    The same investigation on your GitLab projects, with the fix prepared as a merge request.

  • Bitbucket Code

    Bitbucket repositories are read the same way, so the cause is found in your actual code.

  • Vercel Code

    Deploys line up against new errors, so a regression points straight at the release that caused it.

  • Azure DevOps Code

    Azure Repos are read the same way, so the cause is found in the code you actually ship.

  • CircleCI Code

    Failed builds and test runs sit next to the errors they line up with.

  • Sentry Errors & metrics

    Errors group by fingerprint and can open an investigation on their own, before anyone writes in.

  • Datadog Errors & metrics

    Use the error tracker you already run. Datadog errors feed the same grouping and investigations.

  • Grafana Errors & metrics

    Metrics and logs pulled read-only as evidence, without giving anyone shell access.

  • Rollbar Errors & metrics

    Rollbar errors feed the same grouping and investigations as everything else.

  • Bugsnag Errors & metrics

    Keep the crash reporting you already run. Bugsnag errors open investigations too.

  • Linear Work tracking

    A conversation becomes a linked issue without retyping, and the two stay in sync.

  • Jira Work tracking

    Bugs land in Jira with the evidence attached. Closing the issue updates the customer.

  • ClickUp Work tracking

    Turn a conversation into a ClickUp task with the evidence attached, no retyping.

  • Asana Work tracking

    Bugs become Asana tasks linked to the conversation they came from.

  • Slack Chat

    Get notified, reply to customers and act on the queue without leaving Slack.

  • Microsoft Teams Chat

    The queue and its alerts reach your team in the channels they already use.

  • Discord Chat

    Alerts and handoffs post to your server, so nobody has to watch a second tab.

  • HubSpot CRM & help desks

    Customer context from HubSpot arrives with the conversation, so nobody goes looking for it.

  • Salesforce CRM & help desks

    Account details sit next to every conversation, pulled from the records you already keep.

  • Zendesk CRM & help desks

    Import your Zendesk history, so switching does not mean starting from an empty inbox.

  • Intercom CRM & help desks

    Bring your Intercom conversations across and keep every customer's history.

  • Attio CRM & help desks

    Account details from Attio arrive with the conversation, so nobody goes looking.

  • Front CRM & help desks

    Bring your Front conversations across and keep every customer's history.

  • Claude AI tools

    Tore's MCP server puts your inbox and investigations inside Claude. Ask, and it answers from Tore.

  • Cursor AI tools

    Pull a bug's evidence and investigation into Cursor through the MCP server while you code.

  • Any MCP client AI tools

    Any AI tool that speaks MCP can read your inbox and investigations.

Something missing? Use the API and webhooks to connect anything else.

One bug, every tool it touches.All of them kept in step.

Across your stack

It moves between your tools so your team does not have to.

The error arrives from Sentry. Tore links it to an issue in Linear, tells the team in Slack and prepares the fix on GitHub. Each tool shows the same story, in the place people already look.

  • Errors open an investigation on their own, before the first customer complains
  • Linear and Jira issues stay linked and in sync with the conversation
  • The fix waits on GitHub for your engineer's approval by default
app.tore.ai/beacon-data/INV-311
Example data
Sentrybeacon/app · production
TypeError: cursor is nullat nextPage · src/export/paginate.ts:57
214 events38 users3 customer reports matched
LinearEngineering · synced with Tore
ENG-412Report export stops after the first page
Status
In progress
Assignee
Alex
Linked
3 conversationsSentry error
Evidence
replay · console · network
Slack#eng-support
Tore app · 09:26

ENG-412: cause found at paginate.ts:57. 3 customers affected. A fix is ready for review.

Alex 09:27

Looking now.

GitHubbeacon/app · pull request #1287
fix(export): keep the cursor between pagesWaiting for approval
src/export/paginate.ts +1 −1
57- cursor = null
57+ cursor = res.nextCursor
48 tests passedApproveApproved by Alex
Reading Sentry

Slack

Work the queue without a second tab.

New conversations, handoffs and fixes waiting for review post to the channel you choose. Reply to the customer or take the conversation from the message itself.

  • Notifications for the conversations and fixes that need a person
  • A reply from Slack reaches the customer by email or chat
  • Teams and Discord get the same alerts and handoffs
#support · Slack
Example data
Tore app · 14:02

Maya at Northwind can't invite teammates. I'm not confident on this one, so I've drafted a reply for a person to check.

Maya Northwind · via chat

The invite button is greyed out for me.

Draft reply

Invites need the Admin role. Your workspace owner, Tom, can switch it on under Settings, Members.

Hana 14:04

Sent. Reply delivered to Maya in chat

Linear and Jira

Support and engineering, looking at the same issue.

A bug from support becomes a linked issue with the replay, console and network log attached. When the issue moves, the conversation knows. When it closes, the people who reported it are told.

  • No retyping between the inbox and the tracker
  • Repeat reports link to the same issue instead of new ones
  • Reporters hear back when it is fixed, without anyone remembering who asked
app.tore.ai/beacon-data/issues/ISS-311
Example data
Tore issueExport stops after the first page
Linear · ENG-412Report export stops after the first pageevidence attached
  • Issue created and linked · 3 conversations
  • Status In progress · Alex
  • Status Done · synced to Tore
  • Priya, Dan and Lena told it is fixed

Connect in minutes.Revoke in one click.

You own every connection. You can see what Tore can reach and take it back whenever you like.

You stay in control

It proposes, you merge, and it is yours to switch off.

GitHub, Sentry, Linear, Slack and email connect from one settings page. The GitHub app reads your repository and opens proposed fixes as pull requests on its own branches. It never merges or pushes to your main branch, and one click takes that access away again.

  • Fix pull requests on its own branches, never merged by Tore
  • GitHub access revocable in one click
  • Your code is never used to train a model
  • Works with the stack you already run, connected in minutes
Settings · Connections
Example data
  • GitHub appbeacon/app, beacon/webRevoke accessAccess revoked Code: never mergesNo shell or cloud access
  • Sentryapi-prod · 3 projectsConnected
  • LinearEngineering teamConnected
  • Slack#support, #eng-supportConnected
GitHub access revoked. Tore can no longer read beacon/app.
Your code is never used to train a model.

No connector for it yet?Build your own in an afternoon.

Webhooks, a scoped API and an MCP server, so Tore reaches whatever you already run.

API, webhooks and MCP

Automate anything in Tore from your own code.

Webhooks push events out the moment they happen. The API reads and writes conversations, issues and more. The MCP server puts your inbox and investigations inside Claude, Cursor and other AI tools.

  • Signed, retried webhooks with a delivery log for every attempt
  • Scoped API keys with live and test modes, and safe rotation
  • Public read and write API for anything you want to automate
  • MCP server for Claude, Cursor and any other MCP client
Read about the API and webhooks →
Developers
Example data 
// POST https://hooks.northwind.dev/tore
x-tore-signature: sha256=9f2c…e41a
{ "type": "investigation.fix_ready",
  "issue": "ISS-311", "reporters": 3 }
  • 503attempt 1 · retrying14:02:07
  • 200attempt 2 · delivered · 84 ms14:02:39
  • 200conversation.closed · delivered · 61 ms14:05:12
1 clickto revoke the GitHub app's access to your code
0lines of your code used to train a model
6scopes on API keys, with separate live and test modes
3retries for every webhook, each attempt in the delivery log

Keep exploring.

PlatformAPI and webhooksSigned webhooks, scoped keys and the public API.See how → SupportSlackNotifications, replies and actions from Slack.See how → Capture & fixError monitoringErrors that open their own investigation.See how →

Connect your first toolbefore your coffee cools.

Start with GitHub and your support inbox. Add Sentry, Linear and Slack when you are ready.

You're on the list. We'll email you the day you can start.

Get early access when Tore opens. No spam.