@mailkite/mail is a MIT-licensed, framework-native inbox UI. Drop it into your app or self-host it to read, search, and reply to a MailKite mailbox — backed by IMAP/JMAP, with no mail server to run.
@mailkite/mail is MIT-licensed — read the code, audit it, fork it, and run it on your own infrastructure. No black-box webmail.
A component you drop into your existing app, not an iframe or a separate product. Styled to match, wired to your MailKite account.
Messages are served over standard IMAPS (and a JMAP gateway in beta), so the same inbox works from the UI, mobile clients, and your own code.
Mail lives on your own domain with SPF/DKIM aligned, stored on MailKite (or passed through) — not siloed in a consumer webmail provider.
Add the MX records (or start on a managed subdomain) and create a mailbox. Inbound mail is stored and ready to read.
Generate an app password in the dashboard for the mailbox — that's the credential the webmail UI and any IMAP client use.
Install the component, point it at your account, and you have a working inbox — read, search, compose, and reply.
A MIT-licensed inbox UI you embed or self-host — the same mailbox is also reachable from any IMAP client.
# Install the open-source webmail component
npm i @mailkite/mail
# It talks to your MailKite mailbox over IMAP/JMAP using an
# app password you generate in the dashboard — no mail server,
# no OAuth dance. Self-host the whole thing if you prefer.Yes — @mailkite/mail is MIT-licensed. You can read the source, embed it in your app, or self-host the entire UI. It talks to your MailKite mailbox over IMAP/JMAP.
No. MailKite handles receiving, storage, and IMAP/JMAP access. The webmail component is just the UI on top — you provide a domain and an app password.
Yes. Because it's backed by standard IMAPS, the same mailbox opens in Apple Mail, Thunderbird, or mobile — see the Mailboxes solution.
Start free on unlimited domains — no credit card. Or browse the other solutions.