The five services
Lerian Console
One web interface for the products that ship a Console module.
Access Manager
Authentication and authorization for protected Lerian products: tokens, users, groups, applications, and MFA.
Streaming Hub
Delivers platform events to destinations you own: webhook, pull cursor, SQS, RabbitMQ, and EventBridge. It consumes the internal stream and never produces onto it.
Multi-tenancy
One deployment serves independent tenants. Each product derives tenant context according to its own authentication contract.
Observability
Products export traces, metrics, and logs over OpenTelemetry to a collector.
How the services sit around the products
The diagram shows five interactions.
- Your application sends a bearer token to a product route that Access Manager protects. The product asks Access Manager whether that subject may perform the route’s action, then admits or rejects it.
- Lerian Console reads and writes access data through Access Manager, and operates each product module.
- Streaming Hub matches events on the internal stream against your subscriptions and delivers each match.
- Products push traces, metrics, and logs over OTLP to the collector address you set.
- Your identity provider, when you run one, plugs into Access Manager as an upstream provider.
Services and products
What you bring and what Lerian ships
You bring:
- Cloud infrastructure and Kubernetes clusters.
- Database administration and backups.
- Network security, container patching, and secrets management.
- Your monitoring pipelines and the collector that receives telemetry.
- The destinations Streaming Hub delivers to.
- Your identity provider. It connects to Access Manager as an upstream provider and does not replace the identity backend.
- Helm charts for supported products and infrastructure components, through an OCI-compatible registry.
- Terraform examples for the base infrastructure Midaz needs on AWS, GCP, or Azure.
- Lifecycle Management for Enterprise BYOC: an agent in your cluster, through which Lerian installs and upgrades products.
- Access Manager and Lerian Console, as Enterprise features.
Adopt one service at a time
1
Access Manager
Get the Auth and Identity services running with Caradhras, PostgreSQL, and Valkey. Then turn enforcement on per product. Install first, validate, then enable.
2
Lerian Console
Point the Console at Access Manager. Its user and application screens read and write that data.
3
Streaming Hub
Deploy the dedicated
streaming-hub-helm chart, separate from any product chart. Its API routes require an Access Manager token.4
Observability
Deploy a collector in your Kubernetes cluster. Then configure the product workloads that support it to send telemetry to it.
Deploy and operate
Helm charts
Install and upgrade the published charts.
Lifecycle Management
Lerian installs and upgrades products in your cluster through an agent that you install.
Licensing
How a Lerian product validates its license key, and what each result allows.
Terraform examples
Create the network, DNS, database, and Kubernetes base Midaz needs on AWS, GCP, or Azure.
Build with Narya
Narya runs coding agents behind one HTTP API. One long-lived host on your machine owns the sessions, the store and the model connections. Lerian ships a terminal client and a one-shot command on top of it, and you can write your own client against the same contract.
Narya
What Narya is, how you run it, and how it fits a pipeline.
The host API
One contract for every client: socket, event stream, envelopes.
Where to go next
Deployment models · Multi-tenancy · What is Access Manager? · What is Lerian Console? · Streaming Hub quick start

