What is the difference between RStudio Connect and



RStudio Connect and are both products used to share content created by R users. They both have features that make hosting Shiny applications a great end user experience, so choosing between them depends on what you want to publish and how you want to it published.

Product Installed or Hosted Push Button Publishing


R Markdown
Python Content (Jupyter, Flask, Dash) Plumber
RStudio Connect Installed      ● (1) ● (1) Hosted      ● (2)    

(1) Supports advanced features for refreshing, scheduling, and distributing documents
(2) Only when using runtime: shiny in the YAML header

RStudio Connect

RStudio Connect is a publishing platform for all the work your teams create in R and Python. Share Shiny and Dash applications, R Markdown reports and Jupyter Notebooks, dashboards, plots, Plumber and Flask APIs, and more in one convenient place. Use push-button or git-backed deployment, scheduled execution of reports, and flexible security policies to bring the power of data science to your entire enterprise. RStudio Connect is software that you run behind your firewall.

Consider RStudio Connect if you can answer yes to these questions:

  1. Do you want push button or git-backed publishing?
  2. Do you want to publish R Markdown documents, Plumber API's, and Python Content in addition to Shiny applications?
  3. Do you want a user interface so that content creators can manage their own data products? is a software as a service (SaaS) product hosted in the cloud by RStudio. It has both free and paid plans. Anyone can publish their Shiny apps to with the push of a button. You don’t need to own a server or know how to configure a firewall to deploy and manage your applications in the cloud. No hardware, installation, or annual purchase contract required. is software that RStudio hosts for you in the cloud.

Use if you can answer yes to all of these questions:

  1. Are you okay with your application being outside your firewall?
  2. Are you okay with the data that the application is pulling from being accessible to our cloud?
    (You have to open up a hole in your firewall if the data is behind the firewall today.)
  3. Are you okay with your end client creating a user account on (if you are looking to use authentication).
  4. Are you okay with a shared computation platform for your analyses? (for example, we don’t have any SLAs today on performance)