NShroud

nshroud.com ↗

Pre-1.0 encrypted team chat for organizations handling sensitive information.

SI Score
75/100
Pricing
Not confirmed
Free plan
Not confirmed
Sign-up required
Not confirmed

Ask SI about NShroud

Answers use saved listing facts and recorded sources.
Homepage screenshot
Screenshot of the NShroud homepage

What it does

NShroud is a private team messenger built around end-to-end encrypted conversations, files, and calls. The vendor offers a self-hosted container or a managed deployment, and its site advertises signed desktop downloads while marking some other client platforms as in development.

Keep message keys on participants' devices

NShroud is designed so that messages and files are encrypted before leaving a user's device; the vendor also says its one-to-one and group voice or video calls are encrypted. Its site lists group chat, direct messages, file sharing, and sign-in through Microsoft Entra, Google Workspace, or email and password. Organizations can self-host the container or ask the vendor to operate it.

Treat the project as early-stage software

The linked repository describes NShroud as pre-1.0 and actively developed, and says the source is available while license details are still to be determined. The homepage advertises Windows and Linux downloads and marks macOS and mobile apps as in development, while the repository README describes a broader desktop build; confirm supported clients before deployment. Enterprise pricing is scoped to the deployment and handled by sales. No client, server, or encrypted call was tested.

Strengths

  • The product describes end-to-end encryption for messages, files, and voice or video calls.
  • Organizations can choose to operate a container themselves or have the vendor run the service.
  • The site lists Microsoft Entra and Google Workspace sign-in alongside email and password.

Watch out for

  • The linked repository labels the project pre-1.0 and actively developed, so organizations should assess release stability before deployment.
  • The site's client availability statement conflicts with the repository README on macOS availability, and no mobile client is listed as released on the site.

Best for

  • Technical organizations that want encrypted team messaging and can evaluate a pre-1.0 deployment
  • Teams that need either a self-hosted container or vendor-operated service and use supported identity providers

Sources