Software for people who work.
Two products. One for drivers on the road. One for the engineers building for them — because you cannot test an app made of many people while being one person.
Two products, one thesis.
The people who move the world's goods have no platform of their own. We build one — and the tool that proves it works before anyone has to depend on it.
Buzz
A platform for the 1.57 billion people working the gig economy. Earnings that follow the road, a live map of the drivers near you, group chat and a feed — built for a mid-range phone on a prepaid plan.
Populace
Brings a population of simulated people to life inside your app and drives it through your own API — signing up, moving, posting, messaging, joining groups. Published on npm and pointed at two unrelated backends.
Build it for the people who keep cities moving — then prove it works.
Who we build for
Riders, drivers and couriers, most of them working across several platforms at once on a mid-range phone and a prepaid data plan. That constraint shapes every decision: a 7 MB download, sixteen languages at full parity, and an app that keeps accepting work when the signal drops.
How we prove it
We built our own testing platform, because the bugs that matter in a multi-user product cannot be found by one person. It found six in our own finished app — the last of them on the run meant to sign the work off.
What we publish
The runs that found nothing and the runs that found something, together, with the limits of both written down. The test report names the claims we had to withdraw.
A driver in Delhi shouldn't get a worse app than a driver in London.
Buzz ships in sixteen languages — right-to-left included — and picks the currency from where you actually are.
Built for the connection people actually have
Buzz assumes patchy signal, prepaid data and a mid-range Android phone, because that is what the work runs on. A post or message written underground is queued on the device and sent when the connection returns.
Tested against the cities people actually work in
Populace models drivers moving through Manila, Mumbai, Delhi and Jakarta — real routes, real distances — rather than synthetic load pointed at an endpoint.
Three commitments, each with a mechanism behind it.
A promise nobody can check is marketing. Each of these is held up by something in the code that fails loudly if it stops being true.
Free for workers, permanently
Not a trial and not a freemium tier. Buzz costs a driver nothing and always will.
The mechanism: the business model does not route through them. Revenue comes from enterprise supply, fleet APIs and workforce analytics — the shape that funded LinkedIn and Waze — so there is never a quarter in which charging drivers becomes the obvious fix.
Privacy the database enforces
One driver cannot read another's data even if the app asks it to.
The mechanism: row-level security in Postgres, not a check in the client. An app bug cannot widen it, because the rule is enforced below the app.
We publish what failed
Every test run against both products is public, including the ones that found defects in our own finished work.
The mechanism: the report records withdrawn claims by name. A number we could not reproduce is marked as not measured rather than estimated.
A short history, because it is a short history.
Gigzen Private Limited incorporated in Bhubaneswar, Odisha, India. MCA-registered, two directors.
Populace separated into its own product. It began as a test harness inside Buzz; its engine was rewritten to hold no reference to any real app, which is what turned an internal script into something another company can pick up.
Buzz signed and on Google Play's internal track — sixteen languages, 27 currencies, offline writes, photos moved to object storage.
Populace ran against a live backend for the first time. Six simulated drivers found five bugs in Buzz in three and a half minutes.
Two hundred concurrent drivers across twenty cities: 932,455 API calls, thirteen methods, zero failures. A 300-driver run reached 1.4 million calls the same day.
Small, and deliberate about it.
Gigzen Private Limited is a software company in Bhubaneswar. We ship few things and try to get them genuinely right. We write our own tools, run our own infrastructure, and say plainly what our software does and does not do yet.
Owns the commercial side — partnerships, market strategy, and how our products reach the people who need them.
Owns the engineering — both products end to end, the infrastructure they run on, and the public record of what was tested.
Work with us.
Building something that needs testing at scale, or want early access to Populace? We would like to hear about it.