Distributed KV you can own

PallasDB is a self-hostable distributed key value store written in Go, designed for teams that want cloud-portable deployment without giving up operational control.

Built for the infrastructure team that wants storage to be explicit, portable, and inspectable.

Go runtimeKV semanticsSelf-hostableCRD path
self-hostableGolang coredistributed kvCRD readycloud portableoperator firstself-hostableGolang coredistributed kvCRD readycloud portableoperator firstself-hostableGolang coredistributed kvCRD readycloud portableoperator first

A storage layer with infrastructure taste.

The page leaves clear product surface for future AWS, GCP, and CRD controller actions while making the core promise unmistakable today.

Own the control plane

Run PallasDB inside your boundary, wire it to your observability stack, and keep rollout authority close to the operators who carry the pager.

Small binary, serious topology

A Go-native storage layer shaped for direct deployment, predictable packaging, and infrastructure teams that prefer explicit systems.

AWS and GCP launch paths

Reserve clean space for direct deploy buttons without making the product dependent on one cloud story.

Kubernetes as a first-class citizen

The upcoming CRD controller belongs in the main narrative, not buried in an integration footnote.

Readable failure domains

A distributed store should make placement, replication, and recovery legible before it makes them magical.

Cluster formation

Bootstrap nodes, declare topology, and let operators see what joined, moved, or recovered.

Cloud deploy targets

AWS and GCP entry points are staged as primary actions while keeping self-hosting at the center.

CRD operations

The controller path is designed for reconciliation, not a decorative Kubernetes checkbox.

Reconcile storage like product infrastructure.

The CRD controller can become the operational interface for clusters, upgrades, and placement policy without hiding the underlying distributed system.

PallasDB is built for teams that want the operational texture of a distributed key value store without surrendering their data plane to a managed black box.

Ship your own distributed data plane.

Add the AWS, GCP, and controller entry points when they are ready. The action area is already structured for clean cloud-specific deployment paths.