A ready-to-deploy operating layer for municipal digital services. Municipalities bring their data, choose their services, and keep their brand. One operating system serves every surface — mobile app, web app, operator dashboard and REST API. Operational today, not a concept.
Like applications on Android — not modules of a single vendor platform.
Drop any one and the OS collapses into "a platform with extra steps". Each is operational today, not aspirational.
Sensors, transit feeds, registries and third-party APIs collapse into Smart Data Models. The municipality stops integrating — it starts publishing.
Any application that uses Smart Data Models runs on NeoPolis OS. No vendor gatekeeping, no exclusive integrations — the city keeps the right to choose vendors year after year.
MIMs Plus and Smart Data Models make the whole stack reusable across the EU. Build once in Brno, deploy in Ljubljana, scale to the 190+ OASC cities — the investment is reusable, the lock-in absent.
Transit, parking, bike-share, on-demand transport, sensors — each arrives with its own app, its own data and its own dashboard. Citizens juggle multiple apps, operators have no unified view, and data doesn't flow between systems. Building a custom system from scratch takes 12–18 months and significant investment before citizens see any value.
NeoPolis OS connects city data sources through a standardised adapter layer, normalises them into canonical formats, and delivers them to citizens through branded applications. Operators control which services are active through a web-based admin portal. NeoPolis OS is operational today — not a concept, not a prototype.
Coverage. Live across all 212 Slovenian municipalities through national and local data sources, and now in Czechia — national feeds (CHMI air quality, CZPTT rail, PID & KORDIS transit, DATEX II traffic via ŘSD/NDIC) plus Praha and Brno local sources. Poland, Austria and Germany are being assessed for expansion.
A national-data app from day one, then progressively deeper local integration — each new connection is one adapter, not a new project.
A mobile app on the app stores with national transit, weather, traffic, parking and air-quality data. No development needed.
Operator trained on the admin portal. Services configured, branding set, data-quality monitoring live.
Local systems connected — parking sensors, on-demand transport, events, citizen reports. Each integration is one adapter.
Built on EU standards (GTFS, DATEX II, GBFS, SIRI, NGSI-LD) and open-source routing (MOTIS, Valhalla, MapLibre). No single company can switch off the OS.
The trip planner combines private car, public transit, sharing services and park-and-ride in one result — each leg validated against real-time availability.
Drivers share their route; travellers are matched automatically. Rideshare legs appear inside multimodal trip results — not a separate app.
Each city is its own tenant — its own data and GDPR controller, no cross-tenant mixing. The municipality owns its data, not the vendor.
Integrating on-demand services with the trip planner turns expensive door-to-door rides into efficient feeder trips timed to transit connections.
A wave of EU regulation is pushing cities toward open, federated, standards-based infrastructure — and away from closed single-vendor platforms. NeoPolis OS is not waiting for that shift to arrive; it is the implementation a municipality can deploy today to comply with the direction the regulation sets.
| EU initiative | What it mandates or funds | NeoPolis OS alignment |
|---|---|---|
| Digital Europe Programme | Funding for common data spaces, including mobility | Business model built on this shift |
| ITS Directive + 2017/1926 | National Access Points, EU-wide multimodal travel info | Consuming SI + CZ NAPs in production |
| CEMDS | Federated transport data sharing across the EU | SC-PAL = data-space connector pattern with provenance |
| Data Act (2024) | Fair data access, interoperability, portability | Open standards in, standard formats out — no proprietary lock-in |
| NAPCORE | Harmonising 30+ National Access Points | Multi-country NAP integration operational (SI, CZ) |
| Interoperable Europe Act | Cross-border public-service interoperability | NGSI-LD output, Smart Data Models alignment |
| EU AI Act | Transparency, human oversight and auditability for public-sector AI | Authoritative, provenance-bearing runtime agents can cite — not a black box |
The no-lock-in promise is only credible if the OS is genuinely deployable. A SaaS-only product cannot honestly claim "no proprietary runtime" — the runtime would be the lock-in. NeoPolis OS ships in four tiers, with the self-hosted tier as the trust anchor that makes the rest credible.
| Tier | Model | Best for |
|---|---|---|
| NeoPolis Cloud | Managed SaaS, multi-tenant, EU region | Default — small/mid municipalities, fastest onboarding |
| NeoPolis OS Dedicated | Single-tenant managed instance, EU region of choice | Mid/large cities, sovereignty-conscious procurement |
| NeoPolis OS Self-Hosted | Customer-operated, support contract | Large cities, national deployments, sovereignty-mandated tenders |
| NeoPolis OS Federated | Multiple deployments interconnected | Regional/national rollouts, EU programmes, cross-border services |
Cloud is the default; self-hosted is the exit door. Migration tooling is part of the OS, not an add-on — a city can start on Cloud and graduate to dedicated or self-hosted at any time. Even municipalities choosing SaaS feel safer knowing the exit exists; that is what makes "no lock-in" credible rather than rhetorical.
Where the deployment tiers decide where the OS runs, the delivery options decide how much of the front-end we deliver — a continuum from "we ship everything" to "you build on the API". A city can pick any tier with any option, and move along the continuum later with no code change on either side.
| Option | What the city builds | Mobility UX | Time to launch |
|---|---|---|---|
| A · We deliver everything | Nothing — our mobile + web, rebranded | Native, full quality | Days |
| B · Hybrid | Their web; our native shell with embedded panels for their custom services | Native, full quality | Weeks |
| C · Embed our mobility | Their own app, embedding our mobility widget | Our widget (WebView / iframe) | Months |
| D · API only | Everything — they consume the public API | Whatever they build | Variable |
A is the default; B answers "but we already have X." The embeddable mobility widget (cityconnect.travel/embed/trip-planner, themed by URL + coordinates) is what keeps Option C in the OS story — the city ships our trip planner under their brand instead of reimplementing it. Throughout, the municipality is the GDPR data controller and we are the processor under a DPA — and the single codebase is never forked per customer.
The 1.0 "Brno" LTS guarantee — five years of security patches and compatibility — applies to the OS runtime: public APIs, the Keycloak identity layer, the SC-PAL adapter framework, observability, and the operator console. Individual applications carry their own status badge, mirroring the Ubuntu pattern: an LTS kernel with mixed-maturity packages.
First-party applications use the same public APIs available to every third-party developer. No hidden interfaces, no privileged access. Tap any application for the full buyer and developer brief.
Always-on foundations included in every NeoPolis OS deployment — not operator-selectable services, but the OS itself. Tap any capability for the full brief.
Distinct from citizen applications, OS components are reusable building blocks inside the NeoPolis OS runtime — the business, identity, fare and payment layers that city services draw on rather than reimplement.
Apps consume canonical data; adapters produce it. Every source below is in production through the SC-PAL adapter contract, normalised into the canonical NGSI-LD-aligned model. This is the surface city IT teams configure.
Slovenia is at full production coverage across all 212 municipalities. Czechia is live with national feeds (CHMI air quality, CZPTT rail, DATEX II traffic via ŘSD/NDIC) plus Praha (Golemio) and Brno (KORDIS JMK, data.brno.cz) local sources. Poland, Austria and Germany are being assessed for expansion — most reuse the same GTFS, GBFS, DATEX II and NeTEx patterns, so a new country is largely configuration rather than new code. Internal CityConnect orchestration modules (the multimodal trip planner and the municipality directory) are excluded from this count.
Adapters feed data layers; data layers feed services. From the operator portal a municipality controls each hop — enabling, disabling and prioritising data sources to manage the quality of its citizen apps. Changes take effect immediately, with no app update.
Enable or disable independently at three levels — the adapter, the data layer it feeds, and the service that consumes it. Sixteen data layers sit between the data sources and the city services.
Drop a weak source from one service while keeping it everywhere else — e.g. disable a stale parking feed in trip planning but keep it on the parking map. Quality where it matters, without losing coverage.
Each layer has a primary source and ranked fallbacks. If a source degrades, the circuit breaker trips and the layer keeps serving from the next source — operator preferences resume automatically on recovery.
| Source | Scope | Role | What it adds |
|---|---|---|---|
| NAP SiPark | National | Primary | 377 facilities nationwide |
| Brezavta Parking | Celje · Kranj | Fallback | Real-time occupancy for specific cities |
| Celje Municipal Parking* | Celje | Fallback | Local lots via the city's Centralka platform |
* Celje Municipal Parking is connected from the city's own Centralka platform — a bring-your-own-data source merged into the national parking service with no app update.
If a source becomes unreliable, the operator disables it for the affected service while the others keep serving — and re-enabling it instantly adds its data back, no code changes or app updates. The operator controls what citizens see; the OS controls how honestly it is labelled — a stale real-time transit feed is automatically shown as "scheduled only".
Any application that uses Smart Data Models runs on NeoPolis OS without further integration. Apps consume canonical data; adapters produce it. Both are external surfaces of the same OS.
Browse live NGSI-LD entity types in CityData, copy a subscription snippet, and integrate in minutes. First-party and third-party apps speak the same public APIs — Optifarm's OFP and BusinessCore are the first partner entries in the catalogue.
apps@neopolis.tech →Most cities run 5–15 apps and 20–80 adapters. The catalogue is what citizens see; the adapter registry is what city IT configures.
Grafana ships as the first live open-source integration at launch. A pipeline of further candidates is under evaluation for 1.1+ — no single project's vitality is a launch dependency.
Participatory democracy (CityParticipate category). Barcelona-led, strong active community in 2025–2026; Mediterranean-EU credibility.
OGC SensorThings reference implementation, actively maintained by Fraunhofer IOSB.
Citizen reporting (CityReport). Maintained by mySociety; actively developed.
"Powered by FIWARE" certified, H2020-era project. Codebase and city deployments verifiable; community activity modest after the H2020 cycle.
NeoPolis OS is built around the FIWARE reference architecture and Smart Data Models — the same kind of relationship a Linux distribution has to the upstream project. We take the open standards and reference design and deliver them as an opinionated, production-tested distribution: EU residency, pre-built Central-European adapters, a commercial SLA and a five-year LTS commitment. Our APIs already emit NGSI-LD-aligned entities; native context-broker federation is on the 1.x roadmap. Aligning with FIWARE is a foundation we build on, not a box we tick.
EU-mandated and industry formats integrate with zero custom code, and the same adapter works in any member state — a new country connects to its National Access Point rather than needing new code. Proprietary sources get one adapter to the same canonical model, and municipal IoT sensors add hyperlocal granularity on top of national data through the same pipeline.