Run your car-wash business on the software that runs ours.
Licence the ops dashboard, washer app, customer booking and cloud backend Sazup uses every day in Bangalore. Your brand, your data, your cloud project. No more running the business over WhatsApp.
Three products. One backend. Configured for you.
Run the whole operation
The web console your team runs bookings, washers and revenue from.
A job queue in their pocket
Android app for the partner on the ground — an internal APK, not on the Play Store.
Bookings, not WhatsApp threads
Web and app booking flow for your customers, on your own link.
- Data & logic: Firebase: Firestore + Cloud Functions (asia-south1), the same stack Sazup runs on
- Apps: FCM push · Razorpay · Resend email OTP
- Ops: hardened security rules · payment & OTP collections server-only · immutable activity trail · daily backup
- Runs on: a cloud project in your name; pay-as-you-go infra, typically well inside free-tier limits
- Data & logic: Firebase (Firestore + Cloud Functions) with scheduled jobs for cycles, renewals and reminders
- Apps: FCM push · Razorpay with webhook reconciliation · Resend transactional email
- Ops: everything in Starter + BigQuery export for reporting · uptime & error alerting · point-in-time recovery
- Runs on: your cloud project, Blaze plan; per-area configuration, one dashboard
- Data & logic: managed Postgres (Cloud SQL) behind a Node API, with Firestore kept for realtime job state and push
- Apps: FCM push · Razorpay + settlement reports · Resend · queue-backed jobs for assignment and billing runs
- Ops: everything in Growth + BigQuery warehouse · role-scoped multi-branch dashboard · audit exports · agreed uptime target
- Runs on: your cloud project, dedicated region; sized after a volume review with you
Confirm first, staff second.
A holding state between confirm and assign means the customer never waits on staffing. It is the same pattern ride-hailing uses.
You licence the platform. You keep everything it produces.
Your brand, your cloud project
Deployed under your name into a cloud project you own; customers, bookings and revenue data are yours.
We set it up
Services, vehicle tiers, prices, service areas, team logins, payment gateway.
Your team onboarded
Ops on the dashboard, washers on the app, customers on your booking link.
Updates and support
Improvements we ship to Sazup ship to you for the licence term.
Operators who’ve outgrown the group chat.
Doorstep wash operators with 3+ washers
Assignment, timing and payouts outgrow a group chat fast. A queue and a roster keep the day organised.
Detailing studios adding home service
Bring the studio’s services and prices to the customer’s doorstep without building booking software first.
Apartment-subscription and franchise operators
Cycles, credits and multiple service areas need real configuration, not another spreadsheet.
Common questions
Do we own our data?
Yes. It lives in a cloud project you own, and you can export it any time.
Is it our brand or Sazup’s?
Yours: name, logo and booking link.
Can we change services and prices ourselves?
Yes, live from the dashboard; 6 vehicle tiers.
Do we get the source code?
No. You get a licence to run it, with updates included.
Can we run more than one city?
Yes. Service areas are configuration, not code.
How do customers pay?
Through Razorpay: UPI, cards and wallets, as a deposit or in full.
What does it cost?
Talk to us. It depends on fleet size and cities.