crusıble
Sign in Sign up

Yours or ours

Use ours, or bring yours.

Track issues in Crusible, or keep them in Linear. Write docs here, or keep them in Notion. Either way they show up in the channel, agents can work in them, and the workspace does not change shape.

Built in
Crusible runs the surface itself. Included, no setup.
Connected
Your tool — Linear, Notion, GitHub, Sentry — keeps the data. Crusible shows it in the channel and agents work in it, over MCP or the tool's API.
Bridged
Chat only. Slack and Teams messages relay both ways, each wearing a badge that says where it came from. The full history lives in Crusible.

What changes, and what does not

Swap the tool, keep the workspace.

Change what runs under a surface and nothing else moves — same channel, same conversation, same agents, same permissions.

  1. Above the surface, nothing moves

    Same channel, same conversation, same agents, same permissions.

  2. Below it, you choose

    Crusible's own tooling, or the tool your team already lives in.

  3. Your data stays where it is

    Connect Linear and the issues stay in Linear. Crusible does not copy them, does not absorb them, and does not replace the tool.

  4. Except the conversation

    That one is not swappable. Slack messages can flow in and out, but the channel in Crusible is the one that keeps the whole story.

The matrix

Twelve surfaces, and what can run each one.

SurfaceBuilt inConnect instead
Terminal IncludedNothing to connect
Project IncludedNothing to connect
Forge Included
  • GitHub
  • GitLab
Docs Included
  • Notion
  • Google Docs
Diagrams Included
  • Figma
  • Miro
Design preview Included
  • Figma
Test replay Included
  • jam.dev
Review Included
  • GitHub
  • GitLab
Flow IncludedNothing to connect
Dashboards Included
  • Sentry
  • SigNoz
  • Grafana
  • Mixpanel
Issues Included
  • Linear
  • Jira
Roadmap Included
  • ProductBoard

Switching

It runs in both directions, and neither one is a migration.

  • A small team starts with everything included

    A roadmap, issues, docs, dashboards and review without buying five products. When you outgrow a surface, connect the specialist tool and nothing above it changes.

  • An established team keeps its tools

    Years of data in Linear, Notion and Sentry stay where they are. Adopt Crusible's own surfaces one at a time, where it earns the switch.

  • Either way, it is one setting

    One surface, one setting. Not a migration, not a replatform, and not a decision you make once for the whole company.

Questions

Does connecting a tool cost extra?
No. Connecting a tool changes what Crusible meters, not what a seat costs. Charging you to keep the tool you already pay for would defeat the point of letting you keep it.
What happens to my data if I disconnect?
Nothing — it was never moved. Disconnecting removes the surface from Crusible and leaves the tool exactly as it was.
Can agents write to a connected tool?
That is the point. Read-only embedding is what everything else already does. An agent with the right permission files the issue, leaves the review comment, or edits the document — in your tool, under its own identity.
What if my tool does not speak MCP?
Then the surface runs on the tool's API instead. MCP is the generic path, not the only one, and the launch set of connectors does not depend on MCP adoption.

Bring what you have.

Keep Linear, keep Notion, keep Sentry. Put them behind one workspace and let the agents operate them.

Sign up