The core loop
Causeloop is organized around a single closed loop that turns raw failures into verified fixes.Issue
A discrete failure event — an incident, a defect, a failed check. Issues arrive automatically from connected sources or are created directly via the API or UI.
Pattern
Causeloop groups related issues by shared root-cause fingerprint. A pattern surfaces the recurring failure behind a set of issues rather than treating each one as isolated.
Prediction
From each pattern’s frequency and signal history, Causeloop predicts where and when the failure is likely to recur — giving you a window to act before it does.
Tenancy model
Organization
The top-level account — one per client. Carries the plan, seat count, and billing identity. Status:
active, suspended, or cancelled.Workspace
The data boundary owned by an organization. All issues, patterns, connectors, and settings live inside a workspace. One organization typically has one workspace, but the model supports more.
Membership
The link between a user and a workspace. Carries the role that governs what the user can do inside that workspace.
Organization
An organization is the client entity. It owns one or more workspaces and controls plan-level constraints:| Field | Notes |
|---|---|
slug | URL-safe unique identifier (e.g. acme) |
plan | free / starter / growth / enterprise |
seats_total | Maximum active memberships |
status | active / suspended / cancelled |
Workspace
A workspace is the operational data boundary. Every API call resolves to a single workspace; Row-Level Security (RLS) enforces that no query can read another tenant’s data.| Field | Notes |
|---|---|
slug | Unique within the organization |
timezone | Default display timezone for all reports |
sso_enforced | When true, password login is blocked for the workspace |
workspace_settings record controlling AI confidence thresholds, retention policies, and alert sensitivity, and an onboarding_state record that drives the setup wizard.
User
A user is a global identity (unique by email). Theexternal_id field stores the Clerk subject ID when the user authenticates through Clerk or another IdP.
Membership
A membership joins a user to a workspace with a role. Roles are cumulative — each role includes all permissions of the roles below it:| Role | Can do |
|---|---|
viewer | Read issues, patterns, predictions, recommendations, and reports |
analyst | Everything above, plus create/update issues, link patterns, trigger analysis, create connectors |
admin | Everything above, plus invite members, manage settings, create alert rules, export data |
owner | Everything above, plus manage organization settings, billing, and SSO |
A user can belong to multiple workspaces with different roles in each.
Product entities
Issue
An issue is a single failure event ingested from a connected source or created manually.| Field | Values |
|---|---|
severity | p1 (critical) · p2 · p3 · p4 |
status | open · in_loop · mitigating · resolved · closed |
source | The connector type that originated the issue (e.g. pagerduty, jira, github) |
risk_score | 0–100 composite risk signal |
in_loop are actively being analyzed as part of a pattern.
Pattern
A pattern groups issues that share the same underlying root cause. Causeloop detects patterns automatically by clustering issues on their fingerprint (signal dimensions such as service, error type, time-of-day, and affected team).| Field | Values |
|---|---|
status | emerging · active · resolved |
risk_score | 0–100 aggregate signal |
confidence | 0.0–1.0 model confidence that the grouping is accurate |
fingerprint | Key–value map of the shared signal dimensions |
resolved when a closure note is recorded and its open member issues stop recurring within the configured proof window.
Cluster
A cluster is a higher-order grouping of patterns that share structural relationships (common services, overlapping time windows, or shared contributing factors). Clusters appear in the pattern graph view and help you see which patterns belong to the same systemic problem. Clusters are computed asynchronously. You can trigger a recompute viaPOST /clusters/recompute.
Prediction
A prediction is a forward-looking risk signal derived from a pattern’s recurrence history.| Field | Notes |
|---|---|
probability | 0.0–1.0 likelihood the pattern recurs within window_days |
window_days | Forecast horizon in days |
impact | critical / high / medium / low |
likely_trigger | AI-generated description of what will likely cause the next recurrence |
hit / miss / prevented) on each prediction to improve accuracy over time.
Recommendation
A recommendation is a ranked, actionable remediation tied to one or more patterns.| Field | Values |
|---|---|
status | pending · in_progress · implemented · dismissed |
effort | low / medium / high |
impact | high / medium / quick_win |
rank | Priority order within the workspace (1 = highest) |
expected_loops_prevented | Model estimate of recurrences eliminated if this fix holds |
POST /recommendations/{id}/push.
Integration entities
Connector
A connector is a configured integration with an external tool. Connectors pull issue data into Causeloop on a schedule or respond to inbound webhooks. Causeloop supports 70+ connector types organized by category:| Category | Examples |
|---|---|
| Cloud & Monitoring | Datadog, Dynatrace, New Relic, AWS CloudWatch |
| Productivity & Incident | PagerDuty, Jira, GitHub, Linear, Opsgenie |
| CRM & Support | Salesforce, Zendesk, HubSpot |
| Data | PostgreSQL, Snowflake, BigQuery |
| Security | Okta, CrowdStrike, Splunk |
status (active / paused / error), a configurable poll_interval_seconds, and a sync run history.
Plan and seat concepts
Plan
A plan is the subscription tier of an organization:free, starter, growth, or enterprise. The plan controls feature flags, rate limits, and which connectors are available.
Seat
A seat is one active membership slot. The organization’sseats_total cap limits how many concurrent active memberships a workspace can hold. Suspending a membership frees the seat without deleting the user’s data.
Quick reference
| Term | One-line definition |
|---|---|
| Organization | Top-level client account |
| Workspace | Data boundary; all product data lives here |
| User | Global identity (unique email) |
| Membership | User ↔ Workspace link with a role |
| Issue | A single failure event |
| Pattern | A cluster of related issues sharing a root cause |
| Cluster | A grouping of related patterns |
| Prediction | A forward-looking recurrence risk signal |
| Recommendation | A ranked, trackable fix for a pattern |
| Connector | A configured integration that feeds issues in |
| Plan | Subscription tier controlling features and limits |
| Seat | One active membership slot against the org’s cap |
Quickstart
Get from sign-in to your first insights in 10 minutes.
Architecture
Understand how the platform layers fit together.