WakaGood is a complete negotiated ride marketplace.

What WakaGood stands for

WakaGood is designed for people who want choice without confusion. The platform focuses on upfront agreement, mobile-friendly screens, live ride context, staged privacy, support, and operational accountability.

• Passenger control: passengers can compare proposals and accept the rider that makes sense.
• Rider choice: riders activate only when they want to work and negotiate before committing.
• Staged privacy: trip details should be shared according to what each stage of the ride requires.
• Service accountability: WakaGood keeps ride state, notices, support, ratings, and completion context connected.

Platform coverage

The project is organized around three workspaces and a secure backend.

• Passenger: ride request, trips, payment, rewards, profile, notices, support, live approach, route changes, ratings, and safety reports.
• Rider: onboarding, eligibility, availability, live GPS, ride requests, destination preference, earnings, payout, ratings, notices, support, and profile.
• Operations console: production readiness, rider approvals, support inbox, safety review, account control, payments, messages, broadcasts, audit, diagnostics, and operational switches.
• Backend: Supabase Auth, Postgres, RLS, PostGIS, Realtime, private Storage, RPCs, Edge Functions, provider webhooks, scheduled jobs, and Cloudflare hosting.

The ride model

WakaGood separates a trip into clear stages: request, route estimate, negotiation, acceptance, live approach, pickup, in-progress ride, completion, settlement, rating, and support. That structure reduces confusion when pricing, status, payment, safety, and communication would otherwise be separate problems.

• Before match: riders can evaluate requests without seeing more passenger detail than needed.
• At match: accepting a fare closes negotiation and removes the request from the open marketplace.
• Before pickup: passengers can watch rider approach when live GPS is available.
• After completion: settlement records, ratings, support, and safety records stay tied to the authoritative ride.

Operating principles

• Fare must be recalculated when route-affecting details change.
• No-negotiation fare means a firm passenger offer; passengers who do not accept that fare should choose Negotiate before publishing.
• Negotiation is capped so neither side can keep pushing offers endlessly.
• Accepted fares should be shown before confirmation.
• Map and route usage should be helpful without creating uncontrolled provider cost.
• Payments, rider access, documents, tax, notifications, and platform controls should be verified server-side.
• Waka-controlled popups and notifications should appear under the WakaGood name.

The promise

WakaGood is building a ride culture where agreement is visible, choice is respected, and the trip feels organized from request to completion. That is the standard: practical for riders, clear for passengers, and strong enough for operations teams to run responsibly.