Straight answers

An ed25519-signed license key by email, and — in the buyer portal — a signed download link for the complete source zip: backend, admin, rider app, driver app, docs, plus verify-license.mjs so you can check the key's authenticity offline.

Running your own ride-hailing business on one deployment (one brand): Regular. Hosting the platform for other paying businesses (SaaS / multi-tenant): Extended. Full text at /legal/license.

No. Source code can't be honestly DRM'd, so we don't pretend. The license key is a cryptographic proof of purchase — it protects you (support, updates, authenticity), it doesn't police you. Details: honest engineering.

The binding policy lives in the terms of sale (TODO(owner): finalize before launch). Our stance: try the live demo first — it is the product; a source product that has been delivered can't be "returned".

For the update window in your terms (6 months by default), fresh builds appear in the buyer portal under your same key as the changelog grows. After that your code keeps working forever — you simply stop receiving new zips.

Node 20, PostgreSQL with PostGIS, Redis — one VPS runs the whole stack via the included Docker Compose production setup; the mobile apps build with Expo (store CI config included). Walkthrough: installation and deployment docs.

Everything external is credential-gated and dormant by default: no payment keys → cash rail, no SMS keys → OTP in logs (dev), no e-invoicing credentials → deterministic local invoices, honestly labeled. You can run the entire platform end-to-end with zero third-party accounts, then light rails up one by one.

Yes — the 37 presets are curated starting points, not a boundary. A market is a config row (currency, timezone, rails, languages, tax). You'd add a locale file for an unshipped language and pick from the 9 built rails (or add a provider behind the same interface).

Five newer rails are built and unit-tested against recorded protocol behavior but haven't cleared a live transaction with provider keys. The admin shows this honestly. Practically: budget a sandbox test with your own keys before going live on those rails — exactly what the amber pill exists to tell your operators. Details.

Yes — branding (names, icons, splash, colors, gateways-per-market) is config/asset driven, documented in the branding guide; country/currency/timezone switching is DB-backed, no code edits to launch a market.

You mostly don't have to take our word: the live demo is the product; the test/market/language numbers are counted from the repo at build time ; the changelog keeps its bugs on the record.

The public surfaces are inspectable on the demo, and the docs portal mirrors the real in-repo documentation. Full source review pre-purchase isn't offered (the source is the product), but ask specific questions — sales@example.com answers with real file paths and honest limits.

Email sales@example.com. Pre-sales questions about license fit, market coverage or customization scope get straight answers, including "no" where the answer is no.