Shared addresses like support@, answered as a team
UnInbox is email for teams that reply from common addresses such as support@, sales@ or billing@. Conversations land in spaces, where teammates comment on a thread among themselves, answer as the shared address and set a status that shows whether the email still needs handling. The homepage promises an end to "FWD:" and "RE: RE: RE:" chains. Unproprietary Corporation runs the hosted service and publishes the code under AGPLv3.
A screener for new senders and external SMTP sending
- Comments sit in the thread: a comment is a conversation entry just like a message, with its own visibility (private, internal participants, organisation or all participants).
- New sender screener: every contact has a screening status (pending, approved, rejected) and a type (person, product, newsletter, marketing).
- Statuses defined per space: each space sets its own named, colour-coded statuses, grouped as open, active or closed. A separate permission decides who may close a conversation.
- Addresses on demand: as many addresses as needed on a domain, plus a catch-all.
- Alongside an existing mail setup or in its place: a domain receives natively or through forwarding, and sends natively or through an external SMTP server.
No self-hosting guide and three commits since 2024
The repository description pitches UnInbox as an alternative to Hey, Front and Missive. The free hosted plan includes an @uninbox.me address. Pro, at $12 per user per month, adds custom domains; Enterprise starts at 30 users and adds a dedicated instance and SAML SSO.
The code is under two licences. The whole repository is AGPLv3 except the ee/ folder (Stripe billing and the command app), which is under a commercial licence. The README asks that any distributed fork stay public and requires a commercial licence to keep the code in a private repository. GitHub identifies no licence in this combined LICENSE file.
Running UnInbox takes five apps and five backing services. The TypeScript code (Next.js, Hono, tRPC, Drizzle ORM) is split into web, platform, mail-bridge, storage and worker. Around them sit MySQL, Redis, S3-compatible storage, Soketi for realtime updates and a Postal mail server for native sending and receiving. The app reaches MySQL only through PlanetScale's HTTP driver, so the local setup puts a simulator of that API in front of MySQL 8.
Self-hosting is undocumented. The README says it "will be possible" with some manual email configuration and sends people to Discord for production setups. The repository has no Dockerfile: the only docker-compose.yml, under packages/local-docker, starts the local development dependencies. Issue #784, opened in July 2025 by a user who cannot log in to their own instance, has had no reply from the maintainers. For customer support, LibreDesk is another AGPL shared inbox; it publishes its install procedure and ships as a single binary or a Docker image.
Development mostly stopped in September 2024. The repository has no releases and no tags. Since 14 September 2024 it has received three commits: a Next.js and Unkey security update on 29 January 2026, an architecture document the next day and a fix on 11 February 2026, the most recent one.
The January 2026 architecture document points to Vercel. PRD/2601-consolidate-arch.md plans to merge the services into three Vercel projects and to replace the BullMQ workers with Vercel Workflow. It puts the migration itself out of scope and says nothing about self-hosting.