Should you build your own Inbox Zero?
AI email assistant that organizes inboxes, drafts replies, blocks cold email, and automates cleanup
The personal Gmail loop is a weekend project: classify new mail, apply labels, draft replies, and surface bulk cleanup. The gap is making it trustworthy enough to sit inside a real inbox every day: OAuth setup and review, token refresh, provider quirks, continuous sync, retries, rate limits, security, and integrations. Inbox Zero itself is open source, so anyone wanting the full product should self-host the official code instead of rebuilding all of it.
ENOriginal research content in English. Original prompt preserved in English.
Build me a self-hosted personal Gmail assistant that covers the core Inbox Zero loop.
Use Node 22 + TypeScript + Fastify + better-sqlite3; server-rendered HTML and vanilla JS, no React.
Run on localhost by default, with one Dockerfile for an always-on VPS behind Caddy.
Support exactly one Gmail or Google Workspace mailbox through the Gmail API.
Use a Google OAuth client from .env and request only gmail.modify and gmail.compose; store the refresh token encrypted with an APP_SECRET.
On first run, import 14 days of mail; then poll Gmail history every two minutes and persist the last history ID.
Deduplicate jobs by Gmail message ID, use exponential backoff for transient API failures, and surface a failed-jobs page.
Rules live in rules.md: label definitions, priority senders, newsletters, cold email, and messages that need a reply.
For each new thread, call the OpenAI API with the thread text plus rules.md and require validated JSON: labels, priority, needsReply, summary, and optional draftReply.
Apply Gmail labels automatically, but never archive, delete, unsubscribe, or send without a click.
When needsReply is true, create or update a Gmail draft in the original thread; never send mail from the app.
Build one dashboard with Priority, Needs reply, Newsletters, Cold email, and Failed jobs views.
Add a bulk-cleanup screen grouped by sender with message counts and List-Unsubscribe support; show the exact action and require confirmation.
Add a small analytics page: daily received count, top senders, category totals, and estimated time saved.
Store only IDs, classifications, job state, and draft metadata in SQLite; do not persist full message bodies after processing.
Redact tokens and email contents from logs; add CSRF protection and bind the admin UI to localhost unless ADMIN_TOKEN is set.
Include fixture-based tests for classification parsing, idempotent sync, label application, draft creation, and unsubscribe confirmation.
Out of scope: Outlook, multiple accounts, mobile apps, Slack/Telegram, calendar context, attachment filing, multi-user accounts, billing, and telemetry.
README: exact Google Cloud OAuth setup, scopes and redirect URI, .env example, how to revoke access, Docker/Caddy deployment, backups, and expected LLM costs.
Return finished code with migrations and scripts for dev, test, and start; no pseudocode or TODOs.The prompt opens pre-filled in your agent. Review it before running.
What would building your own look like?
Watch one Gmail inbox, classify and label new threads, create reply drafts for review, and group noisy senders for cleanup.
What you will need
- Google Cloud OAuth client
- OpenAI API key
- Node 22
- always-on machine or VPS for continuous processing
They pay for the two-click setup and the confidence that a security-sensitive inbox integration will stay synced, recover from provider failures, and keep its integrations working. People who prefer to own the infrastructure can self-host the official open-source product instead of maintaining a smaller rewrite.
xOutlook and reliable multi-account support
xbattle-tested token refresh, push sync, retries, rate-limit handling, and background uptime
xreply-in-your-voice learning with deeper mailbox, calendar, and knowledge-base context
xSlack and Telegram chat, mobile access, meeting briefs, and attachment filing
xhosted security, compliance, team administration, monitoring, and support
Prefer something ready-made?
Inbox ZeroThe exact organizer, drafter and cold-email blocker, free to self-host below five business users; OAuth and Docker remain unpaid labor.Free↗License, setup, and limitations for each alternative.
How much does Inbox Zero cost?
- Monthly billing
- $20/mo$20/mo · per person
- Per year
- $240/yr$240/yr
- On a Brazilian card, with 3.5% IOF
- R$105/moR$1,254/yr
Saved to My list. You will see a notice on this site when the price changes.
You complete the purchase on Inbox Zero’s site. Vibe Radar does not handle payments.
| Plan | Monthly | Annual (per month) | What is included |
|---|---|---|---|
| starter | $20/user≈ $20 | - | 1 paid user seat; limited knowledge base; no published email-volume or AI-action quota. |
| plus | $35/user≈ $35 | - | 2 email accounts included per user; unlimited knowledge base; no published email-volume or AI-action quota. |
| professional | $50/user≈ $50 | - | At least the 2 accounts/user included in Plus; team-wide analytics; no published email-volume or AI-action quota. |
| enterprise | custom | - | Custom plan for SSO, SCIM, on-premise deployment and dedicated account management; numeric caps not published. |
Free tierno permanent hosted free tier; 7-day trial on hosted plans; the open-source edition can be self-hosted with Docker and Node.js 24+ but requires your own infrastructure and AI provider
Billing termsmonthly + annual (vendor says annual saves up to 20%, but exact annual plan amounts were not exposed); changes are prorated; cancel anytime; 14-day refund window
Additional costsSelf-hosting avoids the hosted subscription but shifts cost to your own server, database/queue services and LLM usage. Hosted tiers publish no email-volume or AI-usage allowances, so potential usage limits or extra-account pricing could not be verified.
verified 2026-08-12 · source ↗
Is it cheaper to build or buy Inbox Zero?
Adjust the numbers: hours to build, your hourly rate, running costs and the subscription price.
Over 24 months, subscribing is cheaper.
Starting hours estimated from the analysis (weekend). Does not price what you give up (support, integrations, security).
Can I rebuild Inbox Zero?
Kinda. The core of Inbox Zero is buildable in a weekend with the prompt on this page, but there are real gaps: Outlook and reliable multi-account support, battle-tested token refresh, push sync, retries, rate-limit handling, and background uptime. Read the honest list above before committing.
How much does Inbox Zero cost?
Inbox Zero costs about $20/mo (Starter, checked 10/20/2026), which is $240 per year.
What do I lose by replacing Inbox Zero?
Honestly: Outlook and reliable multi-account support; battle-tested token refresh, push sync, retries, rate-limit handling, and background uptime; reply-in-your-voice learning with deeper mailbox, calendar, and knowledge-base context; Slack and Telegram chat, mobile access, meeting briefs, and attachment filing; hosted security, compliance, team administration, monitoring, and support. If any of those are load-bearing for you, keep paying.
Is there an open-source alternative to Inbox Zero?
Yes: Inbox Zero (The exact organizer, drafter and cold-email blocker, free to self-host below five business users; OAuth and Docker remain unpaid labor.) The prompt is for when you want it exactly your way.