Company
Employee identity, private routes, allowances, documents and an auditable ride ledger.
All Omnit modules
CARPOOLING · CUSTOMER INSTANCE
Omnit Ride
Launch a controlled ride-sharing network for employees, members or a city community, with your identity rules, visibility policy and data perimeter.
Company, community or city mode
Search, booking, chat and ratings
Self-hosted Docker delivery
One platform, three operating models.
The operator defines who can join, which rides are visible and how costs are settled.
Community
Invite-only access for campuses, residential areas, events and membership organizations.
City
Public discovery by region with moderation, local policy and configurable settlement.
The complete ride loop
The Telegram bot is the fast entry point; the customer instance remains the source of truth for identity, rides and payments.
01
Find or publish
02
Match route and time
03
Book a seat
04
Coordinate in chat
05
Complete and rate
REAL REPOSITORY BASELINE
Not a mockup. A working corporate carpooling foundation.
The canonical Omnit repository already has authentication, vehicles, ride search, bookings, chat, payments, documents, notifications and administration. The screenshot shows the live Omnit Ride entry used by the presentation environment.
Already implemented in the service
ride publishing and geo search
seat booking and cancellation
ride and direct-message chats
vehicles and driver documents
ratings and notification preferences
payments, refunds and admin audit
Operator-owned infrastructure
Each deployment can run in the customer perimeter. Omnit connects the module to Telegram without copying user passwords or ride records into the bot.
ASP.NET Core 8
PostgreSQL + PostGIS
Redis
Docker
health and readiness probes
offline license support
Working foundation, honest delivery status.
The ride lifecycle exists today. The universal product phase removes remaining single-employer assumptions and packages repeatable country and operator configuration.
Available foundation
modular backend and database
web workflows and administration
configurable visibility and payment modes
Telegram deep links and instance status
Universal rollout layer
neutral identity instead of employee-only IDs
pluggable maps and regional providers
country policy and localization packs
repeatable tenant deployment and Lava plans
Prepare the first Omnit Ride instance.
A pilot starts with the operator, region, identity policy and preferred settlement model. No public price is invented before the delivery package is fixed.