English Français العربية

Karakoram

السجل الرسمي البيانات وقواعدها

Self-hosted database control plane: clusters, backups and operations. Read-only by default.

الشيفرة المصدرية الموقع التوثيق

التثبيت

أضف هذا إلى إعدادات MCP في عميلك (Claude Desktop: claude_desktop_config.json، وCursor: ‏.cursor/mcp.json، ويستخدم VS Code وغيره الصيغة نفسها «mcpServers»).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http karakoram 'https://{control_plane_host}/mcp' --header 'Authorization: <Karakoram API token; `karactl mcp config` mints a restricted, read-only one>'
إعداد JSON (Claude Desktop وCursor وVS Code) 
{
    "mcpServers": {
        "karakoram": {
            "type": "http",
            "url": "https://{control_plane_host}/mcp",
            "headers": {
                "Authorization": "<Karakoram API token; `karactl mcp config` mints a restricted, read-only one>"
            }
        }
    }
}

التوثيق

مأخوذ من ملف README للمشروع على GitHub ويُحدَّث أسبوعيًا. تفتح الروابط على GitHub.

المحتويات
  1. Karakoram
  2. Engines
  3. Providers
  4. Across engines
  5. Quick start
  6. Build from source
  7. Documentation index
  8. Acknowledgements
  9. License and trademarks

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.

EngineDistribution/versionTopologiesBackupsSection
MongoDBPercona Server for MongoDB 8.0.32-14; Percona Backup for MongoDB (PBM) 2.16.0-1Replica sets; sharded clustersLogical/physical; point-in-time recovery (PITR)MongoDB
RabbitMQRabbitMQ 4.3.61/3/5/7 brokersDefinitions only; no messages or PITRRabbitMQ
ElasticsearchElasticsearch 9.5.5; optional same-version Kibana, Logstash and APM ServerCombined nodes; dedicated mastersNative S3 snapshotsElasticsearch
WeaviateOfficial Weaviate 1.40.1; mixed-license binary, community features onlySingle; 3–9 data members with three fixed Raft votersNative S3 full; no PITRWeaviate
PostgreSQLPercona PostgreSQL 17.11.1 default; majors 16/17/18; extension profilesSingle; Patroni/etcd HA (3/5); Citus distributed; ProxySQL client servicepgBackRest full/diff/incr and PITRPostgreSQL
SupabasePostgreSQL 17 plus release-locked native servicesSame database topologies; modular servicesPostgreSQL data only; separate S3 object protection requiredSupabase
KeycloakOfficial Keycloak 26.8.1; OpenJDK 21One native runtime with a PostgreSQL bindingThrough the source PostgreSQL clusterKeycloak
OpenBaoOpenBao 2.7.11/3/5 members; integrated Raft or bound PostgreSQL storageRaft snapshots to S3; PostgreSQL storage uses source recovery; no PITR for RaftOpenBao
TemporalTemporal 1.32.1 (also 1.31.4); ui-server 2.56.0Combined server; split stateless roles on bound PostgreSQL; Dokploy/Nomad only, not ZeropsSource PostgreSQL backup plus cluster-state manifest; requires binding serviceTemporal
MySQLPercona Server for MySQL 8.4.11-11 default; majors 8.4/8.0Single; Group Replication single-primary (3/5); ProxySQLXtraBackup full/incremental and GTID-based PITRMySQL
Percona XtraDB ClusterPXC 8.4.11-11.1 default; majors 8.4/8.0; separate pxc engine driverGalera cluster (3/5); one ProxySQL-routed writerSeparate PXC backup provenance; full/incremental and PITRPXC
Neo4j CommunityNeo4j 2026.09.0 / 2026.10.0 (default); Temurin Java 21Single member onlyOffline system + graph dumps; full outage; no PITRNeo4j

Providers

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

ProviderRole / runtimeInfrastructure and guide
ZeropsReference providerManaged Ubuntu runtimes, Local Storage and public routing in existing projects; guide.
DokployDocker SwarmApplications and node-local volumes on your Dokploy-managed Docker Swarm; guide.
NomadNative jobsNative jobs and dynamic host volumes on your operator-managed Nomad cluster; guide.

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

Across engines

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 executables
make 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.

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.

الأسئلة الشائعة

ما هو Karakoram؟

Self-hosted database control plane: clusters, backups and operations. Read-only by default.

كيف أثبّت Karakoram؟

يعمل كخادم بعيد. في Claude Code: claude mcp add --transport http karakoram 'https://{control_plane_host}/mcp' --header 'Authorization: <Karakoram API token; `karactl mcp config` mints a restricted, read-only one>'. وفي العملاء الآخرين، الصق إعداد JSON من هذه الصفحة في إعدادات MCP الخاصة بهم.

هل يحتاج Karakoram إلى مفتاح API؟

نعم. يتطلب Authorization، وتضبطها في إعداداته.

هل Karakoram مفتوح المصدر؟

نعم. شيفرته متاحة على GitHub بترخيص Apache-2.0.

من يصون Karakoram؟

ينشره KarakoramDev. يدرجه AI.tn لكنه لا يصونه ولا يوصي به.

من سجل MCP الرسمي. الإدراج ليس توصية: راجع شيفرة الخادم وصلاحياته قبل منحه الوصول إلى بياناتك.