How the products work together

Vabu OS is one platform, not nine separate tools. Every product sits on top of services that Vabu runs or rents, such as payment collection, message channels and video delivery. On top of those, each product adds the parts a live business needs: orders, tickets, points, access rules. And every product speaks the same platform language: the same keys, the same events and webhooks, the same customer.

Because every interaction becomes an event, it can feed the three products that learn from the rest: loyalty (points for showing up and spending), insights (numbers across everything) and messaging (a reason to write to someone at the right time). That loop is the point of using the products together.

Product	Sits on	Adds for you
Payments	M-Pesa and card collection through Payd	Checkout, settlement to organizers, refunds, payout requests
Messaging	WhatsApp, SMS and email channels	Blasts to attendees and fans, scheduling, message credits
Identity	Vabu ID and Payd ID	Sign-in, customers, sessions, one customer record per tenant
Streams	Video delivery networks	Ingest, protected playback, access rules, viewer sessions
Events	Payments, Messaging, Streams	Events, ticket types, orders, check-in
Commerce	Payments	Storefronts, products, orders
Fanbases	Events from every product	Members, points, tiers
Insights	Events from every product	Revenue, audience and conversion numbers

A hybrid event, from first ticket to replay

Take a Friday night show with a crowd at the venue and a paid stream for everyone else. Here is how the products carry it, and which parts happen by themselves.

1. Create the event and its tickets. In Events, create the event, add ticket types (General, VIP and a Stream pass) and publish it.
2. A fan buys a ticket. The order starts a checkout. The fan pays with M-Pesa. Payments confirms the money and the order moves to paid. Vabu sends an events.order.paid event to your webhook endpoint.
3. Points arrive by themselves. The purchase earns points in the organizer's fanbase, at 1 point for each KES 10 spent. If the fanbase has auto-enroll on, which is the default, the fan joins it too.
4. You grant the stream. Your handler for events.order.paid makes one call, POST /v1/access/entitlements, with source: "ticket", the order code as the source_ref and your own id for the buyer as customer. That gives the ticket holder the stream. See paid access.
5. A reminder goes out. Schedule a WhatsApp reminder to ticket holders with POST /v1/organizer/events/{event}/communications/whatsapp and a schedule_at the evening before. See Messaging.
6. The night. The venue's encoder sends to the live stream. People at the door are checked in, and each check-in earns attendance points. Viewers at home open your page, your server signs a customer token, and Vabu opens a session and checks the device limit. See Streams.
7. Afterwards. Add the recording as an asset, grant it to ticket holders as a replay, and read the night's sales and audience numbers in Insights.

What runs by itself and what you wire

Step 3 and the attendance points at the door need no work from you. Steps 4, 5 and 7 are one call each, from your own server or your organizer tools.

Some of this will become automatic. Tickets that grant the stream and the replay without your handler, reminders that send themselves, and points for watch time are on What's coming.

Use one, or all

Nothing here forces you to use more than one product. A church can use only Streams and keep its own login and payments. A club can use only Events. When you add a second product, the events and the customer record connect them for you.

Read ways to use Vabu OS for the choices about login and payments.