Any medium the company runs on.
The substrate reads across five categories of source system over read-only OAuth. In diligence, access is granted by the target company. In own-org monitoring, access is granted by the operator. Native connectors below. Custom sources are built to the substrate contract. How the signals combine into a report is on /methodology. The security posture is on /security.
Where the work is shipped.
- GitHub
- GitLab
Reads. Commits, pull requests, reviews, review latency, branch lifetimes, AI-assisted authorship.
Never written. No PRs opened, no reviews posted, no branches created.
Where the work is planned.
- Jira
- Linear
- ClickUp
Reads. Ticket flow, dependency graphs, sprint commitments versus delivery, scope drift.
Never written. No tickets created, no transitions triggered, no comments posted.
Where the work is discussed.
- Slack
- Microsoft Teams
Reads. Thread density, decision capture, escalation paths, sentiment shifts.
Never written. No messages posted, no reactions added.
Where time actually goes.
- Google Calendar
- Microsoft Calendar
Reads. Meeting load, focus time, after-hours patterns, cohort calendar-density decline preceding team retention risk.
Never written. No events created, no invites sent, no responses changed.
Where the work meets revenue.
- Salesforce
- HubSpot
- Zendesk
- Intercom
Reads. Renewal status, escalation patterns, account-team activity, revenue chain connectedness.
Never written. No records created, no fields updated, no tickets opened.
Bring the medium the graph does not know yet.
- Custom adapter
Contract. The substrate ingests typed facts. If the source produces them, an adapter written to the fact contract lands the source alongside the natives. Write to eli@zamski.com to scope one.
Read-only OAuth. Minimum scope requested per integration.
None. Zamski cannot post, comment, transition, or modify records.
30-Day Finding data deleted after 30 days, or sooner on request. Pilot data on pilot close.
No model training on customer data. LLM calls run as inference only.
DPA available on subscription day one. Controls documented at /security.
When a stack is still a poor fit.
Native and custom coverage does not fix every stack. Teams running on Bitbucket plus Asana plus Mattermost plus an internal CRM produce substrate signal too sparse for a meaningful report. The fit disclosure lives on /comparison. If the stack is close and an honest read is what is needed, write to eli@zamski.com.