Base
Hardened build
minimal ports, security patches applied at build time
pgRouting 4.0.2 with PostGIS on PostgreSQL 18 on Ubuntu 24.04 LTS
Azure
Databases
routing and network analysis inside your database, as ordinary SQL
Overview
pgRouting adds graph algorithms to PostgreSQL, and PostGIS makes them geographic. Give it a table of edges with costs and shortest path, A star, Bellman-Ford, driving distance catchments and connected component analysis all become ordinary SQL queries, with the route handed back as geometry you can draw on a map. Because the graph lives in the same database as the data it describes, there is no separate routing engine to run and no second copy of the network to keep in step. Road closures, one way streets and vehicle restrictions are not features to configure; they are the cost column. Note what is not here: no road network data ships, and this is a SQL library rather than a routing web service, so you bring the network and write the service.
Why the cloudimg image
Every virtual machine initialises its own database cluster on first boot and generates its own superuser password, its own application role password and its own TLS certificate, so no two deployments share a credential or a cluster identity. The database is bound to loopback and every TCP path requires TLS. The image ships a self test that proves the routing answers agree across three independent algorithms and that an unreachable destination returns no route rather than a wrong one. A paired deployment guide and 24/7 support are included.
Common uses
- Shortest path and travel time queries over your own street, rail or utility network
- Service area and delivery zone catchments from a depot or branch
- Network connectivity analysis, such as finding unreachable segments after an import