Five apps to answer a client. One inbox instead.
Morax Chat brings WhatsApp, Instagram, Messenger and email into a single mobile inbox, ties every account a client uses back to one record, and refuses to send until you approve. The inbox, the database and the connectors that exist live in their own repository; this hub does not run them.
Open the inbox — indisponible. The inbox runs from the Morax-Chat repository on the Morax NAS, reachable only over its private network. No public URL is wired to this hub, so there is nothing to open from here.
Built in Morax-Chat, running on the Morax NAS, private network only. WhatsApp (Evolution), IMAP and Chatwoot are implemented. Instagram and Messenger wait on Meta App Review.
What this product does
One inbox, every channel
Each channel is converted to a single message model on the way in, so answering a WhatsApp message and answering an email are the same gesture. The app never speaks a provider’s dialect directly.
One client, every identity
The same person writes from an Instagram handle, a phone number and a work address. Those are three identities attached to one contact, not three strangers — and nothing gets merged automatically just because two names look alike.
Drafts you approve
A message only leaves after you press send, by design and by database constraint. Suggested drafts from a model are designed; they are not built yet, and nothing is sent on anyone's behalf in the meantime.
In detail
Search that answers a question
Keyword search and structured filters over the same history, so a postcode or a price comes back as a hit rather than a scroll. Semantic search with citations is designed; it is not what runs today.
Multi-tenant from the first migration
A tenant column on every functional record and PostgreSQL row-level security from day one — not bolted onto a live database later, which is the canonical route to a cross-tenant leak.
A phone-first inbox
An installable web app first: read, assign, note and approve from a phone. Native devices pair with the inbox through a revocable token.
A NAS first, a cloud later
It runs on the Morax NAS under Docker, behind the private network. Moving to managed Postgres, Redis and object storage changes environment variables, not the codebase.
Connectors stay replaceable
Personal WhatsApp runs through an unofficial library, which can be restricted or disconnected at any time. It sits behind an adapter for exactly that reason: swapping it for the official API changes one module.
Who it is for
- A shooting day
- The messages that arrive while you are working land in one queue with a draft answer waiting, instead of four apps left unread until the evening.
- An inbox that overflowed
- What still needs confirming for tomorrow comes back as an answer with its sources, rather than a scroll through three months of threads.
- A client on three platforms
- The Instagram DM, the phone number and the work address are one record, so the history follows the person and not the app they happened to use.
- A quote from last year
- The price, the date and the place are extracted from the conversation when it arrives, so finding them again is a search and not an excavation.
The inbox exists. Not here
The button appears on this page when there is a public URL to point it at. Until then the product runs in its own repository, and this page tells you that rather than pretending otherwise.
Open the inbox — indisponible. The inbox runs from the Morax-Chat repository on the Morax NAS, reachable only over its private network. No public URL is wired to this hub, so there is nothing to open from here.