


Two platforms we designed and engineered end to end, shown the way they really run, and Cockpit, a workspace designed for clients to follow delivery. Try that one yourself.
Tornado and Bingo: real screens from the running apps · Cockpit: interactive demo with sample data
Every reel is a storefront.

Social commerce usually splits shoppers, creators and brands across disconnected tools. Inventory, commissions and content drift out of sync, and heavily filtered content erodes trust in what actually arrives.
One Flutter codebase powering three purpose-built apps that share a single live state. A product a brand edits, a creator pins mid-live and a shopper adds to cart is always the same product, in real time.
A complete, tested product across all three apps: shoppable video, live selling, memberships, affiliate sampling and analytics, in a dark frosted-glass design system.
Shots, posts and lives publish exactly as captured: no colour filters, beauty effects or AR. Creators confirm it before every publish, and shoppers see an “Unfiltered” badge, so products look the way they'll arrive.

Every payment is split by a dedicated engine on integer money, so it always balances. A ₹99 membership pays the creator ₹71.85.
| GST (inclusive) | 18% carved out |
| Payment gateway | 2% of the charge |
| Tornado, year 1 | 12% of post-GST |
| Tornado, after 12 months | 8%, rewarding retention |
| Creator | The rest, settled instantly |

Your ride, the moment you need it.

Launching a ride-hailing business from scratch means two apps, an operations dashboard and a server, each with its own edge cases, before the first rupee of revenue. Riders dislike price surprises and waiting in the dark. Captains lose too much of every fare to commission.
One Flutter and Dart codebase delivers a rider app, a captain app and a web operations console on a shared design system, backed by a single ride server that enforces every rule. Fixed fares, OTP-verified pickups and swipe-to-confirm controls remove the ambiguity from each step.
A complete, tested platform that launches under an operator's own name, colours and fares on iOS, Android and the web, backed by 21 automated API tests. The screens above are real captures from a live test ride between the apps.
Picks a drop, sees fixed fares for bike, auto and cab, and books. A ride OTP is created.
Rider appNearby captains of that vehicle type see the request with a 15-second ring. The first swipe wins.
Captain appThe rider watches the countdown and plate. The captain swipes “Arrived”.
Captain appThe rider reads out the code. The server checks it and never shows it to the captain.
Both appsPayment is settled by UPI, wallet or cash, then the rider rates and tips.
Both appsEverything an operator needs to decide: how the market is moving from commission to subscription, what riders, captains and operators each want, how HALO takes Bingo from signed proposal to first paid ride, and what the outside services cost to run.
Full visibility. Every single day.
Clients often have to wait for a status call to learn what shipped, what is next and what a project has spent. Decisions get buried in email threads, and problems surface late.
One workspace that shows sprint progress, the next live demo, open decisions, budget and files. Clients see the same view as the delivery team, and every decision is kept on record.
A single place to answer the questions a client asks most: where are we, what do you need from me, and are we on track? Try it below.
Sample data. Nothing you do here is saved, and it doesn't show a real client's project.