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
Pricing
Choose the right Shhhs plan for each secret handoff
Compare the safest buying path for the way you share secrets today. Free covers one-off text handoffs, Pro fits recurring individual work, and Team or Enterprise should start with contact when workspace operations, APIs, request intake, identity planning, or deployment review matter.
Packages
Pro Monthly
For recurring individual work with files, request links, rooms, and a personal console.
Current price in app- Recurring capacity
- Files
- Opening codes
- Request links
- Private Rooms
- Personal console
Team
Team plans are being updated. Contact us for current options.
Contact us- Workspace review
- API keys
- Request intake
- Seat planning
- Team operations
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
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
Team
Team is for internal workspace operations, not external recipients. Team plans are being updated; contact us for current options while billing, entitlement, and workspace-seat gates are completed.
- Workspace and internal member review
- API keys, request intake, and event notifications
- Admin workflow and seat planning
- No public Team self-service checkout yet
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 are the people who need workspace access.
- Free for one-off text
- Pro for recurring individual use
- Team for internal workspace operations
- 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 checkout is shown from the app when the billing gate is enabled. Team and Enterprise are reviewed directly so the active configuration, current price path, and workspace needs are clear before use.
- Start in the app
- Confirm the account token that owns the purchase
- Use contact for Team or Enterprise
- Avoid stale public pricing
What is hidden for now?
Team Pack prices, seat rules, renewals, grace states, and self-service checkout remain hidden until their release gates are fully validated.
- No Team Pack prices
- No seat-rule promises
- No self-service Team checkout claim
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, and a personal console. Contact us for Team or Enterprise when workspace operations, APIs, identity planning, or deployment review matter.
Do external recipients consume Team 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 are the people who need Team access.
Where does checkout happen?
Checkout starts from the app and is shown only when the billing gate is enabled. The purchasing account token owns the entitlement, so the user should save that token and complete the Security Kit flow after activation.
Are Team prices public now?
No. Team plans are being updated. Contact us for current options.
Why are Team Pack details hidden?
Billing, entitlement, and workspace-seat release gates must be fully validated before public self-service Team pricing is published.
Can API, CLI, or MCP workflows be discussed?
Yes. Contact us for current Team options and active capabilities. The public docs at /docs/api, /docs/cli-safe-guide, and /docs/mcp describe the operating boundaries.
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.