Short answer: KiloDrive's architecture currently recognizes seven provisioned country workspaces: Jamaica, Cayman Islands, Barbados, Trinidad and Tobago, Bermuda, United States and Canada. That means the platform can keep country data and rules separate. It does not mean every ride, rental, parcel, wallet or provider feature is launched, approved or certified in all seven places.
A country selector can look simple, but location affects much more than the flag at the top of a screen. It can change currency, time zone, driver-licence and plate validation, fare configuration, safety requirements, legal documents, payments, emergency contacts, banks, insurance references and whether a feature is available at all.
What this means Choose the country where the service will actually be used, then trust the current in-app capability label. Do not use another workspace to bypass a local restriction or assume a feature exists because its screen or database table exists.
The seven provisioned workspaces
| Workspace | ISO currency | Configured time-zone context | Product-readiness note |
|---|---|---|---|
| Jamaica | JMD | America/Jamaica | Check the live Jamaica capability policy for each product. |
| Cayman Islands | KYD | America/Cayman | Country schema and signup configuration do not certify providers or local operations. |
| Barbados | BBD | America/Barbados | Feature availability can differ from Jamaica even when the schema matches. |
| Trinidad and Tobago | TTD | America/Port_of_Spain | Payments, legal rules and reference data require their own review. |
| Bermuda | BMD | Atlantic/Bermuda | Check current local policy, provider support and rollout state. |
| United States | USD | America/New_York baseline | State and local requirements can vary; one baseline cannot settle every jurisdiction. |
| Canada | CAD | America/Toronto baseline | Provincial responsibilities and time zones vary; confirm the actual operating location. |
KiloDrive uses ISO 4217 currency codes rather than a bare dollar sign. JMD is not interchangeable with USD, CAD, KYD, BBD, TTD or BMD.
KiloDrive stores server events in UTC and uses an IANA country or user time-zone context for display. The listed US and Canadian zones are baselines, not claims that either country has only one time zone.
What can change from country to country
Identity and vehicle rules. Licence length and pattern, plate format, required evidence, document expiry and vehicle checks can be country-driven. In Jamaica, for example, KiloDrive's current validation configuration expects a nine-digit driver's-licence value. Official requirements still come from the relevant authority; KiloDrive validation does not replace Jamaica Transport Authority licensing.
Currency and fare rules. Fare bands, minimums, time and distance components, toll references and hourly settings belong to the active tenant and country. The app formats each row in its ISO currency and displays the supported distance preference. This guide publishes no prices because values can change.
Safety policy. Pickup confirmation may be optional, required by country policy or unavailable. Emergency numbers must resolve from an authorized country context. Assisted-rider and supervised-dependent products require separate legal and lifecycle approval. Recording and behavioral insights must not be inferred from the existence of safety code.
Payments and membership. Payment providers, cashout, store products, base plans, offers and localized store prices require exact active mappings. A Free plan can be visible where permitted while a paid action remains unavailable. Physical rides, deliveries, rentals and wallet funding are not mobile-store digital purchases.
Rentals and parcels. Both have substantial implemented workflows, but their feature policies can fail closed. A country needs legal, provider and end-to-end lifecycle evidence before these products should be marketed as available.
Schema-ready is not country-ready
KiloDrive uses a control database for global identity and security plus separate country cells for operational records. Matching cell schemas reduces drift, but it is only one launch check.
A responsible launch also needs owned evidence for fares, tax, licence and plate formats, local references, KYC/AML, emergency and privacy rules, providers, reconciliation and operational support. Canada illustrates why this matters: Transport Canada explains that road-transport responsibilities are shared across federal and provincial governments. The United States likewise has federal vehicle-safety resources while licensing and ride-service rules can involve state and local authorities.
The public Legal centre, Safety page, Privacy policy and relevant product page should agree with the same capability policy. If they do not, the safe interpretation is unavailable until corrected.
How to check before you rely on a feature
- Select the correct country during signup or an authorized workspace switch.
- Confirm the ISO currency and local time shown before accepting a price or schedule.
- Read the feature's availability label, maintenance notice and country-specific terms.
- Verify required driver, vehicle, payment or identity steps in that workspace.
- If a destructive action is unavailable, do not try to bypass the gate from another country.
- Ask KiloDrive support for a country-specific answer when the status is unclear.
What is still uncertain
This article confirms the repository's provisioned country catalogue, not live commercial coverage. Rollout percentage, providers, reference-data completeness, emergency configuration, payments and legal approvals can change independently. A human reviewer must verify the public capability endpoint and each country's launch checklist immediately before publication. Readers should also consult local authorities; this guide is product information, not legal advice.
Frequently asked questions
Does a country in the signup list mean every KiloDrive feature is available there?
No. A provisioned country can support identity and data routing while individual products remain disabled, in maintenance or awaiting certification.
Why does KiloDrive show ISO currency codes?
ISO codes distinguish currencies that may share a name or symbol and help the app apply the correct minor-unit and formatting rules.
Can I select another country to access a blocked feature?
No. The workspace must match the real authorized operating context; using another country would apply the wrong rules and may be rejected.
Are the United States and Canada represented by one local time zone?
No. The configured entries are baseline workspace zones; actual display and operations must resolve the relevant user or administrative time-zone context.
How do I know whether rentals or parcels are currently active?
Check the current in-app or public capability label for the selected country; code and schema presence alone are not proof of availability.
Sources
- ISO 4217 — Currency codes — International Organization for Standardization.
- Time Zones — Internet Assigned Numbers Authority.
- Licensing Requirements — Transport Authority of Jamaica.
- Road Transportation — Transport Canada.
- Vehicle Safety Resources — US National Highway Traffic Safety Administration.