self-hosted · deterministic-first · telegram-first

Self-hosted email triage for Windows.
One clear Telegram signal per email.

Letterbot connects to your IMAP inboxes, classifies mail locally, and sends only relevant messages to Telegram with priority, summary, and suggested next action.

Deterministic by default. Optional AI enhancement for harder messages. No vendor cloud. No subscription. Read-only cockpit on localhost:8787.

Read-only IMAP Multi-inbox routing Telegram actions Local SQLite
Download and install View source on GitHub
1. Download ZIPGrab the latest release from GitHub. No subscription gate and no signup.
2. Edit configAdd IMAP credentials and your Telegram bot token. Keep everything on your own machine.
3. Run and watchStart Letterbot and open the local cockpit to confirm health, events and routing.
Latest release Issue tracker See the cockpit
✉ Letterbot ● local
🔴 urgent · invoice

SoftMacro LLC — Invoice #2024-047

Action: pay by Apr 15 · 87,500 ₽

📎 invoice_april.xlsx

🔴 High 🟡 Review ⏰ Snooze 2h
09:14
🟡 important · contract

Jimmy Irish — Contract for review

Action: sign and return by Friday

📅 Tomorrow ✍ Mark done
09:16
📊 weekly digest

3 invoices · 1 overdue obligation · 2 replies pending

Mon 08:00
$0free forever
∞IMAP inboxes
localprocessing + storage
read-onlyno mail moves or deletes

proof, not just promises

Real local cockpit screenshots

The screenshots below are from a running Letterbot instance on 127.0.0.1:8787. They show the operator view that verifies health, message flow, fallbacks and auditability without exposing anything to the public internet.

Letterbot cockpit home view with system status, emails today and latency widgets

Home cockpit

A single operator screen with runtime status, email volume, high-priority flow and fallback visibility. This is where you verify that the system is alive before trusting it with your inbox.

Letterbot health cockpit showing component matrix and golden signals

Health cockpit

Component matrix, delivery signals and recent incidents in one place. You can quickly tell whether IMAP, database, Telegram or optional AI are healthy enough to keep routing messages.

who it fits best

Best for people who want control, not another inbox SaaS

Great fit

  • Freelancers who miss invoices, contracts or urgent replies in noisy inboxes
  • Operators who want a read-only local layer between IMAP and attention
  • Teams routing multiple inboxes into different Telegram chats
  • Privacy-sensitive users who do not want email content sent to a vendor cloud

Not the best fit

  • If you want a hosted SaaS with zero setup, Letterbot is intentionally not that
  • If you need email sending, reply drafting or mailbox mutation, the product is designed to stay read-only
  • If you want Outlook-first enterprise workflow over IMAP, a different tool may fit better
  • If you never use Telegram, the main operator experience will feel less compelling
Compare with alternatives Read the privacy model

deterministic first

Works without paid AI

The core workflow is deterministic: IMAP intake, feature extraction, scoring, Telegram notification, and cockpit visibility. Optional AI can improve summaries for complex messages, but the core triage loop keeps running even when external AI is disabled or unavailable.

  • No mandatory OpenAI dependency
  • Graceful fallback when optional AI is unavailable
  • Reason codes and observable decision paths
  • One-message Telegram workflow instead of a second inbox UI

what you actually get

Core capabilities

📨

IMAP intake

Connect multiple inboxes, keep access read-only, and route each account into the right Telegram destination.

📎

Attachment extraction

Read PDFs, spreadsheets and documents locally to surface amounts, dates and obligations with better context.

📲

Telegram actions

One email becomes one action-oriented message with priority controls, snooze and context restoration.

🧭

Decision trace

Audit why something became urgent, important or low instead of trusting a black box.

🩺

Local observability

Use the cockpit to inspect health, incidents, latency and event history on your own machine.

🌍

EN/RU workflow

English and Russian support across notifications, digests and operator flows.

See the full feature list

open source proof points

Verify the project before you trust it

Repository Inspect the code, licenses, docs and release history before you install anything. Releases Download the latest build and review packaging changes or version notes. Issues See what users report, what is being fixed and how the maintainer responds.

quick answers

Questions that decide the purchase

Does Letterbot require ChatGPT or a paid AI service?

No. The deterministic pipeline works without paid AI. Optional AI can be enabled for harder summaries, but the core triage loop stays local and useful on its own.

Where do my emails go?

They stay between your mail server and your own machine. Letterbot reads through IMAP, stores local metadata for the workflow, and exposes a cockpit on localhost.

Can I route multiple inboxes to different Telegram chats?

Yes. Multi-inbox routing is one of the core reasons to use Letterbot: one instance can separate work, personal and alert traffic into different Telegram destinations.

Is it read-only?

Yes. The product is designed to classify and notify, not to move, delete or send email. That constraint is part of the trust model.

Open the full FAQ