Signals live in different systems
Product events, webhooks, alerts, and provider failures rarely share one operational context.
Operational event control plane
Operational event control for modern product teams
Capture operational events, identify where they came from, inspect delivery failures, and run permission-aware replay or retry actions with audit-ready visibility.
Source-awareDelivery-awarePermission-awareAudit-visible
The operational gap
Logs show symptoms. Operators need context and control.
Teams often receive events, alerts, and webhook failures in separate tools. Lariba Cloud connects the signal, its source, the delivery attempt, the recovery action, and the audit trail.
Failures are hard to trace
A failed delivery is only useful when teams can connect it to the source, event, and attempt history.
Operators need safe controls
Recovery actions need readiness checks, confirmation, bounded retries, and authoritative permission checks.
Mutations need an audit trail
Teams need to know who acted, what changed, and which attempt was created without exposing secrets.
Core platform
One control surface from event intake to recovery evidence.
The platform starts with trusted source identity, carries context through delivery, and applies guarded operator controls only where the current user and project allow them.
Event Sources
Give every producer a known identity, environment, readiness state, and operational history.
Source API Keys
Use source-scoped credentials so event intake is attributable, revocable, and separated by project.
Delivery Visibility
Inspect delivery attempts, lifecycle state, retry policy, terminal state, and sanitized failure context.
Replay and Retry-now
Run controlled recovery actions through readiness gates, explicit confirmation, and bounded execution.
RBAC Operator Permissions
Keep read access separate from replay, retry-now, channel management, and future DLQ controls.
Retry Audit Visibility
Review sanitized worker and operator audit evidence without exposing destination or provider secrets.
How it works
A controlled path from signal to action.
Each step preserves the context teams need to investigate, recover, and review operational outcomes without turning every viewer into an operator.
- 01
Ingest event
Capture a product or system signal through an authenticated event source.
- 02
Attach source identity
Keep project, environment, and producer context with the event from the start.
- 03
Track delivery
Follow each delivery attempt through sent, failed, retryable, terminal, and DLQ-visible states.
- 04
Inspect failure
Use event, source, lifecycle, and sanitized provider context to understand what happened.
- 05
Retry or replay safely
Check readiness and permissions before a confirmed operator action creates new execution state.
- 06
Audit the action
Keep retry, replay, lineage, and operator evidence visible to the project team.
Trust and safety
Visibility stays useful only when control stays bounded.
Capability metadata guides the dashboard, but backend RBAC remains authoritative for every operator mutation. Read access and action access are deliberately separate.
401 · authentication required403 · permission required
Project-scoped isolation
Events, delivery attempts, actions, and capabilities remain bound to the selected project.
Source-scoped credentials
Keys identify the producer and can be managed independently of general account access.
Permission-aware controls
Replay and retry-now remain protected by backend-enforced project permissions.
Clear 401 and 403 boundaries
Authentication failures stay distinct from authenticated users who lack an operator permission.
Capability-aware guidance
The dashboard uses capability metadata to guide the UI while backend RBAC stays authoritative.
Sanitized operational visibility
Audit and failure views avoid raw tokens, headers, destination URLs, payloads, and provider bodies.
Current stage
Developer Preview, with real Foundation and Delivery workflows active.
Lariba Cloud is an evolving product. The current platform supports event-source setup, event investigation, Delivery operations, controlled recovery, RBAC capability guidance, and audit visibility. Broader integrations, intelligence, and governance are still being expanded.
Active workflows
- Event Sources and source-scoped keys
- Core Events inspection and source context
- Delivery history, detail, lifecycle, and retry policy
- Controlled replay and retry-now execution
- Project-scoped RBAC capabilities and audit visibility
Planned expansion
- Broader integration coverage
- Deeper operational intelligence
- Expanded governance and role management
- Controlled DLQ operations after stronger permission controls
Start with one trusted event source
Build operational visibility before failures become business problems.
Create a project, identify the systems producing events, and give your team a controlled place to inspect and recover delivery failures.