Product FAQ

Clear answers before you plan a Ridy deployment.

These answers are based on the product information currently listed for Ridy. Before purchasing or deploying, always verify current version, integrations and licensing with the official product source.

What this covers

Built for the moments that make a ride-hailing operation work.

✓Rider and driver Flutter projects
✓Backend and web admin panel source code
✓Linux VPS and Google Maps account requirements
✓Standard support and licensing notes
✓Known feature boundaries made explicit

How it fits together

A practical workflow, not a disconnected feature list.

01

Review the package

Confirm that the mobile apps, server and web admin panel match the operation you want to create.

02

Validate requirements

Prepare the Linux VPS, map-provider account and the technical resources required for your launch.

03

Confirm the commercial fit

Check current licensing, support scope, optional add-ons and local payment-provider availability.

Product FAQ

Questions worth answering before you build.

This site only describes capabilities stated on the Ridy product page. Confirm current release details, licensing and provider availability before deployment.

What does the Ridy package contain?

The package lists documentation, a Flutter driver app, a Flutter rider app, backend source code and a web admin panel.

What server is required?

The requirements list a Linux VPS, with Ubuntu 18.04 or 20.04 recommended on the product page.

Is parcel delivery supported?

The product page uses delivery as an example in one feature description, but its comparison table says parcel delivery is not supported in Ridy. Confirm this point through RidyTaxiApplication.com before relying on it.

Is dark mode listed for Ridy?

The product comparison says dark mode is not available for Ridy.

Keep exploring

See the connected parts of the platform.