SELF-HOSTED TEAM CHAT · BY KEMIT SECURITY
Nevrit is team chat built by a security company for teams that can't put their internal conversations on someone else's cloud. Channels, threads, DMs, rich Markdown, mentions, search, and file sharing — running on your servers, storing to your buckets, purging on your schedule.
Public and private channels, one-level threads that keep noise out of the main flow, and direct messages with live presence and typing indicators.
Full Markdown with tables and quotes, fenced code blocks with syntax highlighting, and LaTeX math. Written for teams whose messages contain actual work.
@mentions with autocomplete, per-channel notification rules (all / mentions / muted), and desktop push that stays quiet while you're actively in the conversation.
Attachments stream straight to any S3-compatible store — R2, AWS, Backblaze, MinIO, on-prem Ceph. Bytes never sit on the app server's disk.
Full-text search across everything you're allowed to see, with phrase and exclusion syntax. Your history is only useful if you can find it.
A configurable retention window (or indefinite-with-export), a one-command export of the full workspace, and an audit trail of every administrative action.
Because your team's chat is your company's memory: incident timelines, credentials discussions, customer details, legal questions, the unfiltered record of how decisions were made. On a SaaS messenger that record lives in someone else's datacenter, under someone else's subpoena surface, priced per seat forever.
Nevrit deploys from a repo onto a plain Linux box in one command — Postgres, TLS, backups and all. No Kubernetes, no license server, no callback to us. If Kemit Security disappeared tomorrow, your chat wouldn't notice.
✓ One-command unattended install on a fresh VPS
✓ Caddy auto-TLS, versioned DB migrations at boot
✓ Nightly encrypted database backups to your bucket
✓ No telemetry, no license checks, no phone-home
✓ Custom branding — your name, logo and colors
✓ Web now; native iOS on the roadmap
Nevrit speaks exactly one storage API: generic S3. Object keys are portable — no provider, region, or account baked in. The same deployment works against:
Moving providers is a data copy and a config change — never a migration of the application.