Why licensing matters as much as features
In PCB and electronics workflows, software capability is only half the equation. The license model can have a direct impact on how efficiently teams work, how IT manages access, and how easily engineers can collaborate across locations.
PCB-Investigator addresses this with three distinct licensing approaches: SOD for online flexibility, Floating for internal shared usage, and Dongle for hardware-bound security. That means you can align the licensing model with your real operational setup instead of forcing your team into a one-size-fits-all structure.
Three options, three different use cases
SOD (Software on Demand / Online-License) is ideal for distributed teams, remote work, and location-independent access. Licenses can be managed centrally and used worldwide, which creates a highly scalable setup. The trade-off is simple: a stable internet connection is required.
Floating licenses run through an internal license server within the company network. Users pull licenses from a shared pool, which improves utilization and avoids assigning one license per person. This is a strong fit for organizations with established internal IT infrastructure.
Dongle-based licenses are the most hardware-dependent option. The license is tied to a USB dongle, making it highly secure and independent of public network infrastructure. It is particularly suited for single-user setups or secure environments where local control is preferred.
What engineering teams gain
- Flexible deployment for different organizational structures
- Centralized control and detailed usage statistics
- Efficient sharing of licenses in internal networks
- Hardware-bound security for controlled environments
- Options for remote, on-premises, and offline-oriented workflows
The right license model removes friction from daily engineering work and helps teams stay focused on analysis, not administration.
Next step
If you are evaluating PCB-Investigator for your team, take a closer look at the license systems and compare them against your infrastructure, security requirements, and collaboration model. The best licensing setup is the one that fits how your engineers actually work.
