Skip to content


Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?

Latest commit



Failed to load latest commit information.
Latest commit message
Commit time



(pronounce [navi-sia])

Version Build status License Chat Code Coverage Vulnerabilities Security Rating
version Last build license chat SonarCloud Coverage SonarCloud Vulnerabilities SonarCloud Security Rating
Maintainability Quality Gate Duplicated Lines (%) Reliability Bugs Lines of Code
SonarCloud Maintainability Rating SonarCloud Quality Gate Status SonarCloud Duplicated Lines (%) SonarCloud Reliability Rating SonarCloud Bugs SonarCloud Lines of Code


Welcome to the Navitia repository!

Navitia is a webservice providing:

  1. multi-modal journeys computation
  2. line schedules
  3. next departures
  4. exploration of public transport data
  5. search & autocomplete on places
  6. sexy things such as isochrones


Navitia is an open-source web API, initially built to provide traveler information on urban transportation networks.

Its main purpose is to provide day-to-day informations to travelers.
Over time, Navitia has been able to do way more, sometimes for technical and debuging purpose or because other functional needs fit quite well in what Navitia can do or just because it was quite easy and super cool.

Technically, Navitia is a HATEOAS API that returns JSON formated results.

Who's who

Navitia is instanciated and exposed publicly through
Developments on Navitia are lead by Hove (previously Kisio Digital and CanalTP).
Hove is a subsidiary of Keolis (itself a subsidiary of SNCF, French national railway company).

More information

Getting started

Want to test the API?

The easiest way to do this is a to go to
Signup, grab a token, read the doc and start using the API!

For a more friendly interface you can use the API through navitia playground (no matter the server used).

Want to use your own datasets or infrastructure?


The easiest way to have your own navitia is to use the navitia docker-compose.

If you don't want to use the prebuilt docker images you can use the fabric scripts we use to deploy to
⚠️ WARNING ⚠️ Those scripts should be usable, but they are not meant to be completely generic and are designed for our own servers architecture.
Use this only if the docker does not suit your needs and if you are an experienced user 😉

Want to dev and contribute to navitia?

If you want to build navitia, develop in it or read more about technical details please refer to

Curious of who's contributing? ⏯️

Architecture overview

Navitia is made of 3 main modules:

  1. Kraken is the c++ core (Heavy computation)
  2. Jörmungandr is the python frontend (Webservice and lighter computation)
  3. Ed is the postgres database (Used for preliminary binarization)

Kraken and Jörmungandr communicate with each other through protocol buffer messages sent by ZMQ.

Transportation data (in the NTFS, or GTFS format) or routing data (mainly from OpenStreetMap for the moment) can be given to Ed.
Ed produces a binary file used by Kraken.


More information here:


Navitia is written in C++ / python, here are some alternatives: