System requirements and supported browsers

This article lists what you need to run and use MobilityManager, both as an everyday user in the browser and, for administrators, on the server side.

For everyday users

MobilityManager is a browser-based application, so you do not install anything. You need:

• A current version of a modern, evergreen browser — Google Chrome, Microsoft Edge, Mozilla Firefox, or Apple Safari. Keeping the browser updated ensures the interface renders and behaves correctly.
• JavaScript enabled. The interface is a single-page application and will not load without it.
• Local storage and cookies enabled. The app stores your session and small preferences (such as your chosen interface language) in the browser. If local storage is blocked, some preferences will not persist between visits.
• A network connection to the server address your organization gave you.

Screen size and layout

The layout is responsive. On wider screens you get the full sidebar navigation; below roughly 1024 pixels of width the app switches to a mobile layout where the sidebar collapses behind a menu button. A desktop or laptop is recommended for management tasks such as reviewing Belege (receipts/expense documents) or working with the booking calendar, while drivers can comfortably use a tablet or phone for self-service.

Tip: If the interface looks broken or a page stays blank, first make sure your browser is up to date, then clear the cache and reload. An outdated cached version is the most common cause of display problems after an update.

For administrators and self-hosting

If you operate the platform yourself rather than using a hosted instance, the server side has additional requirements. MobilityManager is built on .NET 10 with an Angular front end, and it supports two database engines.

Both database engines are fully supported; PostgreSQL is the default for local development and is recommended on ARM-based machines. You choose the engine and provide the connection details during the onboarding wizard.

Health and monitoring endpoints

Administrators can confirm a running instance is healthy using its built-in endpoints:

• /healthz — overall health
• /livez — liveness probe
• /readyz — readiness probe

Note: These server-side requirements matter only when your organization hosts the platform itself. If you sign in to an instance someone else manages, a supported browser is all you need.

Related

• The onboarding wizard: configuring your database
• Where to get help in MobilityManager
• Changing the interface language (German or English)