Secure, low-latency API key management service built on an edge-native serverless architecture.
Most key management solutions either introduce unnecessary latency or are overly complex.
CYPHR focuses on:
- Fast read access through edge caching.
- Strong encryption guarantees.
- Minimal operational overhead.
-
Edge Encryption (AES-256-GCM)
Secrets are encrypted at the edge before persistence. -
Low-Latency Reads
Cloudflare KV caching keeps key retrieval fast, wherever your requests come from. -
Edge-Native Execution
Runs on Cloudflare Workers for globally distributed execution. -
Minimal API Design
Simple and predictable API for managing keys. -
Lightweight Dashboard
Fast interface for managing secrets.
- Sign in using GitHub
- Store an API key
- Retrieve secrets via the dashboard
CYPHR handles encryption, caching, and storage automatically.
Below is a simple system design diagram to explain the basic flow of data
- AES-256-GCM encryption at REST before persistence.
- Stateless authentication model.
- No plaintext secrets stored.
- Client: HTML, CSS, Bulma, JavaScript (ES6+)
- Server: Node.js, Hono
- Auth: Supabase Auth
- Database: PostgreSQL (Neon)
- Edge Runtime: Cloudflare Workers
- Caching: Cloudflare KV
- Designed for developer-focused workflows.
- Focused on performance and simplicity.
- Encryption and decryption happen server-side; secrets are encrypted at rest.
- Decryption only on demand. Plaintext key is never cached, logged or exposed.
- Does not support full End-to-End Encryption (for now).
- Client: https://github.com/NexusWasLost/cyphr-client
- Server: https://github.com/NexusWasLost/cyphr-api
Built by Aritra