Discuss your project
TOMORISGRID.WHISPER

PUBLICLY AVAILABLE

Zero-knowledge secret sharing.

GRID.WHISPER shares passwords, credentials and text secrets via client-side encrypted links that are limited by time and number of views.

Open productAll products

IN BRIEF

What is GRID.WHISPER?

GRID.WHISPER is a zero-knowledge secret pusher. Encryption happens in the browser; the key stays in the URL fragment and never reaches the TOMORIS server.

  • THE TASK

    What problem does GRID.WHISPER solve?

    Passwords and credentials too often end up permanently in emails or chats. A secure handover channel has to limit the content and must not know any plaintext itself.

  • AVAILABILITY

    PUBLICLY AVAILABLE

    Publicly usable as a web application for text secrets; the key stays in the URL fragment of the browser.

Available

Your next step.
Agreed in concrete terms.

Open GRID.WHISPER to share a text secret with limits on time and number of views.
  • Encrypt a text secret in the browser
  • Set the expiry and the view limit
  • Pass the generated link specifically to the authorized person

The documented functionality covers text secrets. Check the recipient and the chosen transmission channel before sharing.

Open product

FEATURES & MODULES

What the solution
delivers day to day.

The specific scope depends on the environment, approvals and the agreed operating model.
  • 01

    Client-side encryption

    AES-256-GCM in the browser; the server stores only ciphertext and metadata.

  • 02

    Limited sharing

    Expiry time and number of views determine the lifetime of the secret.

  • 03

    Click-to-reveal

    Link previews do not use up a view; the recipient confirms deliberately.

  • 04

    Controlled deletion

    After expiry or the last view, the stored ciphertext is permanently deleted.

IN OPERATION

How GRID.WHISPER
fits into everyday work.

  1. 01

    Enter the secret

    The browser generates the key and encrypts the content locally.

  2. 02

    Share the link

    Only ciphertext and limits go to the server; the key stays in the fragment.

  3. 03

    Retrieve deliberately

    The recipient actively reveals the secret; view counter and expiry are enforced.

WHO IS IT FOR?

For people who need clarity.

  • IT teams and service organizations
  • Companies that occasionally hand over credentials
  • Anyone who wants to share text secrets deliberately rather than permanently

RESULT

What GRID.WHISPER improves in concrete terms.

  1. 01No plaintext secret on the server
  2. 02Fewer permanent credentials in messages
  3. 03Traceably limited sharing

ENVIRONMENT & INTEGRATIONS

Close to the process
instead of isolated.

We only connect the solution where data responsibility, identity and technical impact are clearly regulated.
  • Web Crypto API
  • Public web interface
  • Programmable API, enabled when needed

SUMMARY

GRID.WHISPER at a glance

What is it?
GRID.WHISPER is a zero-knowledge secret pusher. Encryption happens in the browser; the key stays in the URL fragment and never reaches the TOMORIS server.
Who is it for?
IT teams and service organizations; Companies that occasionally hand over credentials; Anyone who wants to share text secrets deliberately rather than permanently.
What does it deliver?
No plaintext secret on the server; Fewer permanent credentials in messages; Traceably limited sharing.
How is it available?
PUBLICLY AVAILABLE — Publicly usable as a web application for text secrets; the key stays in the URL fragment of the browser.

CLEAR ANSWERS

Frequently asked
questions.

Can TOMORIS read the shared content?

No. The decryption key technically never reaches the server.

Can I share files?

No. WHISPER is deliberately limited to passwords, credentials and text secrets.

Does a link preview use up the view?

No. Retrieving metadata and deliberately revealing the secret are separate steps; the counter changes only after confirmation.

RELATED SOLUTIONS

A good fit.

KNOWLEDGE & CONTEXT

YOUR NEXT STEP

Find the right fit
for GRID.WHISPER.

We clarify the goal, environment, integrations and the permissible next step.

Discuss your use case