01
Sharding
Scale Postgres past the limits of a single machine to hundreds of millions of QPS and petabytes of data.
02
Shard splitting
Split hot shards as workloads grow. Neki creates new target shards, catches them up with replication, and moves traffic through topology changes.
03
Zero-downtime resharding
Move data to a new shard layout while the database stays online. Rebalance capacity without application rewrites or maintenance windows.
04
Real Postgres at scale
Each shard is real Postgres. Neki adds the router, sidecars, and control plane needed to scale Postgres horizontally.
05
High availability
Let the platform track health, promote replicas, and update routing. Applications keep using the same Postgres endpoint.
06
Online schema changes
Run schema changes as coordinated workflows across shards. Neki applies the right method per shard and tracks progress through cutover.
07
Connection pooling
Pool connections inside the sharded database layer. Neki routes with awareness of topology, shard health, and session state.
08
Shard groups
Assign different tables or workloads to different shard groups. Scale hot, cold, or isolated data on the hardware profile it needs.
09
Multi-AZ availability
Run each shard as a highly available Postgres cluster across availability zones. Failures stay isolated to the smallest possible unit.
10
Data topology
Define how data maps to shards, shard groups, and shard indexes. Placement is explicit, reviewable, and built for controlled resharding.
11
Cross-shard transactionsComing soon
Write across shards in one transaction. Neki coordinates commit so the change is atomic: every shard applies it, or none do.
12
Workflows
Use explicit workflows for imports, resharding, schema changes, cutovers, and cleanup. Neki makes distributed Postgres operations repeatable.
13
Online version upgrades
Move to new Postgres versions through the same online migration model: create target shard groups, replicate, cut over, and retire the old groups.
14
Zero-downtime imports
Import into Neki while the source database keeps serving traffic. Copy, replicate, verify, and cut over when the target is ready.
15
CDC
Each Neki shard has its own WAL and logical replication path. CDC stays compatible with standard Postgres patterns and per-shard streams.
Run Postgres at any scale.
Start with a single shard and split as you grow. Bring an existing database over with a zero-downtime import, or talk to the team about your workload.
