Lamassu IoT offers flexible deployment options designed for different use cases, from local development to production-grade Kubernetes clusters.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/lamassuiot/lamassuiot/llms.txt
Use this file to discover all available pages before exploring further.
Deployment Options
Monolithic Deployment
All-in-one deployment for development, demos, and small-scale environments
Kubernetes Deployment
Production-ready microservices deployment with horizontal scaling
Architecture Comparison
Monolithic Deployment
The monolithic deployment bundles all Lamassu services into a single process or container. It automatically manages dependencies like PostgreSQL, RabbitMQ, and Vault using Docker containers. Best for:- Local development and testing
- Proof-of-concept deployments
- Demo environments
- Quick evaluation of Lamassu features
- Single binary or container
- Automatic dependency management
- Minimal configuration required
- In-memory or SQLite storage options
- HTTP or in-memory service communication
Kubernetes Deployment
The Kubernetes deployment runs each Lamassu service as an independent microservice with dedicated pods, allowing for fine-grained scaling and resource management. Best for:- Production environments
- High-availability requirements
- Large-scale IoT deployments
- Enterprise integration scenarios
- Independent service scaling
- High availability with pod replication
- Advanced networking and ingress
- Production-grade storage backends
- Comprehensive observability
Core Services
Both deployment options include these essential services:| Service | Description | Container Image |
|---|---|---|
| CA Service | Certificate Authority management and certificate lifecycle operations | ghcr.io/lamassuiot/lamassu-ca |
| Device Manager | IoT device registration, management, and provisioning | ghcr.io/lamassuiot/lamassu-device-manager |
| DMS Manager | Device Manufacturing System for secure device onboarding | ghcr.io/lamassuiot/lamassu-dms-manager |
| KMS | Key Management Service for cryptographic operations | ghcr.io/lamassuiot/lamassu-kms |
| Alerts | Event monitoring and alerting system | ghcr.io/lamassuiot/lamassu-alerts |
| VA | Validation Authority for certificate validation | ghcr.io/lamassuiot/lamassu-va |
| UI | Web-based management dashboard | ghcr.io/lamassuiot/lamassu-ui |
Infrastructure Dependencies
Required Components
PostgreSQL
PostgreSQL
Primary data store for certificate metadata, device records, and system configuration.
- Development: Automatically managed by monolithic launcher
- Production: External PostgreSQL 12+ cluster recommended
Message Broker
Message Broker
Asynchronous event bus for inter-service communication.
- Options: RabbitMQ (default), AWS SQS/SNS, or in-memory (dev only)
- Development: Automatically managed or in-memory mode
- Production: Dedicated RabbitMQ cluster or managed AWS services
Crypto Engine
Crypto Engine
Secure key storage and cryptographic operations backend.
- Options: HashiCorp Vault, AWS KMS, AWS Secrets Manager, PKCS#11 HSM, Filesystem
- Development: Filesystem or auto-configured Vault
- Production: Hardware-backed HSM or cloud KMS strongly recommended
Next Steps
Choose Your Deployment
Select the deployment strategy that matches your requirements:
- Monolithic for development and testing
- Kubernetes for production workloads
Review Configuration
Understand the configuration options including environment variables, storage backends, and crypto engines.
Additional Resources
- Helm Charts Repository - Kubernetes deployment manifests
- UI Repository - Web dashboard source code
- Source Code - Backend services and APIs