With MapTiler Server 4.4, we introduced the option to activate your MapTiler Server instances
using floating licenses.
In this article, you can find an overview providing a clear understanding of what they are, how they work, and the advantages they bring when you need private map services running on-premises or offline.
Instance - single occurrence of MapTiler Server (for the administration of MapTiler Server)
Node - device/machine
Admin - users of MapTiler Server
End-Users - end-users of your application (internal or external)
Benefits of Floating Licenses
Floating Licenses allow for more flexible and scalable usage of MapTiler Server.
You can activate all your instances from a central pool of licenses, instead of having node-locked ones.
Each floating license can be set to allow more than 1 concurrent instance.
This enables multiple admins to run numerous MapTiler Servers simultaneously.
An example: the MapTiler Server floating license is set up to 3 concurrent instances. This means that the software can be used by 3 different admins on 3 different nodes at the same time.
If a 4th admin wants to use it with the same license, one of the three active admins' licenses needs to be deactivated.
Note: It's impossible to affect a particular MapTiler Server instance from multiple nodes.
Every single node runs its own MapTiler Server instance that reads Map Styles and Tiles from a local directory.
Bear in mind that this does not affect the number of the end-users.
The limit of the end-users in production applications is equal to the total number of Monthly Active Users (MAUs) allowed in your subscription: Basic - 100 MAUs, Business - 1000 MAUs, Partner - Custom number of MAUs
Types of Floating Licenses
1. Hosted Floating License (Online)
With this option, the software is connected to the MapTiler licensing infrastructure so it requires a web connection.
All the machines need to be connected to the internet, being all tight to the MapTiler licensing infrastructure.
2. On-Prem Floating License (Offline)
An on-prem floating license allows you to set up your own licensing infrastructure
(MapTiler License Server) and distribute the licenses in your private network.
Because of that, it does not require a web connection.
The infrastructure needs to be set up on a "Host server” which is a fixed or permanent machine
(not a Docker or VM). This machine needs to be running at all times.
All the instances must be connected to the host machine through an on-premise connection to be able to "borrow" the licenses from the MapTiler License Server.
The Server is activated offline, via the DAT file which requires cooperation with our support team.
The DAT file needs to be generated and sent to the MapTiler Team which will activate it and send it back.
Floating License in Docker or Virtual Machine (VM)
Virtualization has become more and more popular for scalable and efficient operations, and the need for adaptable software licensing models is more pronounced than ever.
With that in mind, we developed the floating license so it's very useful, especially with Docker and VM deployments.
Docker or Virtual Machines, provide the flexibility to scale resources up or down based on demand. When using floating licenses in a Docker container or VM environment, the licensing server can handle the dynamic nature of Docker or VM scaling, to ensure optimal license distribution.
Floating licenses offer flexibility in terms of license mobility. Admins can move licenses between docker containers or VMs as needed, responding to changes in workload or infrastructure requirements.
Note: Offline activation of the MapTiler Server license can not be performed on Docker or Virtual Machine.
If your deployment environment does not allow you to host the software on the fixed machine, the solution is to obtain the pre-activated binary which is ready to use MapTiler Server.
Floating licenses in MapTiler Server are useful when you need maps to be integrated into multiple different projects/applications.
Running MapTiler Server instances on new nodes, means totally new MapTiler Server admin.
At the moment, there is no solution for affecting the same admin from multiple nodes because of reading the data from local directories.
How can I get it?