Karakoram

Karakoram

Karakoram is a multi-platform, self-hosted control plane for database and stateful-service orchestration inside your infrastructure, without Kubernetes or a hosted coordinator. A Go control plane provides a REST API, karactl CLI and web UI; providers supply infrastructure, while you operate the installation, credentials, data and recovery procedures. Zerops is the reference provider; Karakoram's maintainer works at Zerops (see Acknowledgements). Dokploy and Nomad are also available; see Providers for their status.

Status: pre-1.0. The current release is v0.4.3; read its known issues and the limitations before you rely on it. Dokploy and Nomad are experimental for every engine, and several engines are experimental on every provider (engine availability). The main branch, and the documentation on it, can describe changes that are not released yet.

Engines

Versions below are catalog defaults; each engine section lists supported versions and upgrade paths.

Release status and provider-specific availability are centralized in engine availability.

Providers

Karakoram is multi-platform; a namespace selects the infrastructure provider that provisions its members.

See Providers for capability differences and Operating costs for infrastructure costs.

Across engines

• Catalog-driven creation, resource configuration, disk growth and capability-gated cluster operations.
• S3-compatible storage, schedules and recovery.
• Multi-project namespaces and authenticated relays.
• Monitoring, logs and actor-attributed audit activity.
• Local accounts, OIDC, namespace-aware RBAC and owner-scoped API tokens: access control.
• Safe fleet operations, control-plane backup/recovery, notifications and backup drills, verified offline.

Warning: Review critical limits before production use: replica count does not guarantee independent hosts, Local Storage is single-host, and the control plane has one replica.

Quick start

Choose a provider in Providers. For Zerops, use the dashboard-only Quick start, or the installation reference for local deployments, custom names and CLI setup. Dokploy and Nomad installation paths are linked there.

Build from source

Requires Go 1.26+, Node 22.6+, npm and Make:

make build-all             # web UI and both Go executablesmake test                  # Go unit/handler tests# Integration-tagged tests (some require Docker; PostgreSQL/Supabase use native LXC):go test -tags integration -count=1 -timeout 30m ./...

A Go-only make build without UI assets serves a “UI not built” page. See UI development, Contributing and the end-to-end suite; deployment tests create billable Zerops resources.

Coding agents: read AGENTS.md for repository boundaries and contribution commands.

Documentation index

Keep docs/ beside the repository's api/, ui/ and root README so relative source/reference links resolve.

• Getting started: Overview · Quick start · Install · Providers · Operating costs · Upgrade
• Control plane: Architecture · Clusters and operations · Backups and storage · Namespaces and relays · Zerops provider · Dokploy provider · Nomad provider · Monitoring and events · Access control · Security · Operations and troubleshooting · Limitations
• Interfaces: Web UI · CLI · REST API and SDK · MCP quick start · MCP server · Cluster data MCP
• Operator agents: karakoram-operator skill · Skill installation
• Control-plane recovery: State backups and provider rebuild runbooks
• Backup verification: Scheduled and manual restore drills
• Notifications: Webhook, Slack and email channels, signatures and delivery guarantees
• MongoDB: Overview · Replica sets · Sharding · Users, roles and TLS · Backups and PITR · Operations
• RabbitMQ: Overview · Access and TLS · Definitions backups · Operations
• Elasticsearch: Overview · Kibana, Logstash and APM · Access and security · Snapshots · Operations
• Weaviate: Overview · Access and TLS · Backups · Operations
• PostgreSQL: Overview · Extension profiles: PostGIS, pgvector, TimescaleDB · Service bindings · Distributed Citus · Access and TLS · Backups and PITR · Operations
• Supabase: Overview · Components and availability · Operations
• Keycloak: PostgreSQL binding, routing and administrator recovery
• OpenBao: Overview · API access and TLS · Raft backups and recovery · Operations and unseal
• Temporal: Overview and prerequisites · Access and TLS · Operations and recovery
• MySQL and PXC: Overview · Configuration · Access and TLS · Backups and PITR · Operations and recovery · Native verification
• Neo4j Community: Overview · Access and TLS · Offline backups · Operations
• Reference: Architecture decisions · Native artifacts · Verification · Contributing · Code of Conduct

Acknowledgements

Thank you to Zerops for providing free-of-charge infrastructure for developing and testing Karakoram. Disclosure: Samyazz, who maintains Karakoram, is employed by Zerops as a system architect. Karakoram is not a Zerops product, and Zerops does not endorse it.

Karakoram installs Percona Server for MongoDB and Percona Backup for MongoDB from Percona's official repositories. It independently implements orchestration; no OpenEverest code or UI is copied into this repository.

License and trademarks

Karakoram uses the Apache License 2.0; see NOTICE. Dependencies retain their licenses and notices. Percona Server for MongoDB and Percona Backup for MongoDB are Percona products and trademarks. OpenEverest, MongoDB and Zerops names and marks belong to their respective owners. Karakoram is independent of OpenEverest and MongoDB and is not affiliated with or endorsed by them. Zerops does not endorse Karakoram either; its connection to Zerops is described under Acknowledgements.