Skip to main content
Lerian supports two deployment models: SaaS and BYOC (Bring Your Own Cloud). Both give you access to the full product portfolio — the difference is who operates the infrastructure. Choose the model that fits your operational maturity, compliance requirements, and team structure. You can also combine models across products if needed.

SaaS — Fully managed by Lerian


In the SaaS model, Lerian hosts and operates the entire 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
SaaS is ideal if you want the fastest path to production without building or maintaining infrastructure. You get the full platform with 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, Helm Charts, Terraform templates, 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 Kubernetes clusters
  • Database administration, backups, and scaling
  • Network security (firewalls, VPCs, ingress)
  • 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.

BYOC variations

Depending on your architecture, BYOC supports two configurations:
ConfigurationDescriptionBest for
Single-TenantOne dedicated environment per institutionLarge institutions with strict isolation requirements
Multi-TenantOne environment serving multiple subsidiaries or clientsInstitutions operating as a platform or managing subsidiaries
SaaS is operated as a multi-tenant environment managed by Lerian. If you need dedicated, isolated infrastructure, choose BYOC Single-Tenant.

Comparing the models


SaaSBYOC
InfrastructureManaged by LerianManaged by you
Data locationLerian-managed cloudYour cloud or on-premises
Data sovereigntyData hosted in Lerian-managed cloud infrastructureFull control — data never leaves your environment
Security responsibilityShared (Lerian manages infra + app)Shared (you manage infra, Lerian manages app)
Time to productionFast — no infrastructure setup requiredDepends on your team’s provisioning timeline
Operational overheadLow — Lerian handles operationsHigher — your team operates the platform
CustomizationStandard configurationFull control over infrastructure and networking
ComplianceLerian’s environment meets security standardsYou ensure your environment meets your regulatory requirements
UpdatesApplied by LerianApplied by you via Lifecycle Management or Helm
ScalabilityManaged by LerianManaged by you

Which model is right for you?


Choose SaaS 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 model and licensing


Lerian’s deployment models (SaaS and BYOC) are independent from the licensing models (Community and Enterprise).
CommunityEnterprise
SaaSNot availableAvailable
BYOCAvailable (self-managed)Available (with Lifecycle Management and support)
SaaS requires Lerian to manage infrastructure, operations, and lifecycle on your behalf — capabilities that are part of the Enterprise offering. That’s why SaaS is not available under the Community model.
  • Community + BYOC: You deploy and manage everything yourself using the open-source Helm Charts and documentation. Community support via GitHub and Discord.
  • Enterprise + BYOC: Full BYOC with Lifecycle Management, dedicated support, SLA, onboarding, and access to plugins.
  • Enterprise + SaaS: Lerian manages everything. You get the full platform without infrastructure responsibilities.

What’s next