Lavik Admin
Deploy and operate Lavik clusters through the Admin UI bundled with 0.1.0.
Start The Included Admin
Download a 0.1.0 release archive from Download and extract it. Run ./lavik-admin from that directory, open http://localhost:4173, and sign in using the access token printed in the terminal. Linux uses the included Node.js runtime; macOS needs Node.js 24.15 or newer and uses SSH to install Linux binaries on hosts. APT packages and server Docker images do not include Admin.
Deploy A Version-Pinned Cluster
Choose Create cluster → Set up machines. Prepare hosts, verify SSH access and private cluster addresses, then select the v0.1.0 GitHub release in Node placement. Keep the selected release explicit: choosing nightly or an architecture-mismatched demo may download a nightly build. Review placement and storage before deploying.
Use Dashboard, Topology and Operations to observe readiness, add replicas and follow operations. Three separate hosts provide a useful starting point for host-level redundancy. Dedicated SPDK deployment requires explicit device selection and its own host prerequisites; do not select a disk containing data you need.
Monitoring And Workspace
Admin can provision Prometheus, Grafana and the Lavik dashboard on prepared monitoring hosts with Docker Engine and Compose v2. Back up the private Admin workspace, including its SSH identity and trust files, separately from each cluster’s Meta and Data files. Stopping Admin does not stop managed clusters.