The answer is never
in another tab.
Order status, account history, an open deal, a monitoring alert, a linked bug — Salamandr fetches it live from the systems you already run and puts it beside the ticket the moment an agent opens it. Nothing copied in, nothing left to go stale.
Before / After
One glance instead of six tabs
A support agent working a hard ticket used to keep half a dozen tabs open — the store admin, the CRM, the monitoring console, the issue tracker — copying numbers back and forth by hand while the customer waited. The Context Rail collapses all of it into one column that opens with the ticket.
What shows up in the rail
Eight kinds of context, one place to read them
Each panel only renders when there's something to show — no empty box taking up space on a tenant that hasn't connected that system.
Live orders, refunds & coupons
Pull the exact order behind a ticket from WooCommerce or Shopify — line items, tracking, how much has already been refunded — fetched the moment the agent needs it, never synced into a second database.
Who this customer is to the business
HubSpot's account owner, whether they're mid-deal, a VIP flag your team defines — so a support reply and a sales relationship stop working from different facts.
What's actually broken
Zabbix's open problems for that customer's own host group, acknowledged with one click from the ticket — before anyone has to ask "is something down on our end?"
Link the bug, not just the ticket
Search, link, or file the underlying issue in Jira, GitHub, Linear, or Redmine without leaving the conversation, and watch its status change as engineering works it.
Hand off without losing the thread
Open a card in Trello or a task in Asana on whichever board another team actually works from, tied back to the ticket that started it.
Get the file without the email dance
Send a tokenized upload link straight into your own Dropbox, Box, Drive, OneDrive, S3-compatible bucket, or SFTP server — no more 25MB attachments split across five messages.
A drafted answer, cited
Ask a question in plain language and get a reply drafted from the tenant's own uploaded docs, embedded and matched entirely by a local Ollama instance — nothing sent to a third-party API to answer it.
Whatever you actually run
The plugin host and SDK are free in every edition. Wire up your own ERP, internal admin tool, or field-service system the same way the 15 built-in connectors work.
How it stays honest
Fetched live, never copied
Every panel above is fetched on demand, the moment an agent opens the ticket — never synced into a background job, never cached into a second copy of a system you already run and already secure. Close the ticket and the rail forgets it ever asked.
Each connector runs sandboxed, declares exactly what it's allowed to touch, and authenticates with your own API keys — never a shared vendor app sitting between you and your data. That's also why it's auditable rather than promised: the plugin host and the SDKs it runs are code you can read, not a claim you take on faith.
Ready to see it on your own stack?
Community ships the plugin host and SDK free — write your own connector today. Enterprise adds the 15 ready-made ones, kept working by this project.