Skip to main content
Lerian supports two deployment models for its complete, modular platform: Lerian Cloud (SaaS) and BYOC (Bring Your Own Cloud). The deployment model defines who operates the infrastructure; your license and commercial agreement define which modules are available. Choose the model that fits your operational maturity, compliance requirements, and team structure. Availability depends on the permitted license and commercial arrangement.

​
Lerian Cloud (SaaS) — Fully managed by Lerian

In Lerian Cloud, Lerian hosts and operates the platform for you. Your team focuses on building financial products. We handle everything underneath. What Lerian manages:
  • Cloud infrastructure (compute, storage, networking)
  • Database provisioning, backups, and scaling
  • Security patches and OS-level updates
  • Application upgrades and version management
  • Monitoring, alerting, and incident response
  • High availability and disaster recovery
What you manage:
  • Business configuration (organizations, ledgers, accounts, rules)
  • API integrations with your systems
  • User access and permissions within the platform
  • Compliance obligations specific to your institution
Lerian Cloud is ideal if you want the fastest path to production without building or maintaining infrastructure. You get enterprise-grade operations from day one.

​
BYOC — Bring Your Own Cloud

In the BYOC model, you deploy and operate Lerian in your own infrastructure — whether that’s a public cloud (AWS, GCP, Azure), a private cloud, or on-premises. You have full control over the environment. Lerian provides the software, , , and tooling to make deployment and lifecycle management straightforward. What Lerian provides:
  • Application software (container images, Helm Charts)
  • Terraform templates for infrastructure provisioning
  • Lifecycle Management for deployment orchestration and version tracking
  • Security patches and application updates (delivered by Lerian, applied by you)
  • Technical support (Enterprise)
What you manage:
  • Cloud infrastructure and clusters
  • Database administration, backups, and scaling
  • Network security (firewall rules, network isolation, and traffic routing)
  • OS and container-level patching
  • Monitoring and observability pipelines
  • Encryption, secrets management, and access control
BYOC is ideal if your organization requires full data sovereignty, has strict regulatory constraints on where data lives, or has an established platform engineering team.

​
Why Helm for BYOC deployments

Lerian publishes official for the products and platform components supported through its Helm repository. Helm is the recommended way to deploy, configure, and manage the platform in your infrastructure. Here’s why it matters:
  • Reproducibility — Every deployment from the same chart version produces the same result. No “it works on my cluster” surprises across staging, production, or disaster recovery environments.
  • Rollback — Helm keeps a history of every release. Rolling back to a previous version is a single command — no need to reconstruct the previous state manually.
  • Reduced operational risk — Charts encode configuration details (environment variables, ports, dependencies), so your team does not have to remember them. Review your values and rendered manifests; Helm does not eliminate operational risk.
  • Faster time to production — Instead of writing Kubernetes manifests from scratch, start with Lerian’s official charts and adjust a single values file. Days of YAML editing become an afternoon of parameter tuning.
  • GitOps-ready — Charts integrate naturally with GitOps workflows (ArgoCD, Flux). Deployment configuration lives in version control, changes go through pull requests, and every deployment is traceable to a specific commit.
For the full version compatibility matrix, see Version compatibility. For step-by-step installation instructions, start with the Helm overview in the Platform section.

​
BYOC variations

For products and Enterprise entitlements that support multi-tenancy, BYOC supports two configurations:
Lerian Cloud is operated as a multi-tenant environment managed by Lerian. If you need dedicated, isolated infrastructure, choose BYOC Single-Tenant.

​
How your deployment model affects Midaz API integration

The Midaz API surface is identical across deployment models — same endpoints, same payloads, same responses. The difference is in how authentication and tenant scoping work. Lerian Cloud and BYOC Multi-Tenant (Midaz) Your tenant context is established automatically through your authentication token. There is no tenant header to pass and no tenant ID to manage manually.
  • You authenticate via Access Manager and receive a JWT.
  • That token includes your tenant context.
  • Every API call is automatically scoped to your tenant — organizations, ledgers, accounts, and transactions are all isolated.
  • You never interact with data from other tenants, and they never interact with yours.
BYOC Single-Tenant (Midaz) Configure authentication with PLUGIN_AUTH_ENABLED. It defaults to false for local and development onboarding, but production deployments must set it to true; BYOC Multi-Tenant deployments also require it. In a permitted non-production single-tenant environment with authentication disabled, API calls do not require a token.
For a deeper look at how tenant isolation works, see Multi-tenancy.

​
At a glance

Not sure which model fits? Jump to “Which model is right for you?” below.

​
Comparing the models

​
Which model is right for you?

Choose Lerian Cloud if:
  • You want to go live quickly without provisioning infrastructure
  • Your team prefers to focus on product and integration, not operations
  • You don’t have strict requirements for data to remain in your own environment
Choose BYOC if:
  • Regulatory or compliance rules require data to stay in your infrastructure
  • You need full control over networking, encryption, and access policies
  • Your organization has a platform or DevOps team ready to operate Kubernetes workloads
  • You want to integrate Lerian into an existing cloud environment with specific architectural constraints

​
Deployment and licensing

Deployment and licensing are related dimensions, but not every pairing is available. Lerian Cloud is Enterprise-only; Community supports self-managed Midaz BYOC. See Community and Enterprise.
Lerian Cloud requires Lerian to manage infrastructure, operations, and lifecycle on your behalf — capabilities that are part of the Enterprise offering. That’s why it is not available under the Community model.
  • Community + BYOC: You deploy and manage the source-available, ELv2-licensed Midaz software using the published Midaz Helm charts and documentation. Community support via GitHub and Discord. Other Lerian products are available to licensed customers under the Enterprise model.
  • Enterprise + BYOC: Full BYOC with Lifecycle Management, dedicated support, SLA, onboarding, and access to plugins.
  • Enterprise + Lerian Cloud: Lerian manages everything. You get the licensed platform modules without infrastructure responsibilities.

​
What’s next

Community and Enterprise

Understand the licensing differences and what’s included in each model.

Getting started

Follow the step-by-step guide to set up your first Ledger and run transactions.

Security

Learn how the shared responsibility model works for each deployment option.

Deployment strategies

Explore Kubernetes, Helm, and Terraform options for BYOC deployments.