Workspace
The organization-level boundary for teams, projects, access, and operational ownership.
These are the core terms used across Lariba Cloud Docs. They define how operational activity enters the platform, how it is trusted, and how it becomes searchable, actionable, and governed over time.
The organization-level boundary for teams, projects, access, and operational ownership.
A product or environment boundary where sources, events, quotas, and operational context are grouped.
A known producer of events, such as a backend, website, ERP, worker, service, mobile app, or integration.
A source-scoped credential used by external systems to send events into Lariba Cloud.
An operational record describing something that happened in a system, such as a payment failure, invoice creation, API error, or customer action.
The standard structure around an event: event id, event type, source id, environment, severity, timestamp, and payload.
A unique request key used to make retries safe and avoid duplicate operational records.
The operational memory layer for event storage, search, indexing, replay, and durable event history.
The future decision layer for rules, anomaly detection, alerts, risk scoring, and operational intelligence.
The future action layer for webhooks, queues, retries, dead-letter handling, notifications, and external workflows.
An optional future local collector, cache, and retry runtime for local-first resilience and lower-latency operations.
The governance layer for projects, sources, keys, policies, quotas, audit records, and configuration.
A workspace contains projects. A project contains event sources. Each source uses a source API key to send events. Events follow a standard envelope so Lariba Cloud can authenticate, validate, store, search, and later evaluate them through Core, Sentinel, and Delivery.