About
Email infrastructure
you can actually own.
Teams that work shared email face a bad choice. Stay in provider webmail and you end up sharing passwords, forwarding threads, and losing track of who replied. Move to a hosted helpdesk and your mail becomes tickets in someone else’s database, priced per agent seat.
TELVRIX takes a third path: keep the mail at your provider, and add the team layer on infrastructure you control. A workspace with roles and audit trails on top of plain IMAP — readable by your team, operable by your admins, ownable by you.
It is a unified inbox over any IMAP provider, team workspaces with enforced roles, shared mailboxes without shared passwords, and an operator console for the people running it. Nothing more is claimed than what is built.
Principles
The five things we won't trade.
01
Your provider keeps your mail.
TELVRIX connects over IMAP and SMTP — the protocols every provider already speaks. There is no migration, no proprietary mail store you can’t leave, and no OAuth scope that hands over account control. Stop using TELVRIX tomorrow and your mail is exactly where it always was.
02
Self-hosted means operable.
Software you run yourself must be honest about its runtime. TELVRIX ships a real operator console — live queue counts, worker heartbeats, provider health, incident workflows — and a public status page that reads live state instead of displaying synthetic uptime numbers.
03
Security is enforced in code.
Credentials are encrypted with AES-256-GCM and excluded from logs, caches, and admin views. Permissions are checked server-side on every route. Support access is scoped and audited. None of this is a policy document — it is the implementation.
04
No fake anything.
The product does not show capabilities it doesn’t have. Roadmap items are labeled as roadmap on the pricing page, the beta page lists what works and what doesn’t, and the status page will tell you when something is down.
05
Email is not ad inventory.
TELVRIX stores message content in your database to power your inbox and your search — and for nothing else. No analysis for advertising, no profiling, no selling data.
A short history
From first sync to closed beta.
Early May 2026
The core mail platform.
Multi-folder IMAP sync, full sending, full-text search, drafts, labels — and AES-256-GCM credential encryption from day one.
Mid May 2026
Workspaces and teams.
Organization workspaces, tokenized invitations, four roles with server-enforced permissions, shared mailbox visibility.
Late May 2026
The operator console.
Admin overview, queue monitoring, provider health, incidents and investigations — live state, no synthetic metrics.
June 2026
Closed beta, public platform.
Audit log with CSV export, plan limits enforced across the API, this public site. Billing built but inactive — beta is free.
The beta page lists exactly what works, what is partial, and what is not built. The changelog tracks what shipped, and the roadmap shows what is coming — labeled as future work, not sold as present capability.
A small note
Beta access is free and reviewed manually. Bring a mailbox you actually use — that is the honest test.