One inbox for every product you run.

Why Yuva

Several products means answering people in several places.

Small teams rarely run just one product. There is an app, its website, a side project and the tool that pays the bills, and each one collects messages somewhere else.

Yuva gives all of it one home: every product is an inbox, every channel lands in the same conversation model, and the whole team answers from one panel on servers you control.

Channels

Every channel, one conversation model.

Live chat and asynchronous messaging differ only in settings. Whatever channel a conversation starts on, it looks and works the same in the panel, and each inbox chooses live or async.

Live chatLive chat and embedded threads

One web component loaded by one script tag. Use it as a floating launcher on a website, or embed a conversation thread inside your own product's panel.

• Shadow DOM: your styles stay out, the widget's styles stay in.
• Presence, typing and read receipts in live inboxes; an expected reply time in async ones.
• When the visitor has left, unread replies follow them by e-mail, and their answer continues the same conversation.
• Anonymous visitors, or signed-in users through an identity token from your backend.
• English and Turkish, left-to-right and right-to-left.

Widget guide

In-appIn-app messaging and feedback

Native SDKs for iOS (YuvaKit, SwiftUI) and Android (Kotlin, Jetpack Compose) give your app a conversation list, threads with attachments and a feedback form, or a headless client for your own interface.

• Feedback with a category (bug, idea, praise, other), screenshots and device details: app version, build, system, device and screen.
• The panel filters feedback by category and counts what is still open.
• Users write as themselves through a short-lived token signed by your backend; Yuva never sees your user database.
• Push stays yours: Yuva sends a webhook, your backend sends the notification through APNs or FCM.

Mobile SDK guide

For developers

Made to be embedded in your products.

Yuva is built for teams that make their own software. Every surface has a typed contract and a small, documented integration.

<script src="https://support.example.com/yuva.js" defer></script>
<yuva-chat channel="yuva_pk_xxxxxxxxxxxxxxxx"></yuva-chat>

import "github.com/productdevbook/yuva/sdk/go/identity"

token, err := identity.Sign(os.Getenv("YUVA_IDENTITY_SECRET"), identity.Claims{
	Subject:       user.ID,
	Email:         user.Email,
	EmailVerified: user.EmailConfirmed,
	Name:          user.Name,
	Attrs:         map[string]any{"plan": user.Plan},
})

import YuvaKit

let yuva = YuvaClient(configuration: YuvaConfiguration(
    serverURL: URL(string: "https://support.example.com")!,
    channelKey: "yuva_pk_xxxxxxxxxxxxxxxx",
    identityToken: { try await MyAPI.yuvaIdentityToken() }
))

YuvaConversationsView(client: yuva, openConversationId: $openConversationId)

val yuva = YuvaClient(
    context,
    YuvaConfiguration(
        serverUrl = "https://support.example.com",
        channelKey = "yuva_pk_xxxxxxxxxxxxxxxx",
        identityToken = { myApi.yuvaIdentityToken() },
    ),
)

YuvaConversationsView(client = yuva, openConversationId = conversationId, onClose = { finish() })

import "github.com/productdevbook/yuva/sdk/go/webhook"

body, _ := io.ReadAll(io.LimitReader(r.Body, 1<<20))
if err := webhook.Verify(os.Getenv("YUVA_WEBHOOK_SECRET"), r.Header, body, 5*time.Minute); err != nil {
	http.Error(w, "bad signature", http.StatusUnauthorized)
	return
}

Web widgetIdentity tokensMobile SDKsWebhooksOpenAPI

Security and privacy

Careful with what it holds.

A support inbox holds other people's words. Yuva is built with that in mind, and says plainly that it has not had an independent security audit yet.

Found a vulnerability? Report it privately through GitHub, not in a public issue. Security policy

Status and roadmap

Where it stands today.

Yuva is pre-alpha and built in the open. Versions start at 0.0.1, there is no 1.0 until the project is ready, and the first release, 0.0.1, is out now.

1. Done

   Foundation

   Go server, OpenAPI contract, migrations, job queue and CI.

2. Done

   Core model and sign-in

   Workspaces, roles, inboxes, channels, contacts, conversations, API keys, codes and passkeys.

3. Done

   Team panel

   List, search, threads, notes, labels, canned replies, realtime updates, Turkish and English.

4. Done

   E-mail

   Inbound through a Worker or any MTA, threading, quote stripping, SMTP, loop protection and bounces.

5. Done

   Web widget

   Live chat, embedded threads, identity tokens, presence and e-mail continuity.

6. Done

   Mobile SDKs, feedback and webhooks

   iOS and Android, feedback with device details, Standard Webhooks.

7. Done

   Member notifications

   Installable panel, Web Push, preferences per event and inbox, e-mail fallback.

8. Done

   First public release, 0.0.1

   Tagged v0.0.1 with its Docker image on GitHub Container Registry, after hardening sign-in, client sessions, ingress and attachment handling.

9. In progress

   First real use

   Running real support for a set of products on Yuva alone.

Later: a Helm chart and optional push sent by Yuva itself. Not planned for now: a CRM, marketing e-mail, a public knowledge base or social-media channels. Full roadmap