heyflare

heyflare brings HEY's workflow to existing mailboxes: a Screener for first-time senders, an Imbox for people, The Feed for newsletters and Paper Trail for receipts. It adds a calendar and an AI assistant that works with the owner's own model API key.

A first-time sender waits in the Screener until the owner lets them in or screens them out, and that decision applies across every connected account. The Imbox has Reply Later, Set Aside and Bubble Up trays, and Bundles fold a chatty sender into one row. Gmail and Outlook connect over OAuth, other providers over IMAP and SMTP with an app password, and mailboxes on custom domains receive mail through Cloudflare Email Routing. The assistant opens in a side panel. It can search and read threads, screen senders, file mail, and draft replies or forwards in the owner's tone; nothing is sent until the owner presses Send, unless autonomous sending is turned on. It works with Anthropic, OpenAI, xAI, OpenRouter, Google Gemini or any OpenAI-compatible endpoint. Mail goes to the provider only when an AI feature runs, including the optional learning from sent mail that builds the assistant's memory. A calendar sits beside the mail with Google Calendar sync, subscribed .ics feeds, tasks, habits and a journal. Two-factor auth, keyboard shortcuts and a mobile layout are built in. Tauri wrappers exist for macOS and iPhone. On Cloudflare it is a single Worker with static assets, a D1 database, a cron trigger that syncs Gmail, Outlook and IMAP every minute, and an email handler for custom-domain mail. Besides the Deploy to Cloudflare button, npm create heyflare@latest walks through the same setup as a CLI wizard.

Built for: Individuals who like HEY's mail workflow but want to keep their Gmail, Outlook or domain addresses and run the client in their own Cloudflare account.

What you can use it for

• Screen unknown senders across Gmail, Outlook and IMAP accounts
• Read personal and custom-domain mail in one Imbox
• Draft replies with an AI model you choose and pay for
• Keep a calendar, tasks and habits next to your mail

Deploy

• One-click

  Branch main

  The Google OAuth fields can be left empty during the deploy. Open the workers.dev URL, create the owner at /setup, then add GOOGLE_CLIENT_ID and GOOGLE_CLIENT_SECRET to connect Gmail.

  Deploy to CloudflareDocs

Gmail needs a Google Cloud OAuth client with the Gmail and People APIs enabled, a consent screen that lists test users, and a redirect URI on the deployed host. Outlook needs a separate Microsoft Entra ID app registration.

What it needs to run

• D1 databasesheyflare-db

Good to know

One deployment serves a single owner. Until the Google OAuth app is published, Google limits refresh tokens for test users to 7 days. Custom-domain mailboxes cannot send until Cloudflare Email Sending or Resend is set up. Turning on Email Routing for a domain takes over all mail for that domain. SMTP cannot use port 25, which Cloudflare blocks; use 465 or 587. Connecting an account imports no history; only new mail syncs. AI features need an API key from one of the supported providers.

Cost on Cloudflare

Where this comes from

• Repositoryhttps://github.com/doable-team/heyflare
• App websitehttps://heyflare.email
• Documentationhttps://heyflare.email/docs

An alternative to HEY, Spark, Superhuman.