Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.lerian.studio/llms.txt

Use this file to discover all available pages before exploring further.

March 5, 2026 Documentation update No action

​
Affects

Teams choosing between SaaS and BYOC deployment models. This update applies to the public documentation portal. It does not change the runtime API behavior unless the linked product documentation says otherwise.

​
What changed

A new Deployment Models page was added to explain the two ways to run Lerian products and help teams choose the right approach for their infrastructure and compliance requirements.

​
SaaS (fully managed)

In the SaaS model, Lerian manages the complete infrastructure — provisioning, scaling, monitoring, patching, and backups. Teams get:
  • Zero infrastructure overhead
  • Automatic updates and maintenance
  • Built-in observability and SLA guarantees
  • Shared-nothing multi-tenant isolation

​
BYOC (Bring Your Own Cloud)

In the BYOC model, Lerian products are deployed inside the customer’s own cloud account. Teams maintain full control over:
  • Infrastructure and network configuration
  • Data residency and sovereignty
  • Security policies and access controls
  • Scaling and cost optimization
Lerian provides Helm charts, deployment guides, and support — but the customer owns the infrastructure.
Several existing pages were updated to reference the new deployment models:
  • Getting Started — Now includes guidance on choosing between SaaS and BYOC before beginning setup
  • Security — Expanded with deployment-model-specific security considerations
  • About Lerian — Updated to reflect the dual deployment strategy
  • Deployment — Cross-references to the new page
  • Lifecycle Management — Links to BYOC operational guidance

​
Impact

This is a documentation update. No migration or product change is required.

​
What you need to do

1
Use the deployment model documentation when comparing SaaS and BYOC options.

​
Deadline

None.

​
Why

The documentation explains the available deployment models and links them to product-specific deployment guidance.