Self-host data export, sign-in policy everywhere, fairer billing, and taxi operations controls
Export your entire workspace for self-hosting in one guided flow, sign-in rules now enforced across every app with passkey support, plan changes with fair proration and a payment grace window, and runtime toggles for parcel, scheduled, and round-trip rides.
Your data is yours — self-host migration export
Businesses on the cloud plans can now take everything with them. A new
self-host export add-on (enabled on request) moves your full workspace —
drivers, vehicles, trips, shops, products, wallets, reviews, KYC,
uploads — out of the cloud and into your own infrastructure.
Two destinations. Download a complete archive via a secure,
expiring link, or stream directly into your own Postgres database —
including through an SSH bastion if your database isn't publicly
reachable.
Dry-run first. Before anything moves, the exporter walks every
table and shows a coverage projection — what will be exported and
roughly how large it is.
Safe by default. Direct database transfers refuse to run against
a non-empty target unless you explicitly opt in, so a re-run can
never silently collide with existing data.
Hands-off completion. Long exports run in the background and
email you when the archive is ready to download.
Sign-in, your rules — now enforced in every app
May's auth policy page decided what sign-in methods are allowed per
role and per app. This month, every app enforces it end to end.
Login screens follow your policy. The passenger, driver, shop,
parking, and admin console apps now show exactly the sign-in methods
your policy allows — nothing more.
Passkeys across the board. Passkey enrollment is now offered in
all six apps, and only appears for user groups whose policy permits
it. Require passkeys for admins while customers keep phone OTP, or
roll them out to everyone.
Fairer billing
Change plans from the dashboard. Upgrade or downgrade your cloud
plan directly from Dashboard → Billing — no more round-trip through
the payment portal. Downgrades warn you up front if the new plan
allows fewer operation cities.
Fair proration. Upgrades charge only the prorated difference
immediately; downgrades bank the unused balance as credit on your
next invoice; nothing is charged during a trial.
A real grace window. A failed payment no longer interrupts your
operation. You now get 7 days of full service to update your payment
method, and the failure email tells you exactly how long you have.
The moment payment succeeds, everything is restored automatically.
Taxi operations controls
A new Taxi operations section under dashboard settings lets you
shape what your taxi service offers — at runtime, no app update needed.
AI across the workspace, legacy data import, auth policy, and platform support tickets
AI is now wired into KYC, reviews, shop, support, analytics, and driver voice — alongside a self-serve importer for legacy systems, per-role auth policy controls, and a support channel inside the admin panel.
AI is now a first-class part of BetterSuite
The biggest shift in May. A new AI layer runs across the workspace,
configurable per business with its own provider keys, usage and spend
tracking, and per-feature toggles. What it powers today:
KYC document OCR. Reviewer opens an application and document
fields are already extracted from the upload — ready to accept or
edit.
Review moderation. Incoming reviews are scored for abuse and spam
before they hit the public feed, with the AI's reasoning shown in the
moderation queue.
Parcel delivery — turn the parcel option in the passenger app on
or off for your business.
Scheduled rides and round trips — enable or disable advance
booking and return-trip requests independently.
Instant effect. Apps read these flags when they start, so a
toggle flipped in the dashboard reaches your riders' phones without
waiting on a store release.
Review summaries. Each driver, merchant, or service provider gets
an at-a-glance summary of their reviews — strengths, complaints,
recurring themes.
Product suggestions for shop vendors. Adding or editing a product
proposes a title, description, and category from a short prompt or
photo.
Semantic shop search. Product embeddings power natural search and
related-product suggestions — "wireless headphones under £50"
returns what the shopper meant.
Support ticket triage. New tickets land with a suggested
category, priority, draft reply, and the closest matching past
ticket.
Service question templates. Setting up a new service type
generates the intake questions from a one-line description.
Natural-language analytics. Ask questions like "top-grossing
vehicle classes last week?" on the accounting dashboard — no SQL,
no custom report.
Voice for drivers. The driver app reads new order requests and
active-order updates aloud, so drivers don't have to look at the
screen mid-traffic.
A dedicated AI page in the admin panel handles provider keys, spending
caps, per-provider usage breakdowns, and lets you flip each feature on
or off independently.
Legacy data import — Ridy and BetterTaxi v1 in one self-serve flow
The admin panel now has a built-in importer for legacy systems.
Auto-connect. Drop in the source credentials and hit Test
connection. The importer reaches the legacy server, inspects the
schema, and confirms it's a shape it can read.
Automatic schema mapping. Drivers, vehicles, trips, regions,
services, KYC, reviews, support tickets, wallets, uploads — every
table is mapped into the new schema without glue code.
Live progress, cancel and retry. Each phase reports as it runs,
individual phases can be retried, and incremental syncs pick up from
the last watermark — so cutover can happen in stages rather than one
big bang.
Ridy and the legacy BetterTaxi backend are the first two connectors.
More slot in without rebuilding the pipeline.
Per-business auth policy
A new auth policy page in the admin panel decides what methods are
allowed, encouraged, or required — per role and per app.
Per-app. Require passkeys in the admin console while keeping
phone-OTP only in the passenger app.
Per-role. Owners and admins can be held to a stricter bar than
end customers.
Three states per factor. Password, email OTP, phone OTP, passkey,
social login — each can be off, optional, or required. Sensitive
admin actions can also require a fresh re-auth.
Platform support tickets in the admin panel
Submitting a support ticket no longer means email back-and-forth or a
separate portal.
File from the admin panel — pick a category, write the issue,
attach files.
Threaded replies between the business and the platform team in
one conversation.
Email and in-app notifications on every status change, so neither
side has to keep an inbox open.
Loading…
