Frequently asked questions

Entirely inside your own infrastructure. CollaborationSonar is self-hosted - you run it in your environment, and the collected data is written to a Postgres database you control. Nothing is sent back to us.

Metadata only - timestamps, user IDs, action types, and interaction patterns. We do not ingest message bodies, file contents, source code, or document text. The signals that matter for operational visibility live in the metadata.

Each source (Slack, Jira, GitHub, ...) has its own user IDs. We unify them into a single identity per person before analysis, so cross-tool patterns make sense. You stay in control of how detailed that identity is - in some setups you may not want personal details, only that signals are attributed to the right person.

Not yet certified - we are working toward it. Architecturally we are set up well for it: the system runs entirely in your infrastructure, you remain the data controller, and we collect only metadata. Formal GDPR readiness (DPIA templates, processor agreements, certified retention controls) is on the roadmap. If you have specific compliance requirements, we are all ears.

Slack, Microsoft Teams, Jira, GitHub, Bitbucket, Azure DevOps, Confluence, Notion, Linear, Asana, Trello, Google Workspace, Figma, Miro, Zoom, and PagerDuty - among others. The integration list grows; if you need something specific that is not yet on it, ask.

Yes. On the Enterprise plan we build custom collectors for internal tools and audit log sources. The collector framework is the same one we use for first-party integrations, so adding a new source is usually a matter of days, not months.

Read-only admin scopes are enough in most cases. We document exactly which scopes are needed per source so your security team can review before granting them. No write access is ever requested.

We do the install inside your environment. Hands-on time is small; the longer pole is your team approving the architecture and provisioning OAuth apps.

A Kubernetes cluster and a Postgres database in your environment. Works on EKS, GKE, AKS, or any cluster you already run on-prem. Ships as container images.

We do, inside your environment. You keep the keys: every change - new images, configuration tweaks, new integrations - goes through your review before it lands.

We push new container image versions and you approve the rollout. We publish a changelog with breaking-change notes ahead of each release so your team can plan around change windows.

Annual on-prem licenses. Pricing depends on headcount and the integration mix you need. Installation assistance is included.

No. CollaborationSonar is sold as an annual on-prem license - no free trials and no paid pilots. Before you commit, we walk you through the product end-to-end on sample data so you know exactly what you are getting.

Yes. Send them over. We have answered most of the common ones already and can usually turn around standard questionnaires inside a week.

PE firms post-acquisition, COOs at mid-sized companies, heads of engineering at larger orgs, and operations teams managing distributed contractor pools. The page on /solutions has more detail.