States are writing their own aggregator rules now — why that matters even if you're not Ola or Uber
For years, "aggregator regulation" in India mostly meant a handful of national rules that the big platforms dealt with and everyone else assumed didn't apply to them. That assumption is getting less safe. States have started writing their own aggregator rules, and they're doing it with real enforcement teeth — licensing fees, safety deposits, and penalties that apply to any platform operating app-based rides or deliveries, not just the household names.
If you run, or are building, a ride-hailing or delivery operation focused on a specific city or region, this is now a compliance question, not just a national-platform one.
What's actually changed
Maharashtra has introduced Motor Vehicle Aggregator Rules for 2026, with cab aggregators required to register by 1 September 2026. The structure includes licensing fees, tiered safety deposits based on fleet size, and a requirement that drivers receive at least 80 percent of the fare collected.
Haryana has gone further in some respects — a licensing regime that bans onboarding new petrol and diesel vehicles from January 2026, pushes fleets toward CNG and EV, caps platform commissions at 20 percent, and carries penalties up to ₹1 crore along with possible licence suspension.
Two states, two different specific approaches, but the same underlying shift: regulation is moving from a small number of national rules to a patchwork of state-level requirements, each with its own registration process, fee structure, and driver-payout rules.
Why this matters more for regional operators, not less
It's tempting to assume state-level rules are aimed at the big national platforms and a smaller, city-focused operator will be beneath notice. That's a risky assumption for two reasons.
First, licensing and registration requirements generally don't have a "you're too small to count" exemption written in — they apply to anyone operating an app-based aggregator model in that state, and the definitions are broad by design.
Second, and less obvious: a smaller, regional operator often has less slack to absorb a compliance misstep. A large platform can afford a temporary suspension in one state while it's a rounding error nationally. For an operator running in one city or one state, the same suspension is the whole business, stopped.
The part that's easy to get structurally wrong
The driver-payout rules are worth particular attention, because they're not just a policy statement — they're an operational requirement. If a state mandates that drivers receive a minimum share of the fare, that has to be true of how your payout system actually calculates and pays out, verifiably, not just true in your terms of service.
Retrofitting that into a payout system that wasn't built with an auditable percentage split from day one is a much bigger job than building it in from the start. The same goes for anything a regulator might reasonably ask to see — trip records, fare breakdowns, driver earnings — being reconstructable, not just theoretically calculable.
What this means practically
If you're operating, or planning to operate, an app-based ride-hailing or delivery service anywhere in India, it's worth treating "check the current state rules for every state you operate in" as an ongoing task, not a one-time check before launch. The trend is toward more states doing this, not fewer, and each one is free to set its own specifics.
Practically, that argues for building the underlying system — driver payouts, trip records, fare splits — in a way that can be adjusted per state without a rebuild, since the rules in the state you're in today may not be the rules you're operating under in eighteen months.
We built ZoRide for exactly this kind of regional, multi-vehicle-type operation — riders, drivers, and dispatch across autos, bikes, and cabs for an operator in Chhattisgarh — with payout and record-keeping structured to be auditable, not just plausible. It is also a concrete example of our custom software development work. If you're building or running something similar and want to talk through what the current rules mean for how your system needs to work, get in touch.
This is general information, not legal advice. Aggregator rules are being actively written and revised state by state — confirm the current requirements for your specific state before relying on any of it.