Skip to Content

STARTER PACKS / MOBILITY

SHARED MOBILITY GBFS

STARTER PACK

60 DAYS - 4.900€

GBFS PUBLISHING FOR BIKES, SCOOTERS, MOPEDS, AND CAR-SHARING - ONE OPERATOR.

problem

YOU OPERATE A SHARED-MOBILITY FLEET - BIKES, SCOOTERS, MOPEDS, OR CARS - AND YOUR DATA LIVES IN A VENDOR APP. NEITHER YOUR CITY NOR JOURNEY PLANNERS CAN SEE YOUR LIVE FLEET. THE ISSUE IS NOT MORE VEHICLES - IT'S PUBLISHING WHAT YOU HAVE IN A STANDARD ANYONE CAN CONSUME.
YOUR FLEET DATA IS 
LOCKED IN YOUR 
VENDOR APP


Customers see it. Cities don't. Journey planners can't.


CITY PERMITS REQUIRE 
GBFS BUT YOU DON'T 
PUBLISH ONE


Operating permits in many cities now mandate GBFS feeds.

MULTI-OPERATOR ZONES 
ARE INVISIBLE TO USERS



A user opening a journey planner can't see all available shared mobility - only the apps they have.

YOU CAN'T MEASURE 
CROSS-MODE 
INTEGRATION


Are bikes feeding the metro? You don't know. Nobody does.

 
SHARED-MOBILITY OPERATORS DON'T NEED ANOTHER APP. THEY NEED THEIR DATA TO BE STANDARD AND VISIBLE.

solution

HOW WE APPROACH THIS

(simple and a bit refreshing)

We connect to your fleet management system, generate GBFS 3.0 feeds, validate against the spec, and bridge to NGSI-LD for cross-domain integration.


We connect it using:

  • GBFS 3.0 as the open standard for shared mobility.
  • ETSI NGSI-LD Smart Data Models to bridge into the wider mobility context graph.
  • The Vela Context Data Hub.
  • Your existing fleet management system - operator-specific or off-the-shelf.


No replacement of your dispatch or fleet system. No new operations process. No 'enterprise digitalisation committee'.


Once the connection is built → live GBFS feeds publish continuously, journey planners can find your fleet, and the city sees your operations in their mobility data layer.


Then we expand - adding incentive zones, geofencing data, and trip aggregates.

What You Get (in 60 Days)
 
  • GBFS 3.0 feed publishing - system_information, station_information, station_status, free_bike_status, vehicle_types, geofencing_zones.
  • NGSI-LD Context Bridge - your fleet entities also live in the Vela Context Hub for cross-domain queries.
  • Live fleet widget - embeddable map for your website, city portal, or partner sites.
  • Multi-operator friendly - your feed slots into city aggregators alongside other operators.
  • Trip Aggregates (anonymized) - daily and hourly trip patterns for city reporting and your planning.
  • Data Ownership - your data, your context. The city consumes it; you control it.
THIS IS YOUR SHARED-MOBILITY PUBLISHING LAYER, NOT A PILOT.

 

Who This Is For ​
 

Shared-mobility operators that:

  • Run bikes, scooters, e-mopeds, e-bikes, or car-sharing in one or more cities.
  • Have a fleet management system with vehicle status visibility.
  • Need to comply with city permit GBFS requirements or want to be discoverable in journey planners.
  • Want cross-domain integration with public transit, EV charging, parking via NGSI-LD.


Multi-city aggregators or shared-mobility data spaces → see Mobility Data Space STARTING pack.

 

We start with the Starter Pack (one operator, one city or region, GBFS 3.0 publishing) because this gives you 80% of value in 60 days with minimal cost and no risk.

pricing  

STARTER PACK

4.900€

one time setup

(20 working hours included for consulting and developing)


  • Fully managed shared hosted Vela Context Data Hub instance
  • The essentials 

Metadata and data viewer / editor  

Searchable metadata and data portal

Authentication and authorization

Fleet-management connector (vendor API or custom)

Database

NGSI-LD Context Broker

Operator / fleet / vehicle / station / zone hierarchy

Semantic model for shared mobility (NGSI-LD bridge to GBFS)

GBFS 3.0 feed generator with continuous validation

City-aggregator-friendly endpoint 

Live fleet map widget

 Trip aggregates dashboard

Data ownership

API for database access and direct Context broker access


Installation



    Support

    E-mail support (Business hours)

(OPTIONAL) 12 MONTH SUPPORT EXTENSION

990€ per month

    12-month support extension,

     hosting & support, billed monthly after 90 days period

    (5 working hours per month included for consulting and developing)

     Quarterly review session

    New zones / vehicle types / cities onboarded

    GBFS spec evolution support


    Support
     
    E-mail support​

Want the architecture walkthrough?

We’ll show:

  • How your fleet system feeds GBFS automatically.
  • How NGSI-LD bridges shared mobility into the wider city context graph.
  • How journey planners find and use your data.

VELA CONTEXT DATA HUB · ONE SHARED DATA LANGUAGE FOR MOBILITY · EU OPEN STANDARDS (NGSI-LD) · YOUR INFRASTRUCTURE, YOUR RULES