Guided Atlas setup
Best for founders who want help deciding what data is enough. We map your systems, define the first permission boundary, decide what should be redacted, and choose the fastest path to the first audit.
Atlas Integration Guide
Atlas connects the evidence before Brain Engine diagnoses churn.
Atlas is the permissioned evidence agent for OrthancIQ. It pulls approved records, cleans messy data, maps it into a customer evidence layer, detects missing signals, and sends validated evidence into Brain Engine.
Atlas Data Agent
Best for teams ready for recurring evidence refresh. Atlas can sit beside approved systems, normalize records into OrthancIQ’s evidence contract, and send only the fields your team has approved.
CSV / JSON first audit
Best for early pilots. Send structured exports for usage, billing, CRM, support, and product context so Atlas can test whether the first dossier set has enough signal.
Atlas boundary
Atlas creates structure, not fake history.
When we say Atlas can create evidence, we mean it creates structured records, mappings, tasks, and audit trails from approved sources. It does not fabricate customer behavior.
Atlas can create
- Canonical evidence events from approved raw records
- Account/user identity bridges
- Field mappings and source health reports
- Missing-evidence and instrumentation tasks
- Audit logs for data pulls, transformations, and approvals
Atlas cannot create
- Historical usage that never happened
- Churn-risk scores by itself
- New tracking without approval
- Shared training data across customers by default
- Unredacted PII retention unless explicitly approved
Evidence contract
The minimum approved evidence Atlas needs.
During Private Rollout, we provision your tenant ID, API key, and exact base URL during setup. The contract below shows the shape of approved records Atlas can normalize before Brain Engine reasons from them.
AccountsCompany/account, contract value, lifecycle stage, owner, renewal date.
UsersKey people inside accounts: admin, champion, billing owner, workflow owner.
EventsMeaningful product actions, not just logins. Example: workflow run, export, invite, integration connected.
SubscriptionsMRR, plan, renewal timing, cancellation state, seat count, invoice events.
SupportTickets, sentiment, unresolved blockers, cancellation notes, success-manager context.
POST /v1/eventsExample payload
{
"tenant_id": "tenant_provisioned_by_orthanciq",
"account_id": "acct_123",
"user_id": "user_456",
"event": "workflow_export_completed",
"occurred_at": "2026-06-08T10:24:00Z",
"properties": {
"workflow": "board_report",
"source": "product",
"success": true
}
}No diagnosis before data. OrthancIQ does not claim a churn read from the request form alone. The form only starts the setup process. Atlas needs approved customer evidence before Brain Engine can build dossiers, score recovery potential, or recommend action.
Setup sequence
What happens after you request access.
1
Request access
Tell us your company, MRR range, and which data systems matter.
2
Define Atlas permission boundary
We agree which sources, fields, redaction rules, and retention windows Atlas can use.
3
Connect approved data
Use API, CSV, JSON, or a guided export depending on what is fastest.
4
Run first dossiers
Only after Atlas prepares approved evidence does Brain Engine generate risk dossiers and next actions.
Ready to connect?
Start with Atlas setup, not a blind upload.
We will help your team choose the simplest approved data path for the first audit: Atlas Data Agent, API stream, CSV/JSON export, or guided onboarding.