Private beta

Beta access for real handoffs, without weakening the privacy model.

Shhhs beta accounts are activated by checkout or private coupon. Paid users should save their token, register passkey where available, generate recovery codes, and test request links before client use.

01

How beta access works

Free users can create simple text pushes. Private coupons remain available for demos, governed QA, and customer trials.

  • No public coupon directory
  • Security Kit appears after activation
  • Private coupons only

02

What to test first

Run a small internal handoff before sending secrets to a customer. Validate create, open, burn, request link, Email OTP when enabled, and the lost-access support boundary.

  • Use test data only
  • Check mobile and desktop
  • Do not store plaintext in screenshots or logs

03

CLI and MCP during beta

Use the shhhs CLI for scripting, CI, and Workspace operations. Use shhhs-mcp for local agent tools. Both encrypt locally for secret creation flows.

  • shhhs for scripts
  • shhhs-mcp for agents
  • No plaintext in prompts or logs

04

Support boundary

Support can help validate billing and cancellation. Shhhs cannot restore lost secrets or recreate access if the token, passkey, and recovery codes are all lost.

  • No secret recovery
  • Billing support only
  • Metadata-only investigation

FAQ

Can I get beta access without public checkout?

Private beta and demo access can still be issued with governed coupons.

Should I use CLI or MCP?

Use shhhs for shell scripts and operations. Use shhhs-mcp when an agent runtime needs MCP tools for local encrypted handoffs.

Can Shhhs recover my beta account if I lose everything?

No. Support can help with billing cancellation, but cannot restore secrets or recreate access without valid access material.