Rekhu Assistant 0.13 for multi-tenant apps and white-label resellers
Rekhu Assistant 0.13 keeps tenants with their own users tables strictly apart, puts later work back in the right tenant, lets tools run several steps with progress and usage of their own, switches the chat on per tenant, and lets your customers resell it under their own brand.
Many apps host many customers on one server, each with their own users. Some of those customers resell the app under their own name. Rekhu Assistant 0.13 is built for both.
Tenants strictly apart
When your app names a tenant per user, a conversation belongs to the tenant and the user together. User 3 of one print shop and user 3 of another are two different people. Neither ever sees, lists or continues the other's conversations, and each has their own limits. Work that runs later, such as a report sent again from the queue, first puts your app back in the right tenant, so a database per tenant is switched before anything happens.
Tools that do real work
A tool can now do what a person in your app does, step by step:
- price a product;
- choose the delivery;
- add it to the cart.
Each step goes through your own routes, as the signed-in user, with their permissions. While it works the user sees progress ("Comparing 120 offers…") and the first results early. What a tool uses of its own, such as a preflight check or an image improved, is reported with the answer, so you bill it together with the tokens.
Roll it out tenant by tenant
Switch the chat on per tenant, user or chat. Where it's off, the widget simply isn't there. That lets you run the new chat next to an old one and move customers over one by one.
Your customers' brand
Turn off the Rekhu name, and nothing in the chat mentions Rekhu or its knowers. Each tenant gets its own name, logo and colours in the widget.