Skip to content
Go

Browse by product

Everything Go does for taxi and private-hire operations, grouped by domain. Click a feature to open its documentation.

Domain

Pricing

Tariffs, quotes, and fare rules.

When a ClientCapability has `priceCents` set, every trip segment that requests that capability gets a CAPABILITY_FEE lin
GPS Meter Pricing coming soon
A planned pricing mode that meters the fare from the driver's actual GPS trail during the trip, rather than from the rou
Conditional adjustments applied on top of the base tariff — surcharges, premiums, or rebates triggered by an arbitrary d
Architectural overview of the pricing pipeline: how tariffs are selected (decision tree), how tariff bands enforce stepp
Multi-load trips charge each passenger individually for their own segment; a Ride-Share Discount reduces each passenger'
For trips priced as a single total (not per-segment) — a Single-Priced Discount controls how the trip total is shared ba
Stepped pricing rates on top of a Tariff
A tariff defines how a trip is priced — its base fare components for distance, time and fixed charges, the vehicle types
Operator-defined tax classifications (standard, reduced, zero, exempt, and so on) that tag chargeable price elements
The API for pricing operations on an existing trip: reprice it after its inputs change, view the fixed-versus-metered fa
A quote is a priced snapshot of a trip segment — either a pre-booking estimate the operator or customer sees before conf

Domain

Trip

Bookings, lifecycle, scheduling, and trip health.

