Shhhs Open app

Pricing

Choose the right Shhhs plan for each secret handoff

Start free, upgrade to Pro for USD 5/month or USD 50/year, and add automation identities when agents, scripts, CI, CLI, or MCP need separate scopes. External recipients and submitters do not consume seats.

Packages

Free

Anonymous text-only sharing when you need a quick one-time handoff.

USD 0
  • Text secrets
  • Short TTL
  • View limits
  • No opening codes
  • No workspace history
Create free

Pro

For recurring work with files, request links, private rooms, workspaces, CLI, MCP, and one automation identity.

USD 5/mo or USD 50/yr
  • Recurring capacity
  • Files
  • Opening codes
  • Request links
  • Private Rooms
  • Workspaces
  • 1 automation identity
Start Pro

Automation identity

Add scoped identities when agents, scripts, CI jobs, or MCP runtimes need separate access and revocation.

USD 1/mo per extra identity
  • Separate scopes
  • Separate audit trail
  • Revocable per agent
  • No shared human token
Add identity

Automation pack

Fifteen additional identities for agent fleets, integration environments, and CI workflows.

15 identities for USD 10/mo
  • 15 identities
  • Agent fleet separation
  • Integration-specific scopes
  • Lower per-identity cost
Add pack

Enterprise

Customer admin, IAM lifecycle review, Microsoft or Google Workspace planning, and deployment review.

Contact us
  • Customer Enterprise Admin
  • Connector planning
  • Microsoft 365/Teams review
  • Google Workspace review
Contact us

Free

For an occasional text handoff where speed matters more than workspace controls. Start here when the recipient only needs a temporary link and no one needs a billing record, reusable policy, or workspace history.

  • No account required for basic use
  • Short expiration
  • One open by default
  • Recipient account not required
  • No opening codes, files, workspace console, or history

Pro

For one professional who repeatedly shares credentials, files, and sensitive handoffs. Pro is the personal operating plan for request links, private rooms, longer controls, and a console tied to the account token.

  • One internal user
  • Text and file sharing according to current limits
  • Request links for receiving credentials
  • Private Rooms for short sensitive exchanges
  • Longer expiration and advanced controls
  • Personal console and permitted metadata history

Workspaces

Workspaces are included with Pro. Internal owners, admins, and members require Pro; external recipients and submitters stay outside the console.

  • Any Pro user can create or join workspaces
  • Internal Pro members only
  • External recipients and submitters do not consume seats
  • Enterprise for centralized billing or sponsored seats

How to choose

Pick the smallest plan that gives the control surface you need. External recipients and submitters do not need a workspace account just to open or submit a secret; internal owners, admins, and members need Pro.

  • Free for one-off text
  • Pro for recurring individual and workspace use
  • Automation identities for agents and scripts
  • Enterprise for assisted deployment and identity planning

Use case map

Match the package to the handoff. Send covers one-way delivery, Request Credentials covers receiving a secret from someone else, Private Rooms cover short two-party exchanges, and API or MCP workflows cover automation.

  • Send: /product/send
  • Request Credentials: /product/request
  • Private Rooms: /product/private-rooms
  • API and MCP: /docs/api and /docs/mcp
  • Security model: /security

Current buying path

Pro and automation identity add-ons start in the app when checkout is available. Enterprise is reviewed directly so support needs, workspace rollout, procurement, and identity planning are clear before use.

  • Start Pro in the app
  • Confirm the account token that owns the purchase
  • Add identities for agents and scripts
  • Use contact for Enterprise

Automation identities

Use one scoped, revocable identity per agent, script, CI workflow, MCP runtime, or integration instead of sharing a human login.

  • 1 included with Pro
  • Extra identity add-ons
  • 15-identity pack for agent fleets

FAQ

Which plan should I start with?

Use Free for a one-time text secret. Use Pro when you need recurring individual capacity, files, request links, Private Rooms, workspaces, API, CLI, MCP, and one included automation identity. Contact us for Enterprise when procurement, SSO, SCIM, DPA, SLA, private deployment, or volume identity planning matters.

Do external recipients consume seats?

No. External recipients who open a secret or submit through a request link should stay outside the workspace console. Internal workspace owners, admins, and members need Pro.

Where does checkout happen?

Checkout starts from the app when payment is available. The purchasing account token owns the paid access, so the user should save that token and complete Security Kit after activation.

How many automation identities are included?

Pro includes one automation identity. Extra identities can be added individually or through the 15-identity pack.

Who consumes seats?

Internal workspace owners, admins, and members need Pro. External recipients, request submitters, and invited one-time room participants do not.

Can API, CLI, or MCP workflows be discussed?

Yes. The public docs at /docs/api, /docs/cli-safe-guide, and /docs/mcp describe the operating boundaries for automation identities.

Is payment data connected to secret content?

Billing records contain the information required to process the purchase. They must not contain secret values, encryption keys, access codes, or complete private links.