How to Choose the Right Devolutions Package for Your IT Team

Updated

Devolutions bundles its products into four solution packages, each aimed at a different use case: remote desktop management & IT operations, privileged access management (PAM), IT automation, and remote access management. To choose, match your team's primary pain point to one of those four, then check the package's product mix against what you already own. Pricing is listed on the official pricing page, and purchases can also go through a reseller.

The four packages at a glance

Package Use case Bundled products
Remote desktop management & IT operations Centralize remote connections, manage credentials, enforce access policies, standardize IT workflows RDM, Gateway, Password Manager
Privileged access management Control privileged access, enforce least privilege, rotate passwords, monitor activity, meet audit and compliance requirements PAM, RDM, Password Manager
IT automation with PowerShell Universal Create dashboards, REST APIs, scheduled jobs, and administrative workflows PowerShell Universal
Remote access management Secure entry point for segmented networks; JIT access, session monitoring, MFA enforcement; positioned as a lightweight alternative to VPNs Gateway, Password Manager

How to pick

1. Start from the problem, not the product

The packages are organized by use case, so the fastest filter is the question your team is actually asking:

  • "Our remote sessions and credentials are scattered." Remote desktop management & IT operations is the entry point. Devolutions notes that most teams discover the platform through RDM, then realize the same platform can replace their password manager, PAM tool, and scripting patchwork.
  • "We need to control, rotate, and audit privileged accounts." Go to the PAM package. It covers just-in-time elevation, automatic password rotation, session monitoring, and an audit trail.
  • "Our routine IT work should be scripted, not manual." PowerShell Universal is the automation package. It turns PowerShell scripts into dashboards, REST APIs, and scheduled jobs.
  • "We need a secure way into segmented networks without a full VPN." Remote access management pairs Gateway with Password Manager for JIT access, session monitoring, and MFA enforcement.

2. Check what each package actually bundles

The packages overlap, which matters if you are adding to an existing deployment rather than starting fresh. RDM and Password Manager appear in more than one package, and the PAM package includes both of them alongside PAM itself. If you already run RDM, the incremental decision is usually whether you need PAM, Gateway, or PowerShell Universal on top — not whether to switch tools.

3. Confirm platform coverage

The connection and credential products list Windows, macOS, Linux, iOS, and Android support. If your team is mixed-platform, verify the specific product you are buying covers the endpoints you manage before committing.

4. Size the decision against adoption signals

Devolutions cites 1M+ IT professionals, 140+ countries, 200+ integrated tools, and 15K+ community members. These are useful as a maturity signal for the ecosystem (especially the 200+ integrations, which affect how well RDM fits your existing stack), not as a reason to pick one package over another.

Pricing and where to buy

  • Pricing page: https://store.devolutions.net/pricing?l=en — the official place to see current package pricing.
  • Reseller list: https://devolutions.net/buy/reseller-list/ — find a reseller if you prefer to buy through a partner.
  • Reseller program: https://devolutions.net/buy/reseller/ — for partners.

One concrete data point from the site: the IT automation package lists a PowerShell Universal Developer edition at $0, with free and full editions available. Treat that as the entry point for automation only — it does not tell you the cost of the other three packages, so check the pricing page for those.

A practical selection sequence

  1. Write down the single biggest gap: scattered connections, unmanaged privileged accounts, manual scripting, or insecure remote entry.
  2. Map that gap to the package in the table above.
  3. List the products in that package and cross off any you already license.
  4. Check platform coverage for your endpoints.
  5. Pull current pricing from the official page, or contact a reseller if you need a quote or local invoicing.

If two packages seem to fit, the PAM package is the broader one — it includes RDM and Password Manager, so it covers the remote-connection and credential-management needs as well as privileged access. Choose the narrower remote desktop management package only if privileged access control and auditing are not yet a requirement for your team.