Overview

SmartGare is a station-local operational platform for intercity bus stations. It maintains carrier and timetable master data, coordinates vehicles and bays, sells traveler tickets, supervises physical movements, publishes passenger information, and settles station financial flows.

Start here

Run SmartGare locally

Start infrastructure, backend, frontend applications, and this documentation.

Understand the architecture

See deployment boundaries, module ownership, events, data, hardware, and frontends.

Work with Referential

Navigate the advanced carrier, fleet, topology, timetable, authorization, and import model.

Build a backend module

Follow the Spring Modulith, hexagonal, persistence, messaging, and testing contracts.

Build a frontend feature

Use the shared package platform and preserve backend business boundaries.

Browse the API

Find the capability map and generated endpoint documentation.

What is shipped

Area	Delivered surface
Referential	29 named capabilities across carriers, vehicles, permits, topology, service catalog, schedules, authorizations, import provenance, eligibility, and MCP
Business rules	Product-declared domains, version drafting, approval, scheduled activation, exact and contextual resolution
Passenger information	Display-point and reusable display-profile administration
Back-office	Eight administrative capabilities over Referential and SIV
Platform	Runtime, module boundaries, security, web contracts, messaging, delivery gates, and MCP endpoint

Allocation, billing, cycle, scheduling, supervision, and ticketing exist as backend module scaffolds. Counter and supervision have application shells and planned boundaries, but no business capability inventory is marked shipped.

Documentation contract

An owning repository's shipped.md or SHIPPED.md inventory is authoritative. A route, table, mock, or backlog item is not shipped behavior by itself. This site synthesizes those living inventories into developer guides and generated reference pages.

One deployment per station

Station names, topology, timezones, fares, penalties, and operating windows are configuration, referential data, or effective-dated rules. They are never product-specific code.