Ventures

The pipeline, with nothing airbrushed.

Every Rivora venture carries a visible status. Live means people are using it. Prototype means you could tap it tomorrow. Exploration means we are still earning conviction. That honesty is the point.

Live Building Prototype Internal R&D Exploration

Flagship · Consumer marketplace

Live · Dubai

Snook A Look

The problem: cue-sports players in Dubai drive to clubs hoping a table is free, wait with no visibility, and play the same people every week. Clubs, meanwhile, run prime tables empty on quiet nights.

The thesis: make tables and opponents visible in real time, let players book in 30-minute slots, and give clubs a demand system instead of a phone that may or may not be answered.

Live on iOS and Android, with a club-operator platform behind it.

Snook A Look club page for Pot Black Billiards and Snooker: table list with per-hour prices and a book-table button
Snook A Look home screen: map of Dubai with nearby clubs and open table counts

In the engine

Currently building, prototyping, exploring.

Live sports engagementPrototype

Playdaq

The problem: watching live sport on a second screen is passive. The momentum everyone feels in a match has no visual, interactive form.

The thesis: render match momentum as a living probability curve, with a locked design foundation that keeps the product's identity stable no matter which teams play. Interface prototypes and the full design system exist; the engine decides next whether it graduates to build.

Engineering infrastructureInternal R&D

Rivora Fleet

The problem: a small team cannot ship venture-grade software on multiple fronts with conventional processes. Speed usually costs discipline.

The thesis: coordinate specialised AI engineering agents, each with a role, a doctrine of hard-won engineering lessons, and non-negotiable review gates, under a human founder's final pen. The Fleet built and maintains Snook A Look in production and is now building Flash Bikes. It is infrastructure, not a product for sale, and it is the engine's biggest unfair advantage.

Developer toolingExploration

Graphify

The problem: understanding a large unfamiliar codebase or document set is slow, and the map you build in your head disappears when you close the editor.

The thesis: generate a navigable knowledge graph from any input: code, docs, papers. Communities, hub nodes, and an explorable wiki instead of a folder tree. It already runs inside our own projects; whether it becomes a public tool is an open question the lab is testing.

Concepts stay in the lab until they earn a status. When a venture is archived, it will say so here. What you see is the honest state of the engine.

Partner with the engine

Your product could run on these rails.

The same pipeline that carries our ventures carries a small number of partner products each year.