3 Things To Consider About SOLIDWORKS Licensing
Choosing the right SOLIDWORKS licensing approach isn’t just an IT checkbox — it affects how your team works, how you budget, and how quickly you can scale. Below are three key things to weigh when deciding what’s right for your company.
1) SNL (SolidNetWork License) vs. Stand-alone
What they are
-
SNL (SolidNetWork License) — a network/floating license managed by a license server. Licenses are pooled and checked out when a user opens SOLIDWORKS; they return to the pool when the user closes the application.
-
Stand-alone — a node-locked license tied to a single machine (or a single named user/activation). It’s independently activated on each workstation.
Why it matters
-
Teams & efficiency: SNL is ideal for groups who don’t all need SOLIDWORKS at the same time. A properly sized SNL pool reduces overall seat count and cost by sharing licenses across engineers, contractors, and power-users.
-
Simplicity & offline use: Stand-alone seats are simple to manage for single users or isolated machines (e.g., secured workstations that rarely connect to a network). No server is required and they’re often easier for disconnected or field environments.
-
Administration & infrastructure: SNL requires a server, some IT setup, and ongoing administration (updates, backups, monitoring). It can be a single point of failure if not highly available. Stand-alone avoids that overhead.
-
Flexibility features: SNL supports license borrowing (temporarily checking a floating seat out for offline work), centralized monitoring, and easier management of concurrent use. Stand-alone requires deactivation/reactivation to move seats.
Quick rule of thumb
-
If you have multiple engineers who don’t all run SOLIDWORKS full-time, SNL usually wins on cost and flexibility. If a single user needs a guaranteed, always-available seat (or you have isolated workstations), stand-alone may be simpler.
2) Perpetual + Subscription (Maintenance) vs. Term (rental)
What they are
-
Perpetual + Subscription (Maintenance): You purchase a perpetual SOLIDWORKS license (you own that release) and pay an annual subscription/maintenance fee to receive upgrades, technical support, and access to new versions during the maintenance period.
-
Term (rental) license: You pay for the license for a fixed period (monthly/annual). While the term is active you get updates and support; when it ends you lose access unless renewed.
Key trade-offs
-
Upfront cost vs. long-term cost: Perpetual requires higher upfront CAPEX but can be cheaper over a long horizon. Term is OPEX-friendly with lower initial cost but may cost more over many years.
-
Flexibility: Term licenses are great for short projects, contractors, or seasonal spikes — you can scale down without being stuck with unused perpetual seats. Perpetual is better when you plan to keep the software for many years.
-
Access to updates/support: Both models provide updates and support while maintenance/term is active. If you let maintenance lapse on a perpetual license, you can continue to use the last version you owned but lose access to updates and support.
-
Budget predictability: Term makes budgeting predictable and can simplify procurement. Perpetual with active maintenance offers long-term stability and the security of ownership.
-
Resale/transfer: Perpetual licenses can sometimes be transferred per DS-owned rules and your reseller’s policy; term licenses typically cannot be “owned.”
Pick based on strategy
-
Choose perpetual + maintenance if you expect long-term use and want to control total cost of ownership.
-
Choose term if you need flexibility, want to avoid large upfront cost, or expect your licensing needs to change rapidly.
3) Usage limitations — regions, concurrent users, hosting & other gotchas
Licensing isn’t only about seat counts. There are practical constraints and policies that affect how you deploy SOLIDWORKS.
Region / Territory
-
SOLIDWORKS licenses are governed by the End User License Agreement (EULA) and reseller terms. Some licenses are restricted to a licensed territory — running seats in other countries or moving seats across borders can have compliance or administrative implications. If your team is multi-national or you routinely have users working offshore, check territory clauses with your reseller.
Concurrent users & pooling
-
With SNL the number of concurrent users is what matters. You must understand peak usage and factor in borrowing and sessions left open overnight (stale sessions tie up seats). Monitor SNL logs and consider timeout/cleanup policies to maximize utilization.
License borrowing & offline use
-
SNL allows borrowing a license for an offline period, but borrowing terms (length, number of borrows) should be configured and understood. Borrowed seats don’t return to the pool until they expire or are returned manually.
Hosting the SNL / Cloud & virtualization
-
You can host the license server on-premise or through a hosted/cloud provider — or run SOLIDWORKS in virtual desktops (VDI, RDS). Each approach has licensing and support implications:
-
Hosted/cloud solutions usually require validated architectures and may need additional configuration. SOLIDWORKS is supported on certain virtualization platforms and with certified cloud providers; EpiGrid is the only Certified SOLIDWORKS Partner that provides Cloud-hosting.
-
Using a third party to host your SNL is possible and sometimes convenient, but verify support, SLA, and security.
-
Running SNL or SOLIDWORKS in virtual environments may impose extra admin overhead and require follow-up with DS/reseller to ensure compliance.
-
-
Best practice: Use SOLIDWORKS-certified cloud/virtual providers or work with your VAR to design and validate the environment.
Other limitations to watch
-
Add-ons & modules: Many SOLIDWORKS add-ons (e.g., Composer, Simulation, PDM) have separate licensing rules and counts. Don’t assume one seat covers everything.
-
Named user vs device licensing: Some tools or bundles may be licensed by user rather than device; understand which model applies to your products.
-
Support & upgrade access: Access to downloads, tech support, and major upgrades requires active maintenance/term. If you rely on vendor support, plan your maintenance accordingly.
Practical tips before you decide
-
Audit real usage. Look at peak concurrent sessions rather than installed seats. SNL logs are gold for this.
-
Match business needs. Use term licenses for contractors/seasonal needs; use perpetual for core, long-term engineers.
-
Plan for remote and hybrid work. If engineers work remotely, confirm borrowing, VPN, or cloud hosting compatibility.
-
Talk to your VAR. Resellers (like Converge) can pull usage reports, model scenarios, and recommend an architecture or licensing mix that fits your team.
-
Consider lifecycle & upgrades. If staying current with the latest SOLIDWORKS features is critical, maintain active subscription or term coverage.
Need help choosing?
If you’re evaluating the best SOLIDWORKS licensing approach for your team size, budget, or infrastructure plans, we’re happy to run the numbers and map options to your workflows. Licensing decisions are easier (and less expensive) when they’re based on actual usage and a clear run-rate forecast — let’s talk.


