City configuration
Define operator identity, service categories, geography, currency and time zone for each city deployment.
PLATFORM ARCHITECTURE
Shared core.
Local configuration.
Controlled releases.
The engineering model behind Black Fleet: operational logic, dedicated applications, payment integrations and connections to the services a transport operation relies on.
01 DEPLOYMENT ARCHITECTURE
Common logic.
Dedicated deployments.
The system design for a city implementation combines shared operational logic with dedicated applications and local configuration. Your proposal defines the deliverables, integrations and delivery milestones.
BLACK FLEET DEV
Shared operational core
Booking logic · application workflows · standard releases
OPERATING REFERENCELondon
London
- City-branded client app · iOS and Android
- City-branded chauffeur app · iOS and Android
- Operator workspace · Mac and Windows computers
- City website
- Local configuration and data boundaries
CITY DEPLOYMENT MODEL
Partner city
- City-branded client app · iOS and Android
- City-branded chauffeur app · iOS and Android
- Operator workspace · Mac and Windows computers
- City website
- Local configuration and data boundaries
System design for city deployments. London provides the operating reference; applications, functionality and release dates are agreed for each implementation.
02 ENGINEERING PRINCIPLES
Configuration.
Permissions. Integration.
Workflow design
Map the handoffs between booking, allocation and journey updates to the information and actions each role needs.
Access boundaries
Operator data separation, role-based permissions and specifically authorised support access are requirements of the city deployment model.
Integration boundaries
Define how provider events relate to bookings, payment records and journey updates, with access appropriate to each workflow.
Release discipline
Maintain common capabilities in the shared core, with configuration and release readiness checked for each operator deployment.
03 PAYMENT & SYSTEM INTEGRATIONS
Connected payments.
Connected operations.
We develop the integrations that link customer checkout, operational records and external services. Each connection is designed around a transport workflow.
Payments & checkout
The London platform includes Stripe integration for customer payments, connecting checkout and payment-status events with booking records.
Maps & routing
Address lookup, location data and route information to support booking and journey planning within the configured deployment.
Flight data
Flight lookup and schedule information for airport-related bookings and pickup workflows.
Messaging & notifications
Email, SMS and push notification integrations configured around agreed booking events, journey updates and user roles.
Provider selection, enabled workflows, account requirements and third-party usage costs are confirmed for each deployment.
Discuss your integration requirements04 CHAUFFEUR SETTLEMENT
Journey earnings.
Approval. Payout.
A settlement workflow connecting chauffeur earnings, finance approval and payment scheduling.
The settlement design links completed journeys and approved chauffeur payables with scheduled bank payouts, provider confirmation and consolidated self-billing. The implementation plan defines how those stages connect for your operation.
Automated payout integration, approval roles, payment cycles and self-billing requirements are specified in the agreed delivery scope, with acceptance checks before activation.
Discuss chauffeur settlement workflows05 SECURITY & QUALITY
Permissions.
Verification. Accountability.
Our engineering approach considers the people using the platform, the actions they can take and the checks around a change.
Access boundaries
Client, chauffeur and operator workflows have distinct access requirements. Role and ownership checks at the service layer support those boundaries, alongside the permissions presented in each application.
Workflow verification
Automated checks support development of booking, assignment and payment workflows. Deployment-specific acceptance criteria define the scenarios to verify before activation.
Controlled delivery
Development, staging and live environments serve different purposes. Version control and targeted checks support the assessment of changes before release.
Operational feedback
Maintenance connects software development with day-to-day use. Reported issues and operator feedback help prioritise corrections and standard platform improvements.
CONTINUOUS DEVELOPMENT
Maintain the core.
Scope the extensions.
Ongoing software maintenance and standard platform updates are included in the monthly subscription.
Operator-specific workflows, bespoke reporting, custom integrations and other work outside the normal roadmap may be scoped and quoted separately.
Dedicated city apps are included in City Launch setup, with release and distribution agreed for each deployment.
THE NEXT STEP
Start with your system requirements.
Bring your booking process, integration needs and operational constraints to a platform walkthrough.
Plan your deployment