Contact Lariba Cloud with the right context.
Choose the right path: start free, talk about a pilot, ask a security question, or get help understanding how Lariba Cloud fits your systems.
Contact routing
Start with the right path
Product setup
Start free + docs
Commercial fit
Pricing + sales
Integrations
Platform + context
Security
Disclosure email
Best first signal
Create one workspace, connect one source, send one event, then contact us with real operational context.
Contact paths
Choose the path that matches what you need next.
The best conversation depends on whether you are activating the product, evaluating pricing, planning integrations, or reporting a sensitive issue.
Product onboarding
For teams that need help creating a workspace, generating an API key, and sending the first real event.
Commercial evaluation
For teams comparing pricing, event volume, retention, onboarding, support, or enterprise fit.
Integrations
For teams that want to connect ERPs, SaaS apps, databases, queues, payment systems, or custom workflows.
Security disclosures
For sensitive reports, vulnerability disclosures, access issues, or security-related concerns.
Best first step
The best contact starts with one source.
Create one workspace, connect one source, send one event, and inspect it in the live activity view. That gives every onboarding, integration, or commercial conversation a clearer starting point.
01
Create your workspace
Start with the product flow and create a workspace for your team or project.
02
Generate an API key
Create a secure key for your backend, app, ERP, webhook, or integration source.
03
Send one real event
Send a product, system, payment, delivery, or workflow event into Lariba Cloud.
04
Contact us with context
Use the event flow, source, volume, and workflow context to shape the conversation.
What to include
Help us understand your use case faster.
The more operational context you include, the faster we can guide you toward the right setup, plan, or integration path.
Your product or workflow
Tell us what you are building and what operational signal you want to make visible.
Expected event volume
Share an estimate of daily or monthly events so we can understand your scale.
Projects and sources
Mention how many apps, services, ERPs, APIs, or webhooks may send events.
Systems to connect
Include tools like Stripe, Odoo, Cegid Primavera, databases, queues, or custom systems.
Environment stage
Tell us if this is testing, production, enterprise evaluation, or a client deployment.
Security or retention needs
Mention requirements around keys, access, audit logs, data retention, or onboarding.
Routing guide
Use the fastest path for your request.
Not every question needs a sales conversation. Some requests are better handled through docs, pricing, product activation, or a dedicated security disclosure.
Report sensitive issues through the dedicated security path.
For security reports or sensitive disclosures, use the dedicated security email so issues can be reviewed carefully and handled with the right level of urgency.
Security contact
security@laribacloud.comInclude reproduction steps, affected surface, expected impact, screenshots or logs where useful, and any details needed to validate the issue efficiently.
Clear context helps us respond better.
Keep the first conversation practical and tied to real usage.
Lariba Cloud is still early, so the most useful conversations are grounded in a real workspace, project, source, event flow, and operational problem.
message
We are building a marketplace workflow. We expect around 100,000 events/month from: - checkout-service - delivery-api - Stripe webhooks - ERP invoice sync We want to inspect failed deliveries, payment webhooks, and inactive sources. We are currently testing, but expect production usage soon.
Start with one real event. Contact us with real context.
The best conversations happen after you have a workspace, a project, and one real signal flowing into Lariba Cloud.