ProlyticsIntroduction
Learn how Prolytics OS connects business movement, investigation, and recovery in one evidence-backed operating loop.
What is Prolytics OS
Run your first Health review ->
See investigation recipes ->
See what your data unlocks ->
Connect a source ->
Revenue moves in Stripe. Product behaviour changes in PostHog. Reliability pressure appears in Sentry. Each system shows its part of the story, but someone still has to decide what matters and connect the evidence.
Prolytics OS gives that work one operating loop. Health shows what changed and what deserves attention. Engine investigates what the available evidence can explain. Watch keeps the original condition visible after the team acts, so you can judge whether the outcome improved.
OS is not another fixed dashboard or a chatbot that explains one chart at a time. It keeps the metric, timeframe, evidence, uncertainty, investigation, and later outcome connected.
The Investigation Loop
Start With The Business Condition
Open Health when you need to know what changed and where to look first. The main briefing connects the most important movement across the selected reporting window. Billing, Usage, and Reliability then show where pressure is developing and keep every headline attached to the metrics behind it.
Needs Attention keeps the review focused. Health Findings preserve important detected issues. Health Signals capture supported metrics that moved materially against an established baseline. If both describe the same movement, Health suppresses the duplicate.
Do not scan every metric looking for a story. Start with the movement most likely to change a decision, then open its evidence.
Learn how to run a Health review ->
Establish What The Evidence Supports
Take a question into Engine when the cause is unclear, a hypothesis needs testing, or a number needs confirmation. Choose the narrowest mode that can answer it:
- Fetch retrieves a known metric or fact.
- Correlate tests whether specified signals moved together in a defined period.
- Investigate examines an unclear symptom and ranks the explanations the evidence supports.
Engine keeps its tool activity, sources, calculations, visualisations, limitations, and final answer inside the investigation. Missing evidence stays missing. Conflicting evidence stays visible. A plausible explanation is not presented as a proven cause.
Learn how to investigate with Engine ->
Watch What Happens Next
Closing a ticket, deploying a fix, or changing a campaign does not prove that the business problem recovered. Watch keeps the original condition connected to later observations so the team can see whether it improved, stayed flat, or became worse.
Resolve a Watch when the evidence supports recovery. Stop it when continued monitoring is no longer useful but the evidence does not support that claim. Watch tracks the outcome, not the action itself.
Evidence Before Confidence
Prolytics calculates metrics before generated language is requested. The model can summarise, prioritise, and explain the supplied facts. It does not become the source of truth for the number.
History and coverage determine what OS can support. If a metric needs more history, Health shows Building. If a source has no usable records for the selected period, it shows No data. If a connection cannot be trusted, the affected evidence is marked unavailable instead of becoming zero.
One connected source is enough to begin. Additional sources create more places to look and can strengthen a comparison. They do not give OS permission to treat unrelated records as the same customer or turn timing into causation.
More data is useful. More data does not make a weak claim true.
Architecture, Security & Access
OS acts as a read-only orchestration layer over the systems where your operational data already lives. Each connector requests only the permissions needed to retrieve and analyse supported evidence.
Prolytics cannot alter connected provider data, change subscriptions in your Stripe account, issue refunds, deploy code, or resolve incidents in your tools. Actions that affect your business systems remain under your control.
Data Storage & PII Scrubbing
Prolytics does not create a second unrestricted warehouse containing everything in your source systems. It stores the service records needed to operate OS. These include connection state, selected provider snapshots and source identifiers, derived metrics, Health Findings, Health Signals, Watches, prompts, evidence packs, AI outputs, and investigation history.
Rebuildable caches and snapshots are pruned under the applicable retention policy. Raw Stripe webhook payloads are redacted after 180 days. Canonical billing records needed for product operation, tax, legal, and audit purposes are retained.
Engine applies automated redaction to supported sensitive patterns before prompts and tool evidence enter model processing. These patterns include email addresses, phone numbers, IP addresses, and credentials. No automated scrubber can guarantee that every identifier will be detected, so OS also limits the sources, tools, and evidence available to each workflow.
We Don't Train on Your Data
We don't train on your data. It would overfit the system to patterns that only make sense inside your company and make the product worse for everyone else.
Your data is used to operate the service, answer your requests, preserve the investigation history you paid for, support you, and protect the platform. Production prompts, evidence packs, and AI outputs are not added to model-training or evaluation datasets unless you explicitly authorise that use.
Prolytics improves the investigation system itself: how it selects tools, evaluates evidence, performs diagnostic analysis, and communicates uncertainty. It does not fine-tune models on your raw event data or teach one customer's operating patterns to another.
Where To Begin
Use Health when you need to know what changed. Use Engine when you need a number, want to test a hypothesis, or need to investigate an unclear symptom. Use Watch when the condition matters after the current review.
If you are new to OS, connect the source that holds the evidence for your first question. Then run the five-minute Health review in the Operator's Manual. You do not need every source connected before the system becomes useful.