Cryptgeon Hosting

How Cryptgeon works

Cryptgeon encrypts note content in the browser before it reaches the server. The hosted service retains encrypted data and returns a unique link, while the decryption key remains in the link fragment handled by the recipient browser. A note can be constrained by view count or an expiration period, after which it is no longer available through the application.

The interface accepts text and files within the configured size limit. The catalogue sets a 4 MiB limit and uses Redis with persistence for server-side ciphertext and metadata. There is no account system in this template, so anyone who knows the application address can create a note even though only a holder of a complete note link can decrypt that note.

Key Cryptgeon features

Client-side encryption reduces the amount of readable secret material exposed to the application server. View and time limits support one-off transfers, while a simple page keeps the sender workflow short. The recipient must still trust the browser session and verify that the link arrived through the intended communication channel.

Cryptgeon is not a permanent document vault, collaboration area, or identity-verification system. A recipient may copy content before expiry, and the application does not prove who opened a link. The public app address should remain private when the owner does not want unrelated visitors creating encrypted notes on the same installation.

Who uses Cryptgeon

Administrators use Cryptgeon to pass temporary credentials, recovery material, API secrets, or small configuration snippets without placing the plaintext directly in ordinary chat history. Support teams can share one-time values with a known customer, while developers use it for brief secret exchange during an incident or migration.

The tool is unsuitable for large files, long-term record keeping, or a process that requires recipient identity, audit approval, or legal retention. Senders should avoid including unnecessary context in the note, deliver the link through a trusted path, and rotate a credential after use when the underlying system permits it.

Self-hosting Cryptgeon: requirements and cost

Cryptgeon demand follows note creation rate, encrypted payload size, retrieval traffic, expiry processing, Redis activity, and concurrent browser sessions. The catalogue packages persistent Redis as an internal data service, while PostgreSQL or MariaDB is Not required and no relational-database step-up applies.

AvaHost maps Cryptgeon to Plan 1 at €2. The one-click stack includes persistent Redis as packaged support data services. Cryptgeon includes custom-domain HTTPS, automatic application updates, and scheduled backups. The catalogue sets a 4 MiB payload limit and exposes no login. Anyone with the application address can create a note, so keep the service hostname controlled and use each generated note link only through an appropriate trusted channel.