TELVRIX · Self-hosted email operations · Closed beta

The email workspace
your team actually owns.

A self-hosted workspace for shared mailboxes. Quieter than a helpdesk, built on the IMAP accounts your team already runs.

By invitation · No payment during beta · IMAP + SMTP, any provider

TELVRIX — Inbox · Acme Support · support@acme.com
Inbox5 unread · synced
Dana Whitfield09:58
Re: Order #1042 — missing item
Support
Marcus Oyelaran09:41
Invoice 2026-118 — confirmation
Billing
Priya Natarajan09:14
Onboarding call follow-up
Jonas Keller08:52
API webhook returning 410
Support
Renata Silva08:30
Re: Contract renewal
Fig. 01 — A shared workspace on a Tuesday morning. Stylized rendering.Self-hosted · your Postgres
Closed beta · access by invitationProtocols · IMAP + SMTP · any providerCredentials · AES-256-GCM at restDeployment · Self-hosted · your own database

Connects to the mail your team already runs

Gmail
MICROSOFT 365
Fastmail
ICLOUD MAIL
zoho mail
Custom IMAP

The premise

Most team-inbox tools are designed to host your mail. TELVRIX connects to yours.

Your mailboxes already live somewhere — Gmail, Outlook, a hosting panel, your own server. TELVRIX syncs them into one shared workspace without asking you to migrate, forward, or hand over DNS.

  • 01

    Your provider stays.

    TELVRIX speaks IMAP and SMTP to the mail server you already run. No migration, no MX changes.

  • 02

    One connection, whole team.

    The owner connects a mailbox once. Workspace members read its threads without ever seeing the password.

  • 03

    Sending is a grant, not a password.

    Composing from a shared address requires an explicit send grant, verified on every send.

  • 04

    Every action leaves a record.

    Membership, mailbox, and send events land in the workspace audit log on Business plans and above.

Workflow

A surface for working,
not just clearing.

Reply from the address the mail arrived on. Claim a conversation so the team knows it’s handled. Leave an internal note the sender never sees. Schedule the reply for the morning.

Workspace reference

Connect

Add a mailboxIMAP
AuthenticateApp password
Folder discoveryAuto
First syncMinutes
CredentialsAES-256

Share

Invite memberLink
Set role4 levels
Mailbox visibilityWorkspace
Send grantPer member
RevokeInstant

Operate

Full-text searchPostgres
Assign thread1 click
Internal notePrivate
Send LaterWorker
Audit logBusiness+
Connect a mailbox to a shared inbox in one sitting. The rest is keystrokes.Closed beta · Web

For the operator

Run it like infrastructure.

TELVRIX is software you deploy, not a tenant you rent. The admin console shows sync activity, background jobs, and connection health for every mailbox as they actually are — and says so plainly when something is not enabled.

LiveNo synthetic metrics. State is read on every load.
TELVRIX — Admin · Sync diagnostics

Mailbox sync

incremental · last run 2m ago

Send queue

0 pending · 0 failed

Background worker

scheduled delivery — not enabled

Provider connection

IMAP TLS · authenticated

From the TELVRIX principles

“What works, what is partial, and what is not built are published and kept current. The beta page is the contract.”

─── How it’s built, principle F


How it's built

Technical seriousness,
without the showmanship.

A · Self-hosted

Your app, your database, your keys.

TELVRIX runs as one web application against a PostgreSQL database you own. There is no shared tenant; your deployment holds every byte.

B · Standards

IMAP, SMTP, TLS — nothing exotic.

Gmail, Microsoft 365, Fastmail, Zoho, hosting panels, your own Dovecot. If it speaks IMAP, TELVRIX connects to it.

C · Shared access

Visibility and grants, not passwords.

Workspace-visible mailboxes share reading. Send grants share writing. Credentials are never distributed to members.

D · Search

Full-text across every synced thread.

Messages index into Postgres full-text search. Find a phrase from last year across every mailbox you can read.

E · Security

Encrypted at rest, audited in motion.

AES-256-GCM for stored credentials, TOTP two-factor with backup codes, role-based permissions, and a workspace audit log.

F · Honesty

The beta page is the contract.

What works, what is partial, and what is not built are published and kept current. No fake provider health, no pretend features.

Privacy & ownership

Your mail is yours.
We mean this literally.

TELVRIX does not read your mail for advertising and does not sell it. Message content is stored in your own database to power your inbox and your search — and for nothing else.

How access actually works

  • Credentials encryptedAES-256-GCM at rest
  • Never in logs or adminBodies, subjects, passwords excluded
  • Row-level securityNo cross-user reads
  • Shared sendingExplicit grant, every send

Built for your stack

It runs where your infrastructure runs.

One web application, one PostgreSQL database you own, and an optional background worker for scheduled delivery. Deploy it the way you deploy everything else — and keep the keys.

Web (Chromium, Firefox, Safari)Self-hosted deploymentPostgreSQL — yoursScheduled delivery — optionalAny IMAP provider

Your mail. Your servers.
One workspace.

TELVRIX is in closed beta. Apply for access, or sign in if you already have an invite. No payment required during beta.

TELVRIX — Self-hosted email operations for teams