Case Study: Hyver achieves scalable, low-latency API key management with ScyllaDB

How Hyver uses ScyllaDB for API Key Management

Hyver, a platform-oriented company that previously built ad-hoc authentication for specific clients (like web users and Zapier), faced the challenge of scaling API key management as more integrations and developer access were added. To solve this, Hyver adopted ScyllaDB for storing and looking up API keys because of ScyllaDB’s high throughput, fast reads, and simple read/write semantics.

Using ScyllaDB, Hyver implemented an accounts table (storing a map of API keys and permissions) plus a separate api_keys table keyed by api_key so authentication can be performed with a single SELECT by primary key. This design avoided expensive indexed lookups, reduced authentication latency, simplified permission checks, and improved scalability—allowing Hyver to authenticate requests quickly at scale while accepting modest extra write work for key updates. ScyllaDB’s performance thus enabled faster, more reliable API key handling across multiple integration points.

Hyver

Kirk Morales

Chief Executive Officer