MobilityDB on Ubuntu 24.04 LTS

This is a repackaged open source product with additional charges for cloudimg support services.

MobilityDB by cloudimg

A PostgreSQL database for moving objects. This image delivers PostgreSQL 17 with PostGIS 3.6 and the MobilityDB extension at the pinned upstream release 1.3.0, already installed and ready, with a worked spatiotemporal demonstration over vehicle trajectories the moment the machine boots.

What It Does

MobilityDB turns PostgreSQL and PostGIS into a store and analytics engine for moving objects. Instead of holding a position as a single point, a temporal geometry column records how an object moves through space over time, so one row describes a whole vehicle, vessel or asset trajectory. You then query that trajectory directly with SQL.

Where it stands out:

• Trajectories as first-class data. A temporal geometry point column holds an object's full movement over time, so one row is an entire trip rather than a single fix.
• Spatiotemporal analytics in SQL. Ask where an object was at a given moment, the path it took over an interval, how far it travelled, its speed, and how close two objects ever came.
• Indexed and integrated. Temporal types sit on top of PostGIS geometry with GiST indexing, so spatial windows, time slices and nearest approach queries stay fast, right next to your relational data.

What Is Included

• PostgreSQL 17 from the official PostgreSQL PGDG repository, running under systemd
• PostGIS 3.6 and MobilityDB 1.3.0 from the PGDG repository, with the extension already created (PostGIS is preloaded for you)
• A demonstration database with three vehicle trajectories stored as temporal geometry points and a spatiotemporal index already built
• A least-privilege application role for your app to run spatiotemporal queries, separate from the administrator
• Fully patched base with unattended security upgrades enabled
• 24/7 cloudimg engineers handling upgrades, tuning and configuration

Secure By Default

Every role in the shipped image has no password at all, and TLS is disabled, so the database cannot be reached from the network in the image itself. On first boot each machine mints unique passwords for the administrative and application roles plus a unique TLS certificate, into a file only root can read. Two machines never share a secret, and this is proven by launching two and comparing. Remote clients are accepted only over TLS, and no trust rule exists anywhere in the access configuration.

A credential guard runs on every boot. It proves the recorded credential genuinely authenticates, then attempts authentication with published and example values, including those used in the documentation. If any succeeds it stops the database rather than serve a known credential. It authenticates rather than inspects, because the database stores a salted hash and never the password, so an inspection based check could never match and would pass silently forever.

Getting Started

1. Launch the image on Standard_B2s or larger 2. Read the per machine credentials from the root only credentials file 3. Query the demonstration trajectories: where a vehicle was at a time, and which trajectories crossed a map window

Licensing and Pricing

MobilityDB is licensed under The PostgreSQL License and is free; there is no per-seat fee. PostGIS is licensed under the GNU General Public License version 2.0 or later, and PostgreSQL under The PostgreSQL License; attribution ships inside the image. The cloudimg charge of 0.04 US dollars per vCPU hour covers packaging, security patching, image maintenance and 24/7 expert support. Restrict the database port to your application subnet before you put real data on it.

cloudimg Support

24/7 technical support by email covers deployment, upgrades, schema design and tuning. Critical issues receive a one-hour average response.

cloudimg is not affiliated with or endorsed by the MobilityDB, PostGIS or PostgreSQL projects. All product and company names are trademarks of their respective holders.