Nest for Platform & Infrastructure Engineers
Nest gives platform and infrastructure engineers one declarative interface for every stateful backend they run on Kubernetes, reconciled against real operators instead of hand-rolled automation.
Pain points
- Maintaining bespoke scripts or Terraform modules per storage engine, each with its own quirks and failure modes.
- Hand-wiring HA replication, failover, and credential rotation for every new database or cache.
- Standing up separate tooling for on-cluster storage versus cloud-managed disks and buckets.
How Nest helps
- Provision block/file/object storage, PostgreSQL, Valkey, Kafka, OpenSearch, ClickHouse, Trino, and Iceberg through one CRD reconciled against real upstream operators, instead of separate tooling per engine. (DataResource Custom Resources)
- Get CloudNativePG streaming replication and Valkey primary/replica topology — configured automatically from `replicas.write.count` — without hand-wiring `replicaof` or failover scripts. (Managed Databases with HA)
- Use the same DataResource API whether a resource is provisioned on-cluster (managed) or against a cloud provider (external), rather than maintaining separate automation per environment. (Three Operating Modes)
- Provision OpenSearch, Kafka, ClickHouse, Trino, and Iceberg lakehouse resources the same declarative way as block storage. (Search, Streaming & Analytics)