Invite-only controlled beta

Managed Valkey for teams that need predictable spend before self-serve polish.

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

Best for bounded workloads with real pricing pain and a reversible cutover.

Fit

Cache, sessions, rate limits

TTL-heavy workloads where a miss, re-auth, or fallback path is acceptable during beta.

Limit

No formal SLA or compliance

Do not bring regulated data, unrecoverable source-of-truth data, or procurement-heavy requirements.

Proof

Evidence before expansion

Restore drills, incident tabletops, usage reviews, and support boundaries are reviewed before quotas rise.

Auth

Magic link, then passkey

Accepted contacts use passwordless access; no shared passwords or public self-serve account creation.

Phase 3 self-service beta

Accepted clients can use the dashboard after an operator-issued invitation.

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.

Workspace

Guardrails are visible before provisioning

Plan, region, workload, memory, connection, command, and teammate limits are displayed before actions.

Access

Credentials are first-reveal only

KeyNest stores only fingerprints and version history; raw credentials are never shown again.

Evidence

Operational proof stays beta-safe

Readiness, usage, backup, restore, and support evidence uses observed, target, and hypothesis wording.

Operator

Exceptions stay founder-controlled

Provisioning is pauseable, idempotent, and blocked when a request exceeds assigned guardrails.

Structured intake

Apply with the same fields used for beta fit scoring.

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.

Beta application

Submit workload details.

Do not paste secrets, tokens, passwords, connection strings, hostnames with credentials, or regulated data.

The founder will score fit before provisioning. Credentials are never shared through this form.