Most ReportPlane workflows are combinations of the resources below. Learn these names first; the rest of the product will feel familiar.
AccountYour personal identity. It holds your name, email, password, and workspace memberships.
WorkspaceThe top-level team and subscription boundary. Members, roles, plan limits, and shared security resources belong here.
ProjectAn isolated product or environment inside a workspace. Models, warehouses, clients, and analytics belong to a project.
Data modelA named schema that defines allowed fields, their types, required status, and time semantics.
WarehouseThe storage and compute system used for accepted data and analytics queries.
DestinationThe relationship that sends one model's accepted records to a warehouse.
CredentialAn encrypted connection secret used by ReportPlane to access an external warehouse or service.
Ingest clientA write identity. It defines allowed data models, protocol, authentication, and network restrictions.
Query clientA read identity. It defines allowed Analytics APIs, authentication, and network restrictions.
API keyA programmable identity that can have ingest capability, query capability, or both, with explicit resource scopes.
Management TokenA personal, expiring control-plane credential with project restrictions and explicit Management API scopes.
Client CAA trusted certificate authority used to validate client certificates for mTLS.
Analytics APIA saved and published analytics definition. It describes dimensions, metrics, allowed filters, ordering, limits, and optional visualization metadata.
DimensionA field used to group or label results, such as country, plan, or page path.
MetricA numeric calculation such as count, sum, average, minimum, or maximum.
FilterA controlled condition applied at query time. Published filter allowlists prevent callers from filtering arbitrary fields.
ExplorerAn interactive workspace that uses the same analytics runtime to build and preview queries. It is not a separate query engine.
AlertA governed Event Alert or Analytics Alert rule with severity, grouping, cooldown, and Notification Channels.
IncidentOne open, acknowledged, or resolved lifecycle for an Alert and deterministic group.
OccurrenceA bounded sample or event reference merged into an Incident. The warehouse remains the full event history.
Notification ChannelA reusable Email, Generic Webhook, Slack, or Microsoft Teams delivery destination.
Workspace
└── Project
├── Data model ── Destination ── Warehouse
├── Ingest client ── writes allowed models
├── Analytics API ── reads model data
├── Query client ── executes allowed analytics
└── Alert ── Incident ── Notification Channel
