Share a commute in Dhaka without handing a stranger your address
Sohojatri matches riders and drivers on the corridor they already travel and the time they travel it, between people who verified themselves first. It works from routes, never from a pin on your house. In build.
In build — tell us what you need and we will say honestly how close it is.
- Verify identity
- Describe the corridor
- Matched on route + time
- Recurring commute
Why this exists
Commuter ride-sharing in Dhaka runs on group chats and trust. There is no verification, no record, and no way to share a route without handing a stranger your home address.
Riders and drivers travelling the same route at the same time are matched into a recurring commute, with verification and location privacy treated as the product rather than as settings nobody opens.
What it does
Everything Sohojatri handles for you.
Route and time matching
PostGIS-backed matching on the actual commute corridor, not a straight-line radius that ignores how the city is laid out.
Verified identity
Email and phone verification gates participation, so a match is with an accountable person.
Privacy by construction
Precise location is never the default shared object; the system works from corridors rather than pins.
Admin oversight
A full administration surface for reports, verification review and route data.
What you get
Concretely, what lands.
Not adjectives — the things that exist afterwards that did not exist before.
- Matching on the actual commute corridor using PostGIS, not a straight-line radius that ignores how the city is laid out.
- Email and phone verification before anyone can participate, so a match is with an accountable person.
- An administration surface for reports, verification review and route data — oversight as a built part, not a spreadsheet.
How it works
From nothing to working.
Verify first
Email and phone verification gates participation. It is a low bar deliberately — high enough to make an account cost something, low enough that a commuter will actually clear it.
Describe the route, not the address
The system works from corridors rather than pins. Precise location is never the default shared object, which is a construction decision rather than a privacy setting somebody has to find.
Get matched on route and time
PostGIS matches riders and drivers travelling the same corridor at the same time, which is a different question from who is nearby right now.
Make it recurring
A commute is the same trip most days. The match is built to persist rather than to be re-negotiated every morning.
Who it's for
Built for these people.
If you are not one of them, we will say so rather than sell you a seat.
- Daily commuters in Dhaka splitting cost on a route they already travel
- Employers running staff transport they would rather not operate themselves
Before you ask
The questions that come up.
No — Sohojatri is in build. There is no waiting list theatre here: tell us you want it and we will tell you when there is something to use.
Ride-hailing matches a one-off trip between strangers and optimises for growth. This matches a recurring commute between verified people and optimises for whether you would get in the car twice.
The design is corridor-based rather than pin-based, so precise location is not the object being shared by default. That is the whole point of the product and we would rather lose a feature than break it.
Verification before participation, and an admin surface for reports and verification review. Neither is a guarantee, and we will not claim it is.
Be first on Sohojatri.
A few lines is enough. A senior engineer reads it and replies within one business day — and says straight away if it isn't a fit.
Or email contact@caffinix.com. We sign a mutual NDA before scoping if you need one.
Built on·Go · PostgreSQL 17 + PostGIS · React Native (Expo) · Angular 22 admin
← All products