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.
team-dfw1 is in the mesh and the agent is reporting.
@michael backup drill at 15:00 — notes in thread.
What's in it
Public and private channels, 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. Built for teams whose messages contain actual work.
@mentions with autocomplete, per-channel rules (all, mentions, muted), and desktop push that stays quiet while you're already reading the conversation.
Attachments upload straight to any S3-compatible store. Bytes never rest on the application server's disk.
Full-text search across everything you're allowed to see, with phrase and exclusion syntax. History is only useful if you can find things in it.
A configurable retention window or indefinite-with-export, a one-command export of the whole workspace, and an audit trail of every administrative action.
Why self-host
Incident timelines, credentials discussions, customer details, legal questions, the unfiltered record of how decisions got 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 — database, TLS and backups included. 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
✓ Automatic TLS, versioned migrations at boot
✓ Nightly encrypted database backups to your bucket
✓ No telemetry, no license checks, no phone-home
✓ Single sign-on against any OIDC provider
✓ Custom branding — your name, logo and colours
Storage
Nevrit speaks exactly one storage API: generic S3. Object keys are portable — no provider, region or account baked into them. The same deployment works against any of these:
Moving providers is a data copy and a config change — never a migration of the application.