Launching Amargi Hub: one sign-in for the whole suite

Today we're publishing the marketing site for Amargi, a unified product family with one sign-in, one billing layer, one AI fabric, and six (and counting) products that share all of it. This post is the why behind it.

The problem isn't which tool to buy

Every growing team hits the same wall around year two. The CRM, the WhatsApp inbox, the meeting tool, the email service, the ticketing system, the AI assistant, each one solid in isolation, none of them designed to work together. The integration layer becomes its own job. Customer records get duplicated. Billing arrives in six languages on six different days. AI ends up bolted onto each tool with its own opinions about your data.

We didn't build Amargi because we thought any one of those tools needed to be replaced with a slightly better version. We built it because the right unit of design was the platform itself, not the products that sit on top.

What "one platform" actually means

Most "platforms" are a marketing claim, a shared logo on a sign-in page, then six independent tools behind it. We took a stricter definition. For Amargi, "one platform" means:

• Federated identity, Hub issues a signed JWT, every product verifies it via a shared JWKS endpoint. No duplicated user databases, no session-sync.
• Unified billing, every billable operation across every product flows into one organization ledger. Token packs for tools, per-org licenses for platforms.
• Shared AI fabric, every product's AI agents run through the same Amargi Agents layer, with one capability manifest, one audit trail, one set of governance guarantees.
• Hard isolation, data boundaries at organization, workspace, and team level. Reach can't see Mail's data without explicitly going through Hub.

The payoff is that integrations become the default, not a project. A WhatsApp conversation in Reach hits a complexity threshold and opens an Escalate ticket with full context, without anyone writing an integration. A Meet recording flows into Agents for transcription, and the action items become Escalate tickets automatically. A bounced Mail message gets classified by Agents and the suggested action shows up in the operations panel.

Sovereign deployment, by default

Every Amargi product is deployable as managed cloud, EU-isolated cloud, private cloud (your AWS / Azure / OpenStack), or fully air-gapped on-premise. Same codebase, same architecture, no second-class on-prem version that lags six versions behind. Regulated industries, banking, healthcare, government, shouldn't have to choose between modern tooling and data sovereignty.

What's shipping today

• Amargi Hub, the unified launcher and account surface (live).
• Amargi Agents, the AI control plane that powers every embedded agent (live).
• Amargi Reach, multi-tenant WhatsApp Business with direct Meta integration (license required).
• Amargi Meet, branded video conferencing, no per-minute fees (live).
• Amargi Mail, transactional email through your own MTA (in active build, Q3 2026).
• Amargi Escalate, operations ticketing wired into the suite (in design, late 2026).
• Amargi Remote Control, cross-platform desktop remote control (in design).

What's next

We're in early access. Founding customers get heavy discounts, direct access to the founding team, and outsized influence on the roadmap. If any of this sounds like the platform you wish you had, contact us.