Baobab Live
Live events, controlled access, audience conversations, and replay.
Made for event organisers and audiences.
Overview
This platform family is under active development. The scope below describes its intended design; deployment readiness and supported capabilities must be confirmed for each engagement.
Live-event software needs to serve two very different moments: the organiser preparing a broadcast and the viewer trying to join it. Complex registration, unclear payment status, or excessive data demands can interrupt that connection.
Baobab built a product around a direct event journey. Organisers create an event, configure access, prepare the broadcast, and distribute the event link. Viewers arrive at a public lobby that explains what is happening and how to enter. Free access stays immediate, while paid access connects phone verification and payment to the same event.
What is included
Organiser workspace
Prepare and run the event
Organisers manage event details, scheduling, pricing, recording preferences, and shareable QR assets. OBS provides the broadcasting path, while stream-health information helps the host understand whether the incoming feed is ready.
The event lifecycle separates a scheduled event, a connected broadcast, a host's decision to go live, and the end of the event. This keeps technical ingest activity from silently changing what viewers are told. Event and revenue reports give organisers a view of the commercial and operational activity around their broadcast.
Viewer experience
Reach the stream
Free events support guest entry without phone verification. For ticketed events, viewers verify their Ghanaian phone number, pay in cedis through Paystack, and return to the event they selected. The public link and QR code help audiences arrive from messaging apps, posters, and physical venues.
Data-conscious playback controls support mobile audiences. The interface communicates scheduled, live, reconnecting, and replay-related states so viewers can understand whether they should wait, resume, or return later. The product is accessible through the web without requiring a native app installation.
Commerce and playback
Connect payment to access
The commerce workflow records orders and establishes an entitlement after verified payment processing. Playback authorisation uses that internal entitlement to issue bounded access. A checkout return alone does not mark an order paid, and a shared event URL does not carry a paid viewer's access rights.
This separation matters when payment notifications arrive late or are retried. The viewer's purchase is a durable business record, while the credentials used to play media have a shorter lifetime. The platform can recover access from its own state rather than repeating a purchase or trusting an unverified browser redirect.
Engagement and replay
Live chat, presence, and moderation support the social part of the event. Hosts and moderators can manage disruptive participation while keeping the broadcast experience focused.
Recording is an organiser choice. When a recording is processed and replay is enabled, replay access follows the product's entitlement rules. Live viewing and replay are connected experiences, with explicit processing and availability states between them.
Built with
Baobab separated the event platform's control plane from the media-delivery provider. The application owns identity, events, payments, entitlements, chat, and authorisation; Cloudflare Stream supplies managed media infrastructure for the launch product.
The control plane uses Hono on Cloudflare Workers with a D1 transactional database, R2 storage, Queues, and Durable Objects. Product-owned packages define authentication, commerce, playback, broadcasts, recordings, and reporting. Validated contracts, conditional transitions, and retryable follow-up connect those domains without letting provider callbacks become the sole source of business truth.
Questions
Is this available for deployment?
Deployment readiness has not yet been verified for this catalogue entry. Contact us to discuss current scope, release gates, and your requirements.
Who owns this software?
This is owned engineering work from The Baobab, a brand of Fortezza Nuova Enterprise. Deployment and licensing terms are agreed for the relevant product.
Run Baobab Live in your organisation
Discuss the capabilities you need, deployment environment, and integration responsibilities. We will confirm current readiness and agree a scope before committing to a release.