Mikrom is a Rust-first, open-source edge platform designed for deploying containerized workloads into lightweight microVMs powered by Firecracker or Cloud Hypervisor. Every application gets hardware-level isolation in its own microVM, a dedicated ingress route with automatic TLS, and a placement decision made by a scheduler that coordinates workers over NATS — all driven from a singleDocumentation Index
Fetch the complete documentation index at: https://mintlify.com/mikronita/mikrom/llms.txt
Use this file to discover all available pages before exploring further.
mikrom app deploy command or a push to your Git repository.
What Is Mikrom?
Mikrom is built around the principle that strong isolation and developer simplicity should not be mutually exclusive. Rather than sharing a kernel across tenants, each deployed workload runs inside its own Firecracker or Cloud Hypervisor microVM. The control plane is a lean Rust binary (mikrom-api) backed by PostgreSQL and NATS; the web dashboard is SvelteKit; and every service in the stack — from the Pingora-based ingress router to the WireGuard mesh and the internal DNS resolver — is written in Rust and designed to be operated independently or composed together.
Key Components
Mikrom is organized as a Rust workspace. Each directory is a standalone service or library crate:| Component | Role |
|---|---|
mikrom-api | Control plane API — auth, app lifecycle, deployments, secrets, databases, webhooks, and billing |
mikrom-app | SvelteKit operator dashboard with Svelte 5, Tailwind CSS 4, and Playwright e2e tests |
mikrom-cli | Rust CLI client for day-to-day operations and automation |
mikrom-router | Pingora-based ingress router with ACME/TLS, health checks, and WireGuard-aware traffic routing |
mikrom-agent | Worker daemon that manages microVM lifecycle, metrics, logs, and host coordination |
mikrom-builder | Source-to-image build engine that turns Git repositories into OCI images via BuildKit |
mikrom-scheduler | Placement engine and worker registry that assigns workloads to available agents |
mikrom-network | WireGuard mesh and host identity coordination service |
mikrom-dns | Internal DNS resolver with DNS64 synthesis for platform and tenant resources |
mikrom-init | Zig-built binary that boots the guest workload environment inside each microVM |
mikrom-agent-ebpf | eBPF payload loaded by the agent for host-side networking and data-plane metrics |
mikrom-proto | Shared protobuf definitions and generated Rust types for internal service communication |
Key Features
Zero-Config Git Deployment
Point Mikrom at a Git repository URL and the builder, scheduler, and agent pipeline handles the rest — image build, placement, and microVM boot included.
MicroVM Isolation
Every workload runs inside its own Firecracker or Cloud Hypervisor microVM, providing hardware-level isolation without the overhead of full VMs.
Automatic TLS
The Pingora-based router handles ACME certificate provisioning and renewal automatically for every application hostname.
PostgreSQL via Neon
Managed PostgreSQL databases are provisioned through Neon and run in Cloud Hypervisor-backed microVMs when deployed on the platform. Defaults to PostgreSQL 16.
WireGuard Mesh
mikrom-network maintains a WireGuard overlay mesh across all worker nodes, giving every service and workload a stable private address.eBPF Data Plane
mikrom-agent-ebpf provides the compiled eBPF payload loaded by the agent for host-side network handling and low-overhead metrics collection.Scale-to-Zero Autoscaling
All applications scale to zero automatically after inactivity. Autoscaling can be configured with CPU and memory thresholds and a min/max replica range.
Dagger-Backed CI/CD
A local Dagger CI runner provides fast-feedback profiles from
ci-smoke to ci-release, runnable locally or inside GitHub Actions without environment drift.Supported Application Stacks
Mikrom’s builder recognizes and auto-configures the following application runtimes out of the box:- Phoenix (Elixir)
- Static sites
- Ruby on Rails
- Docker (bring-your-own Dockerfile)
- Go
- Rust
- Django (Python)
- Laravel (PHP)
- JavaScript (Node.js)
If your stack ships a
Dockerfile, Mikrom will use it directly. The builder falls back to automatic detection only when no Dockerfile is present.Observability
Mikrom ships with Dynatrace-backed OpenTelemetry instrumentation across all services. In the local development stack, a pre-configuredotel-lgtm container (Grafana, Prometheus, Loki, and Tempo) collects and visualises traces, metrics, and logs from every running service.
Technology Stack
- Backend: Rust 2024 edition, Tokio, Axum, SQLx, async-nats, reqwest, tracing, OpenTelemetry
- Router: Rust + Pingora, PostgreSQL, NATS, OpenSSL, WireGuard tooling
- Frontend: SvelteKit, Svelte 5, Vite, Tailwind CSS 4, shadcn-svelte, bits-ui, Lucide, Vitest, Playwright
- Platform & tooling: Firecracker, Cloud Hypervisor, PostgreSQL, Neon, NATS, Docker Compose, Dagger, BuildKit, GitHub Actions
Next Steps
Quickstart
Get Mikrom running locally, install the CLI, and deploy your first application in minutes.
Architecture
Explore the request flow, service responsibilities, and coordination model in depth.
CLI Overview
Browse every CLI command group — auth, app, deployment, db, volume, project, and more.
API Configuration
Review
mikrom-api environment variables, rate-limiting knobs, and Neon integration options.