Host Lizmap yourself, or with 3Liz?
Lizmap Web Client is open source software. You can install it on your own server, for free, without asking us anything — and many people do it very well. This page explains when that is the right call, and when it costs more than it looks.
What you actually have to run
Publishing a QGIS map on the Web takes more than installing Lizmap. The full stack is:
- QGIS Server, its memory sizing and its LTR version tracking
- Lizmap Web Client and its version upgrades
- PostgreSQL and PostGIS, their configuration and major upgrades
- a web server and PHP, with their security patches
- TLS certificates and their automatic renewal
- off-site backups, whose restore is actually tested
- monitoring: knowing the service is down before your users tell you
- operating system security patches
Installation, configuration and maintenance involve a significant cost. This is particularly true in the long term: software vendors are releasing patches with increasing frequency, including fixes for vulnerabilities.
Updates should not be overlooked: the security of your data depends on them.
The full cost, side by side
| A server you run | Lizmap Cloud | |
|---|---|---|
| Server | to rent and to size | included |
| Initial setup | 1 to 3 days | included, free up to the Basic plan |
| Lizmap and QGIS Server upgrades | on you, several times a year | included |
| TLS certificates | to automate and to watch | included |
| Off-site backups and restore tests | to set up | included |
| Monitoring and hardware on-call | on you | OVH 24/7 + 3Liz software monitoring |
| QGIS project validator | unavailable | included |
| Administration time | recurring, to be costed in your context | none |
| Salaries of staff qualified to manage hosting | recurring, to be costed in your context | included |
What you cannot get separately
- The QGIS project validator. We wrote it to operate our own platform: it regularly analyses your projects and reports invalid layers, broken paths, missing rasters and memory-hungry projects. It is only reachable from a Lizmap application hosted with us.
- 3Liz business modules, packaged and maintained — Cadastre, Adresse, OpenADS, NetADS, SAML, AltiProfil, MapBuilder, PgMetadata, PgRouting — installed and upgraded along with your instance.
- Access to the team that writes Lizmap. We develop Lizmap Web Client. When a problem comes from the software itself, there is no middleman.
When self-hosting remains the right call
In some situations, hosting it yourself makes more sense.
- Your application must stay on an internal network, with no Internet access.
- Your organisation imposes its own managed-services policy, or has an IT department already running PostgreSQL in production.
- You need very specific PostgreSQL extensions, or a particular QGIS Server version our platform does not offer.
- Your data volume or load is unusual enough to justify a bespoke architecture.
In those cases we can help differently: through support or training rather than through hosting.
Migrating an existing installation to Lizmap Cloud
It is the same software on both sides: your QGIS projects and their Lizmap configuration are carried over as they are, with no conversion and no intermediate format.
- We open your instance
- You edit your projects in QGIS Desktop to change the PostgreSQL server access details used in your layers.
- You upload your projects to our platform and import your database onto it.
- You’re using Lizmap.
And if I change my mind?
Your data remains yours, and you can retrieve it at any time without asking us:
your QGIS projects and files over FTP or WebDAV, your database through a
standard PostgreSQL dump (pg_dump). There is no proprietary format and no
lock-in — Lizmap Web Client is open source software, you can reinstall it
elsewhere and put your projects back as they are.
Lizmap