Beta.The API can still change before 1.0, so read the release notes before you upgrade. Database migrations run when the server starts: back up first.Releases
Open sourceHosted or self-hostedOne Docker image and Postgres
Every support channel, answered as one chat.
Yuva puts e-mail, live chat and in-app messages from all of your products into one inbox for your team. Open source, one Go binary with Postgres.
Already have an account?Log in
Channels
Connect a support address, a chat widget for your website or the SDKs for your apps.
Everything around the inbox
The tools a support team usually rents separately, in the same server and the same panel.
Team mail
Shared addresses like sales@ and people's own mailboxes, in the inbox your team already uses. Yuva is the mailbox: your domain's mail is routed to it. It is not an IMAP server for mail apps. Read the guide →
Contacts
One profile for each person, whichever channel they write from. Read the guide →
Team and reports
See how support is going and who is on the team. Read the guide →
Help center
Add ratings and a discussion area to your own documentation pages. Read the guide →
Broadcasts
Send newsletters to your mailing lists and see what readers do with them. Read the guide →
E-mail templates and designer
Build e-mails in the designer or start from a free template. Open the templates →
Analytics
See who visits your sites and apps, with no cookies and no stored IP addresses. Read the guide →
Status pages
A public page for the state of your products, kept in the same inbox as your support. Checks keep it current and subscribers hear by e-mail. Open status pages →
AI assistants and MCP
Connect Claude, ChatGPT or Cursor. A teammate reviews and sends what they draft. Open AI assistants →
Moving in
Bring your mail and support history over. Yuva only reads at the source. Read the guide →
Developers
Every part of Yuva has a typed contract and a small, documented integration.
curl https://support.example.com/v1/conversations?status=open \ -H "Authorization: Bearer $YUVA_API_KEY"
- API
- with workspace API keys
- Webhooks
- signed, for every new message
- Identity tokens
- so users write as themselves
Self-hosting and open source
One small server runs all of it. The server is open source, and the SDKs carry no copyleft.
One binary
and Postgres
AGPL-3.0
server and panel
MIT
SDKs and API contract