Pre-flight checks that block a driver from marking a stop as arrived / finished when real-world conditions are not met —
Models the cargo itself — a Package with weight/volume/dimensions, tracking codes, plain recipient contact fields (no Cu
Batch-plans the day's pending PACKAGE segments into sequenced van-day routes respecting time windows and weight/volume/d
Delivery Mode coming soon
A logistics/delivery operating mode alongside taxi/people-movement, built by extending the existing Trip spine rather th
Baseline-driven health resolution engine (ported from the decommissioned go-agent)
Customer-fault miles penalty when a customer cancels late: a no-show penalty if the driver had already arrived, otherwis
A single Trip can carry multiple chained segments (multi-load), enabling shared-ride, ride-pool, and school-run patterns
Compliance chain a driver must satisfy before a stop can be marked no-show: must be near the pickup, must have waited th
Single lightweight endpoint that returns badge counts for every notification source the operator console renders — healt
A planned extension that moves the optimiser from combining trips to assigning them — allocating trips to specific drive
A planned extension that lets the optimiser react to in-flight events — cancellations, no-shows, delays — by replanning
Groups eligible trips into evaluation pools before they're optimised, so the engine only ever compares genuinely combina
Hierarchical merge-preference resolution: each actor (Customer, Account, AccountDepartment, Trip) can declare a MergePre
A planned extension that reshuffles work at the segment level: instead of merging whole trips, it can take segments from
Proof of Delivery coming soon
Captures proof of completion — signature, photo, delivery code, plus who/when — against the Package at the delivery stop
Real-world routing for any two points — driving distance, duration and turn-by-turn geometry
A TripSchedule links a master Trip to a recurrence pattern (TripSchedulePlan) so the platform clones the trip on every m
Append-only record of every release-timing decision for a trip — the initial CREATE/UPDATE from the learned release-time
Operator-managed groups that pause one or many recurring trips for known disruptions — bad weather, voting days, school
Extra safety monitoring for a special-category passenger once they are on board — tighter alerts for a driver going GPS-
Driver-initiated counterpart to automatic zone entry: a driver declares the zone they are driving to and reserves a queu
Per-stop time windows constrain when a pickup or dropoff may happen — a customer's "between 9 and 10am at the school", a
Heatmap endpoint returning per-H3-cell outbound traffic congestion factors at a given day-type + time-slot
Guarantees a shared ride never exceeds the vehicle's capacity
Time-bound soft indicator that an operator is currently editing a trip
Architectural overview of the lifecycle-guard subsystem: pre-flight checks that block or surface advice on a trip transi
HTTP API powering the operator console health dashboard: traffic-light summary of WARNING / CRITICAL counts across all a
Continuous monitoring of every active trip for risk conditions — late prediction, stale GPS, allocation risk, tight wind
Architectural overview of the trip-health subsystem: how checks are evaluated each sweep, the WARNING / CRITICAL severit
Reusable, at-any-stage answer to "is this trip running late, and by how much" plus a SYSTEM/DRIVER/CUSTOMER fault decomp
An end-to-end view of how a trip moves through its states — from booking through allocation, dispatch and in-progress to
The continuous optimisation sweep
An overview of how the platform combines and sequences trips for efficiency: the merge-strategy hierarchy that decides w
HTTP endpoints to manually trigger booking-time preauth, trip-end capture, or refund on a specific segment
How a booking becomes the concrete work a driver carries out — resolving it into executable units, deciding how segments
A unit of work is one self-contained run of driver work — typically an uninterrupted sequence of stops
Operator-defined categories that classify trips based on a JSON decision tree (e.g
Records every booking that was rejected before becoming a Trip — explicit operator decline, no-supply (no driver availab
How the platform reasons about time across a trip — the derived timing metrics (such as acceptable arrival and dispatch
A TripSegment is one leg of a Trip — the work between two stops with its own pickup, dropoff, capacity requirements, lif
A TripSegmentStop is one waypoint on a segment — pickup, dropoff, or intermediate stop
A comprehensive read-only view of a single trip — timeline, driver/vehicle, account + custom fields, per-segment stops w
A Trip is the top-level booking record on the platform
Automatically places drivers into the zones whose areas they enter

Domain

Dispatch

Allocation, offers, queues, and zones.

When a trip is flagged as at-risk (low supply / approaching cutoff / capacity-gated), dispatch promotes it to a manual d
When a feeder queue's drivers can't cover a trip, its BackupQueueGroups widen the trip's eligibility pool over time — ea
When a primary zone has no driver supply, dispatch can fall back to a BackupZoneGroup — an ordered list of feeder zones
Operators can manually assign a trip to a specific transporter, bypassing the normal dispatch flow
Records every dispatch sweep decision (candidates evaluated, scores, exclusions, offers created/rejected/expired) into a
A time-limited, one-to-one binding between a trip and a candidate driver
A Zone is a tenant-defined geographic area used by the dispatch engine
Queues are ordered driver lists scoped to one or more zones
The single place dispatch decides how wide to search for a candidate driver
Dispatch mode where eligible drivers receive direct trip assignments instead of offers — no accept/reject loop, no expir
Driver-self-service staging window before a pre-booked trip enters auto-dispatch
Makes WORKING transporters dispatch-eligible when they are close enough to their final drop-off that they can plausibly
Per-zone overrides for how dispatch falls back when supply is short

Domain

Fleet

Drivers, vehicles, capabilities, and compliance.

Operator-defined approval / preference list of Drivers authorised to transport a specific Special Category Passenger
HTTP API for driver compliance documents: list / get / upload / replace / soft-delete licences, certifications, badges,
Driver Shifts coming soon
Ahead-of-day roster for the driver pool: a DriverShift carries a date + working window + status, plus working-hours / re
A Driver is the worker entity — the person who operates a Vehicle
Customer-side preference: customers can request specific Drivers and dispatch favours them within a soft window (mode ca
A fleet group is a shared operational pool across several fleets
A Fleet is an organisational grouping of Drivers + Vehicles run by a single sub-operator (commonly a franchise, a depart
Gates whether a given Driver+Vehicle pairing is VALID to form — the operability axis, deliberately separate from Capabil
Plans the vehicle pool as a separately-managed resource: which vehicles (by VehicleType — truck vs van) are in service o
How the platform decides which driver and vehicle qualify for a trip — combining what the vehicle can do with what the d
HTTP API for vehicle compliance documents: list / get / upload / replace / soft-delete insurance, NCT/MOT, tax disc, cal
Records the legal owner of each Vehicle — useful where vehicles are rented, leased, or owned by contractors rather than
Operator-defined vehicle classifications (Standard, Executive, MPV, Wheelchair-Accessible, etc.) — they define the passe
A Vehicle is the physical asset operated by a Driver

Domain

Account

Corporate accounts, departments, and contract billing.

Per-Account custom field definitions: tenants can require arbitrary data at booking time (e.g
Departments inside a corporate Account
Links a Customer to a corporate Account (with optional department membership)
How a corporate account is structured — the account as the top-level business record, departments as budget and reportin
Corporate / B2B accounts that book and pay collectively for many passengers

Domain

Customer

Passengers, saved addresses, and preferences.

Customers accrue loyalty miles automatically on trip completion
Per-customer toggle controlling whether their trip segments can be merged with other trips or excluded from multi-load o
Per-customer address book entries with usage telemetry — pickup and destination counts, last-used timestamp
The Customer entity is the passenger record — first/last name, phone (normalised E.164), email, default account, default
Tokenised cards on file for a customer
SCPs are passengers who travel under another customer's account — typically children on school runs, dependents in medic

Domain

Payment

Quotes to charges, pre-auth, and settlement.

End-to-end pipeline that takes a trip segment from booking → Quote → Price → TripCharge → TripPayment
A hold placed against the customer's payment method when the trip is booked, guaranteeing funds are available before the
A public endpoint that receives event callbacks from the payment processor (a mock processor in development; a real gate
How payments fit together across the platform — from a booking-time hold, through the charge and its line items, to capt
A captured payment — the money actually taken from the customer at trip-end
The aggregate billing record for one segment — net + tax + gross + currency + status

Domain

Surge

Demand-based surge pricing, detection and driver pools.

The driver side of Surge: how a driver opts into a busy cluster, gets sent trips, and earns a share of the pool
Where the customer surge money goes
Continuously finds where demand is genuinely outstripping supply and turns each hotspot into a single, priced live event
The customer side of Surge: when an area gets genuinely busy, a temporary uplift is added to the fare — both to ease dem

Domain

Transporter

Live driver state, location, and shift status.

Passive sweep that runs on every transporter location-sync response: for each ARRIVED stop in the active Unit of Work, c
The high-frequency endpoints the driver app calls throughout a shift — location updates, session refresh, offer accept/r
A Transporter is a Driver-on-shift — the active pairing of a Driver, a Vehicle, and a Fleet during a shift, including au
Every driver location update is kept in two tiers: a live position used for dispatch, arrival detection and drift checks
The sync-tick payload returned to the driver app on every location update — the primary communication channel between th

Domain

Capability

Vehicle capabilities and equipment matching.

The platform-wide catalogue of capabilities — wheelchair access, child seat, pet-friendly, premium/luxury, English-speak
How a tenant opts into the platform capability catalogue

Domain

AreaMetrics

Demand heatmaps and busy-area metrics.

Single source of truth for "is this area busy?" — consumed by trip gating, per-trip health checks, and operator dashboar
HTTP API exposing the learned H3-cell metrics: supply density per cell, demand heatmap, capacity-per-hour estimates by z

Domain

Analytics

Operational KPIs, rankings, and reporting.

HTTP endpoints that query the trip analytics store for outcome-score heatmaps, current-versus-historical comparisons, ti
HTTP endpoints over the customer_snapshot warehouse: lifecycle-cohort counts (the retention funnel) and a paginated, coh
The 0–100 quality score stamped on every finished or cancelled trip segment

Domain

Brand

Per-client branding and white-label presentation.

Multi-brand operations: tenants running multiple consumer-facing brands (e.g

Domain

Region

Geographic regions and region scoping.

Tenant-managed geographic areas (Dublin, Cork, and so on) used to scope a session

Domain

Webhook

Event subscriptions and outbound integrations.

Tenant-configured outbound webhook subscriptions: subscribe a destination URL to platform events (trip.created, trip.sta

Domain

ACL

Access control: roles, permissions and ACL profiles.

Tenant-scoped API keys used by third-party integrations to authenticate against the platform
Operator console users — the people who log in to the operator console to manage trips, customers, drivers, etc
WebAuthn passkey credentials — passwordless authentication via platform authenticators (Face ID, Touch ID, Windows Hello
Named access profiles that grant rights to specific data types and actions through a configurable rule tree
Cross-tenant API keys used by platform-level callers — the scheduler, optimisation and area services, and internal admin

Domain

Address

Addresses, geocoding and saved locations.

Autocomplete-driven address search: it queries a fast per-tenant address cache first and falls back to a global places p
A resolved address with coordinates: postal components, lat/lng, providerId (Google Places ID where available), addressH

Domain

Communication

In-app messaging, conversations/threads and operator↔driver/vehicle notifications.

In-app messaging between operators, drivers and vehicles, and from the system

Domain

DecisionTree

The declarative rules engine used by tariff/modifier/discount/profile/ACL/webhook selection.

Configurable rules engine: tenant-defined JSON decision trees evaluate against runtime context to produce yes/no or rout

Domain

Document

Document storage and verification for drivers/vehicles.

The generic document record: a stored binary asset (such as a licence, insurance, NCT/MOT or tax document) plus its clas

Domain

Statistics

Aggregate operational statistics.

Weekly roll-up KPI snapshots for each entity (driver, vehicle, customer, account, fleet) — trip count, distance, revenue

Domain

Tenancy

The tenant records — Client and Environment entities, client settings and CRUD.

Maps a 3-character tracking-code prefix to the correct tenant database connection
Domain-side view of multi-tenancy: the Client entity as the tenant root, the per-tenant configuration surface, regional
HTTP endpoints to read and update tenant configuration: GET the current Client row, list active clients (SYSTEM auth), G
A Client row represents a tenant organisation on the platform

Domain

TripArchive

Archived trips and their charge snapshots.

Append-only ledger of payment-processor events that arrive AFTER a trip has been archived (active rows pruned, archive s