Yuva

What is Yuva about?

Yuva provides a single shared inbox for every product a team runs. It consolidates customer communications across email, live‑chat widgets, in‑app messages and feedback, while also offering tools for newsletters, help‑center publishing, status pages, product roadmaps, and cookieless web analytics. The platform is open‑source, self‑hosted (Docker + PostgreSQL), and includes an MCP endpoint for AI‑assistant integration.

How to use Yuva?

1. Deploy – Create a compose.yaml and .env (see the quick‑start guide) and run docker compose up -d.
2. Bootstrap – Initialise the first admin with docker compose exec yuva /yuva bootstrap --email you@example.com --workspace "Example".
3. Configure HTTPS – Place the service behind a TLS‑terminating proxy (e.g., Caddy, Nginx) and sign in via the emailed magic link.
4. Add inboxes – In the web panel, create an inbox per product, customise branding, working hours, and team members.
5. Integrate – Use the provided REST API, SDKs (Go, JavaScript, Swift, Android) or the MCP /mcp endpoint to connect AI assistants, widgets, or other services.

Key Features of Yuva

• Multi‑channel conversations: Email, live‑chat widget, mobile/in‑app messaging, and feedback all appear in one thread.
• Shared inbox per product: Independent branding, language, support hours, and team permissions.
• Marketing suite: Mailing lists with consent tracking, template‑based email designs, broadcast campaigns, deliverability testing, and detailed reports.
• Publishing tools: Self‑hosted help center, documentation pages, status pages, roadmap board, and "What’s New" changelog.
• Cookieless analytics: Privacy‑first website/app analytics and support‑impact reports.
• Migration utilities: Import historic mail and tickets from Gmail, Microsoft 365, Yandex, iCloud, Zoho, any IMAP server, Zendesk, Help Scout, etc.
• Extensible API & SDKs: OpenAPI contract, scoped keys, signed webhooks, identity tokens, headless mode, and MCP server for Claude, Cursor, VS Code and other assistants.
• Self‑hosted simplicity: One Docker image, PostgreSQL, optional Helm chart for Kubernetes.

Use Cases of Yuva

• Customer support teams needing a unified view of all inbound channels without switching tools.
• Product teams that want to publish roadmaps, status updates and changelogs alongside support.
• Marketing departments managing newsletters, bulk email broadcasts, and consent‑aware mailing lists.
• Developers building AI assistants that can read/write draft replies via the MCP endpoint.
• Privacy‑focused organizations requiring cookieless analytics and on‑premise data residency.

FAQ from Yuva

• Is Yuva production‑ready? It is in pre‑alpha/beta; the API may change before 1.0 and the code has not undergone an independent security audit.
• What databases are supported? PostgreSQL is the only supported database.
• Can I run Yuva on Kubernetes? Yes, a Helm chart is provided (oci://ghcr.io/productdevbook/charts/yuva).
• Are there SDKs for front‑end integration? Yes – JavaScript/TypeScript (npm install useyuva), React shadcn/ui components, iOS/macOS Swift package, Android Maven artifact, and Go SDK.
• How is data privacy handled? All data stays on the host’s infrastructure; analytics are cookieless and consent is recorded for every subscriber.
• How do I enable AI‑assistant integration? Deploy the MCP server (/mcp endpoint) or use the bundled yuva.mcpb binary from a release; then configure assistants with OAuth credentials.

Yuva

One inbox for every product you run.

Website · Docs · API · Releases · Roadmap · X

Yuva is open-source customer messaging for teams that run several products. Support e-mail, live chat, in-app messages and feedback from every product land in one shared inbox, next to the newsletters, help center, status pages and analytics you send and publish from the same place.

You host it yourself: one Docker image and Postgres.

[!WARNING] 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. The code has not had an independent security audit.

Features

Conversations	One inbox per product with its own branding, language, hours and team. E-mail, live chat, in-app messages and app feedback in one thread, with notes, labels, mentions and bot drafts a member reviews.
Reach	Mailing lists with consent records and imports, e-mail designs from templates, broadcasts with approval and reports, and a deliverability check.
Publish	Help center, documentation pages, status pages on your own domain, a roadmap board and What's new.
Insights	Cookieless analytics for websites and apps, and a support report that ranks pages by the conversations they cause.
Move in	Migrations of history and live mail from Gmail, Microsoft 365, Yandex, iCloud, Zoho, any IMAP server, Zendesk and Help Scout. The old mailbox is only read.
Build on it	A REST API with scoped keys, signed webhooks, identity tokens, headless mode, and an MCP server with OAuth for Claude, Cursor, VS Code and other assistants.

Built with Go, Postgres and a React panel, shipped as one Docker image.

Quick start

1. Write compose.yaml and .env from the install guide.

2. Start it:

   docker compose up -d
   

3. Create the first owner:

   docker compose exec yuva /yuva bootstrap --email you@example.com --workspace "Example"
   

4. Put it behind HTTPS and sign in with the code that arrives by e-mail.

On Kubernetes, install the Helm chart oci://ghcr.io/productdevbook/charts/yuva; see Kubernetes with Helm.

SDKs and clients

For	Install	Guide
Web: <yuva-chat>, headless client	npm install useyuva	Web widget, Headless
React and shadcn/ui	npx shadcn@latest add https://useyuva.com/r/yuva-discussions.json	shadcn registry
iOS and macOS	Swift package https://github.com/productdevbook/yuva.git, product YuvaKit	Mobile SDKs
Android	implementation("com.github.productdevbook:yuva:v0.0.32")	Mobile SDKs
Go	go get github.com/productdevbook/yuva/sdk/go	Go SDK
AI assistants	/mcp on your server, or yuva.mcpb from a release	MCP

Working projects are in examples.

Privacy and security

• You host it: conversations, contacts and files stay on your servers.
• Analytics set no cookies and keep no cross-site identifiers; see analytics privacy.
• Every subscription records who consented, when and where, and lists export with that record.
• For assistants, customer text is marked as untrusted data, and their replies are drafts unless you allow sending.
• Report vulnerabilities privately as described in SECURITY.md.

Documentation

Guides, the API reference and examples are at useyuva.com/docs, and in docs/ (also in Turkish and German). How it is built: architecture. What is next: roadmap. What changed: GitHub Releases.

Community and contributing

Read CONTRIBUTING.md first; contributions are made under the CLA. For a local server with Postgres and Mailpit, which catches every mail it sends, run docker compose -f deploy/compose.yaml up -d. Ask questions and report bugs in issues, and follow @useyuva for news.

License

The server and panel are AGPL-3.0. The SDKs (sdk/) and the API contract (openapi/) are MIT, so you can ship them in closed-source apps. Details in LICENSING.md; name and logo in TRADEMARK.md.