A direct route to records
An in-memory key index locates records on local storage. Configurable value caching lets you choose how memory serves your workload.
✳ SIMPLE MAGIC. SERIOUS DATA.
Bring your own cloud. Run SMKV in your own account, on your own network, with your team in control and support from SimpleMagic.
Meet SMKV: our Rust database and persistent distributed cache for read-heavy applications where low latency matters and eventual consistency is a deliberate choice.
Keep the key index in memory, persist records on local storage, and distribute ownership across nodes. Use simple byte values or organize records into tables with typed columns.
# Start a local node
$ smkv-server --data-dir ./data \
--bind 127.0.0.1:7379
# Write a value, with an explicit sync
$ smkv --addr 127.0.0.1:7379 \
--sync put greeting hello
# Read it back
$ smkv --addr 127.0.0.1:7379 \
get greeting
helloSMKV is under active development. Replication is asynchronous, reads may be stale, and automatic failover and S3 backup/restore are not yet available. Start with a representative workload and validate before production use.
Good infrastructure makes its behavior understandable. SMKV keeps storage, routing, and cluster coordination distinct—so you can reason about the system.
An in-memory key index locates records on local storage. Configurable value caching lets you choose how memory serves your workload.
Partitions have explicit primary and replica owners. The Go client uses the cluster map to route requests to the right node.
Inspect nodes, capacity, and replication with the CLI or web console. Prometheus metrics expose throughput, processing latency, and errors.
The client routes the key to its partition owner. The node uses its index to locate the record and returns the value.
SMKV runs on Linux machines you provision in your cloud account. Your team operates the cluster; SimpleMagic helps you evaluate, configure, and troubleshoot it through an early-access engagement.
Choose your machines, storage, region, and private network. Cloud resources and billing stay in your account.
Your team owns access, capacity, upgrades, recovery, and availability. Install only the server, tools, or dashboard each host needs.
Discuss workload sizing and operational guidance with us. Remote access is not required by the installation; any support access is explicitly agreed with you.
Initial target: Ubuntu 24.04 on x86-64. Automated cloud provisioning, a hosted management plane, and managed operations are not included.
Install SMKVRecord sizes, read/write mix, memory budgets, and recovery expectations come before a feature checklist.
Consistency, durability, and performance are engineering decisions. We explain what the system does and where its limits are.
The database is one piece. Clients, installation packages, and operational visibility make it something you can actually work with.
LET’S MAKE DATA SIMPLER.
Tell us about your application, your data, and the part that’s getting complicated.