Cache, sessions, rate limits
TTL-heavy workloads where a miss, re-auth, or fallback path is acceptable during beta.
Invite-only controlled beta
KeyNest beta is for qualified technical teams with low-risk Redis-compatible workloads, clear rollback paths, and a willingness to review operational evidence before expanding.
Fit criteria
TTL-heavy workloads where a miss, re-auth, or fallback path is acceptable during beta.
Do not bring regulated data, unrecoverable source-of-truth data, or procurement-heavy requirements.
Restore drills, incident tabletops, usage reviews, and support boundaries are reviewed before quotas rise.
Accepted contacts use passwordless access; no shared passwords or public self-serve account creation.
Phase 3 self-service beta
The dashboard covers invite acceptance, client workspace review, guarded Valkey provisioning, first-reveal credentials, support requests, usage evidence, backup/restore evidence, and audit history. It does not provide public signup, billing, SLA, GA, compliance, or unlimited capacity.
Plan, region, workload, memory, connection, command, and teammate limits are displayed before actions.
KeyNest stores only fingerprints and version history; raw credentials are never shown again.
Readiness, usage, backup, restore, and support evidence uses observed, target, and hypothesis wording.
Provisioning is pauseable, idempotent, and blocked when a request exceeds assigned guardrails.
Structured intake
This is not a vague waitlist. The details below map to the founder scoring record: workload shape, provider pain, command surface, rollback readiness, and pricing hypothesis.