Terms for using Lariba Cloud.
These terms summarize how Lariba Cloud should be used while the preview product, commercial structure, documentation, and legal agreements continue to mature.
Last updated: May 2026. This page is a product-facing summary and should be reviewed with legal counsel before being treated as a final commercial agreement.
Preview product
Lariba Cloud is still evolving. Features, limits, pricing, documentation, and availability may change as the platform matures.
Account responsibility
You are responsible for your account credentials, source API keys, workspace activity, and the data sent through your integrations.
Operational use
Lariba Cloud is intended for legitimate product events, API activity, workspace visibility, alerts, and operational workflows.
Use your account and workspace responsibly.
Lariba Cloud is built for product events, integrations, API keys, alerts, billing visibility, and operational workflows. Accounts and workspaces should be used for legitimate product and business operations.
Provide accurate account and workspace information.
Use organizations and projects to separate operational data correctly.
Keep access limited to people who should be part of the workspace.
Use Lariba Cloud in a way that matches applicable law and your internal policies.
Do not use Lariba Cloud to harm systems or users.
The platform exists to make operational signals clearer, not to support abuse, disruption, or unauthorized access.
Do not use Lariba Cloud to attack, overload, scan, disrupt, or abuse infrastructure.
Do not use the service to send malware, spam, phishing content, or harmful automated traffic.
Do not attempt to access accounts, organizations, projects, API keys, events, or data that do not belong to you.
Do not bypass usage limits, billing controls, authentication, rate limits, or security protections.
Do not use Lariba Cloud for illegal activity or activity that violates applicable laws or third-party rights.
You are responsible for your credentials and project keys.
API keys are powerful. Treat them like production credentials, keep them private, and revoke or rotate them when needed.
Keep your login credentials secure.
Keep API keys private and scoped to the correct project.
Rotate or revoke keys when ownership, access, or trust changes.
Do not expose secret keys in public repositories, client-side code, screenshots, or shared documents.
Notify Lariba Cloud if you believe your account or API keys have been compromised.
Do not expose secret API keys in public frontend code, public repositories, screenshots, demos, or shared documents.
Send only data you are allowed to process.
Lariba Cloud receives product and operational events. Users are responsible for the payloads and metadata they send into the platform.
You are responsible for the event payloads, logs, metadata, and operational data that you send to Lariba Cloud.
Do not send passwords, private keys, card data, medical data, or unnecessary sensitive personal data unless Lariba Cloud explicitly supports that use case.
You should only send data that you are allowed to process and transmit.
You are responsible for reviewing whether your own use of Lariba Cloud matches your internal policies and legal obligations.
Plans may differ by usage, retention, features, and support.
Lariba Cloud may offer free, paid, and custom commercial plans. Paid billing flows may be handled through Stripe or direct commercial arrangements.
Free and paid plans may differ by event volume, retention, features, workflow depth, support level, and team controls.
Paid subscriptions, invoices, checkout, and billing management may be handled through Stripe.
Paid features may depend on successful payment and active subscription status.
Enterprise terms, custom limits, custom onboarding, and commercial arrangements are handled directly with the Lariba Cloud team.
The product is designed for operational use, but still evolving.
Lariba Cloud is designed for real operational use, but the product is still maturing.
Features, quotas, workflows, APIs, documentation, and product surfaces may change as the platform improves.
Unless a separate written SLA applies, Lariba Cloud does not promise uninterrupted or error-free availability.
Users should evaluate whether the platform is ready for their own production requirements before relying on it for critical workflows.
Lariba Cloud may update, add, remove, rename, or change features as the product matures.
Plan limits, pricing, quotas, retention windows, and availability may change over time.
If a change materially affects paid usage, Lariba Cloud will aim to communicate the change clearly through the product, email, or commercial contact path.
Lariba Cloud may restrict or suspend access when there is suspected abuse, security risk, unpaid billing, platform misuse, or activity that could harm the service or other users.
Where practical, Lariba Cloud will try to provide context or a path to resolve the issue.
Immediate action may be taken when required to protect the platform, users, data, billing integrity, or security.
The platform is provided as an evolving product during its early stage.
Lariba Cloud may contain bugs, incomplete workflows, missing documentation, or changing interfaces.
You should not rely on the platform for critical production workflows unless you have evaluated the risk and agreed appropriate terms with the Lariba Cloud team.
Report security issues through the right path.
Lariba Cloud takes security issues seriously. Responsible disclosure helps protect users, workspaces, product events, authentication, billing, and platform trust.
Use the security contact path for responsible disclosure.
Include reproduction steps, affected endpoints, impact, timestamps, and useful logs or screenshots.
Do not access, modify, delete, or exfiltrate data that does not belong to you.
Report only what is needed to validate the issue safely.
Questions about these terms?
If you are evaluating Lariba Cloud for a team, production workflow, custom plan, enterprise onboarding, or specific data requirement, contact the Lariba Cloud team before relying on the platform for critical use.
Use Lariba Cloud responsibly and keep your workspace secure.
Create real workspaces, send only data you are allowed to process, protect your API keys, respect platform limits, avoid abusive activity, and contact Lariba Cloud if your use case needs a custom commercial, security, or legal agreement.