Free
Anonymous text-only sharing for occasional secrets.
USD 0- Text secrets
- Short TTL
- View limits
- No opening codes
Private beta
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.
Free users can create simple text pushes. Paid beta, demo, and customer-trial access can be granted with a private coupon tied to the current anonymous token.
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 the shhhs CLI for scripting, CI, and Team operations. Use shhhs-mcp for local agent tools. Both encrypt locally for secret creation flows.
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.
Anonymous text-only sharing for occasional secrets.
USD 010 secrets / 3 months for paid, occasional work.
USD 29A short project window for clients, vendors, and urgent handoffs.
USD 49Better value for regular secure sharing.
USD 12/moA base workspace plus admin seats for teams and API-driven workflows.
USD 49/mo workspace + USD 9/seatPrivate deployment, customer admin, IAM lifecycle hooks, and Microsoft or Google Workspace integration planning.
Contact usYes. Private beta and demo access can be issued with a coupon that grants an entitlement to the current account token.
Use shhhs for shell scripts and operations. Use shhhs-mcp when an agent runtime needs MCP tools for local encrypted handoffs.
No. Support can help with billing cancellation, but cannot restore secrets or recreate access without valid access material.