Core conceptsLast updated: June 2026

Concepts

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.

Available now

Workspace

The organization-level boundary for teams, projects, access, and operational ownership.

Available now

Project

A product or environment boundary where sources, events, quotas, and operational context are grouped.

Available now

Event Source

A known producer of events, such as a backend, website, ERP, worker, service, mobile app, or integration.

Available now

Source API Key

A source-scoped credential used by external systems to send events into Lariba Cloud.

Available now

Event

An operational record describing something that happened in a system, such as a payment failure, invoice creation, API error, or customer action.

Available now

Event Envelope

The standard structure around an event: event id, event type, source id, environment, severity, timestamp, and payload.

Available now

Idempotency Key

A unique request key used to make retries safe and avoid duplicate operational records.

In progress

Core

The operational memory layer for event storage, search, indexing, replay, and durable event history.

Planned

Sentinel

The future decision layer for rules, anomaly detection, alerts, risk scoring, and operational intelligence.

Planned

Delivery

The future action layer for webhooks, queues, retries, dead-letter handling, notifications, and external workflows.

Planned

Edge Node

An optional future local collector, cache, and retry runtime for local-first resilience and lower-latency operations.

In progress

Control Plane

The governance layer for projects, sources, keys, policies, quotas, audit records, and configuration.

How the pieces fit together

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.

Docs v0.1 focuses on Foundation and Ingestion. Core is in progress. Sentinel, Delivery, and Edge are product direction and should not be treated as production-complete features.