![rstudio license rstudio license](https://www.hanss.info/sebastian/post/_ressources/b5a08b2b611d49ef90e10620bba427f7.png)
With floating licensing, professional RStudio product servers lease a license from a persistent micro-server. Deployments with long-running instances, including in docker containers, generally do not need floating licenses. This scenario is most common with ephemeral backends such as Docker containers used outside the context of the Job Launcher feature. Floating licenses can be required in environments where servers often shut down without deactivating the license. Floating licenses require additional setup and are only recommended if traditional licenses are not working with your architecture. By default, RStudio products come with support for activating and deactivating license keys. It is also the best choice for managing ephemeral instances of the other RStudio professional products like RStudio Connect and Shiny Server Pro.
RSTUDIO LICENSE PRO
If you do not have the Job Launcher enabled in RStudio Server Pro but you need to manage multiple ephemeral containers, a floating license may be the right choice. To get started with the Job Launcher, you must have a license that enables it, and then you can use this Getting Started article to set up the local Launcher to get familiar with the most basic configuration.
![rstudio license rstudio license](https://crackspick.com/wp-content/uploads/2021/04/R-Studio-Logo.jpg)
Furthermore, users can submit standalone adhoc jobs to your compute cluster(s) to run computationally expensive R scripts.
RSTUDIO LICENSE SOFTWARE
RStudio Server Pro integrates with the Job Launcher to allow you to run your R Sessions within your compute cluster software of choice, and allows you to containerize your sessions for maximum process isolation and operations efficiency. The RStudio Job Launcher provides the ability for RStudio Server Pro to start processes within various batch processing systems (e.g., Slurm) and container orchestration platforms (e.g., Kubernetes). This is the easiest way to run sessions remotely without having to manage them explicitly via Docker containers and a floating license. With this configuration, you can use a traditional license on your main RStudio Server Pro instance, and let the Launcher handle the sessions for you. RStudio Server Pro with Launcher allows you to run R sessions and background jobs on external cluster resource managers.
![rstudio license rstudio license](https://support.rstudio.com/hc/article_attachments/360009708213/active-users.png)
Note that if the Job Launcher feature of RStudio Server Pro is enabled on your license, you are not likely to need a floating license in addition. RStudio Server Pro version 1.1+, RStudio Connect version 1.5.4+, and Shiny Server Pro version 1.5.6+ support floating licenses.