Install MathLM on a stable, always-on server (Windows, macOS or Linux), install the Wolfram products on your client machines, then point the clients at the server. MathLM must stay running for clients to launch. The full, version-specific steps for installing MathLM are maintained in Wolfram documentation.

It depends on the role. Administrators manage licensing, activation keys and downloads through Wolfram Account, which end users usually can't access. End users don't need it: from the Wolfram Download Center they can download the latest Wolfram application (used for Mathematica, Wolfram Finance Platform and others) or the separate System Modeler application, then point the installed product at your MathLM server.

A single-user license is tied to one specific machine, no matter how many people use that machine, so it fits a personal laptop or a shared lab computer equally well. A network (concurrent) license instead lets the software be installed across many machines and draws from a central pool sized by how many are in use at once, which suits labs, classrooms and shared workstations used across a group. Network-licensed software needs network access to a server running MathLM.

Because a network license needs an active connection to MathLM and grants access first come, first served, a mix of the two sometimes works best. You might use a network license for student use and dedicated single-user licenses for faculty offices. Or you might give a primary user who travels and may not have consistent internet a single-user license and cover most on-premises use with a network license.

You can install it on as many machines as you like. There is no cap on installations; MathLM simply controls how many instances can run at the same time, so what you license is simultaneous use, not the number of installs.

It is the number of sessions or processes that can run at the same time, granted first come, first served. With a Network 5, different machines can rotate through the day as long as no more than five controlling processes are in use at once. If someone launches when all are in use, they may see a "not enough licenses available, try again later" message.

Yes. The monitorlm tool gives a live view of server status and which processes are in use, locally or remotely, so you can tell whether users are hitting the limit. MathLM also writes usage logs, so you can review how many processes were in use over time and size the license correctly.

With a network license, you are not sending your users' work to Wolfram. MathLM runs on a server your organization operates, and clients contact that server for license access, not Wolfram. Computation runs on client machines, so notebooks, data and results stay in your environment unless users choose other Wolfram services. Usage logs are written to your server and controlled by your administrators. Wolfram follows GDPR and CCPA, and you can read more about how Wolfram approaches trust and data security. For teams that want a fully self-contained deployment, Wolfram offers Enterprise Private Cloud.

Your license password (the mathpass file) is generated for your server's MathID, a value derived from the machine that runs MathLM. You provide that MathID when you obtain or move a license so Wolfram can create the correct password file. It identifies the license server, not your users or their work.

We offer various licensing options for offline and off-network use. Please contact us if you wish to discuss details.

Yes. A single MathLM installation can manage network licenses for both Mathematica and System Modeler.

No. MathLM hands out and tracks licenses; it does not run computations. All it needs is a stable, always-on Windows, macOS or Linux server with a reliable network connection.

Each network license has a standard usage zone, and most organizations upgrade to global access so anyone in the organization can use it regardless of physical location.

MathLM can only serve clients that can reach it within a trusted network environment. If your network is partitioned into segments that cannot all reach one server, you will need a separate license server in each partition.

Yes. Because a network license is measured by controlling and compute processes, not by head count, a common use case is a single user running Mathematica on an HPC cluster. Even though it is only one user, that user may draw on the entire pool of compute processes for a single job.

Yes. The shared compute pool can be expanded on its own through core extensions or a power network without increasing the number of concurrent users or controlling processes. Contact us if you are not sure how much compute you need.

Yes. Mathematica can be installed across platforms such as macOS, Linux and Windows, and MathLM connects to those clients regardless of platform.

It depends. Please contact us so our sales team can review your infrastructure and confirm the details.

The smallest configuration sold is Network 2, a network license with two concurrent seats (controlling processes).