Create one workspace. Connect one source. Send one event.
Move from account creation to one searchable operational signal without configuring the entire platform first.
Account
Create and verify
Workspace
Organization and project
Source
Scoped ingest key
Event
Send and inspect
Start from where you are.
New, returning, or evaluating—the next useful action should be immediately clear.
I am starting from zero
Create your account, verify your email, create your workspace, and send your first event.
I already have an account
Log in, choose your organization, select your project, and continue setup.
I am reviewing the platform
Read the setup path, review pricing, and understand how Lariba Cloud fits your workflow.
From account creation to first event in six clear steps.
Complete only the minimum path required to prove that the workspace, source, and ingestion flow are working.
- 01
Create your account
Start with a free account so your workspace can be linked to a real user.
Account created - 02
Verify your email
Confirm account ownership before continuing into workspace setup.
Identity verified - 03
Create your organization
Your organization becomes the top-level workspace for teams, projects, and settings.
Workspace ready - 04
Create your first project
Projects hold your event streams, API keys, sources, and operational context.
Project created - 05
Generate a source-scoped key
Create a scoped key that allows your app or service to send events securely.
Source connected - 06
Send your first event
Push one real event into the ingestion API and confirm that it appears in your workspace.
Event visible
Secure by default
Source API keys are scoped to the relevant project and can be rotated or revoked as the workspace grows.
Send one real event.
Replace the source API key with your own Event Sources key. Start with one simple event before connecting production traffic.
curl -X POST https://lariba-cloud-api.vercel.app/v1/events/ingest \
-H "Content-Type: application/json" \
-H "X-API-Key: YOUR_SOURCE_API_KEY" \
-d '{
"event_type": "checkout.completed",
"source": "backend-api",
"severity": "info",
"message": "Checkout completed",
"status": "triggered",
"payload": {
"plan": "pro",
"region": "eu-west"
}
}'Tip: keep your source API key private. Never expose ingest keys in client-side code.
Confirm the complete path.
After sending your first event, check that the signal is visible and attached to the correct project.
Your account and organization are created successfully.
Your project exists and has a valid API key.
Your event request is accepted by the ingestion API.
The event appears inside Foundation or the live workspace.
You can continue into alerts, visibility, and workflow setup.
Common setup questions.
Most first setup issues come from email verification, API key scope, or event payload format.
If something fails, start with one event, one project, and one API key before adding integrations.
I did not receive the verification email.
Check spam first. If it still does not arrive, return to login and use the verification help flow linked from the email verification message.
My API key is not working.
Confirm that you copied the full key, that it belongs to the correct project, and that you are sending it in the Authorization header.
My event does not appear.
Check the API response, project name, source name, and payload format. Start with one simple event before sending production traffic.
I already have an account.
Log in and continue from your existing organization, project, and environment instead of creating a new workspace.
Start with one source. Prove the flow with one event.
Confirm the flow works, then expand into alerts, integrations, automation, and stronger operational workflows.