Science1 publisherNot yet confirmed elsewhere2 min readPublished
Posit's shinyapps.io shutdown hands R teams a dated migration, not an optional upgrade
shinyapps.io stops taking new apps at the end of 2026 and existing content is moved automatically in early 2027. Deployment pipelines built for it need editing before then.
The Scientist · Science desk
What happened
- Posit said in January 2026 that shinyapps.io would stop accepting new apps at the end of 2026, with all users moving to Posit Connect Cloud.
- Apps already on shinyapps.io keep running and are then migrated automatically to Connect Cloud in early 2027.
- Deployment automation written against shinyapps.io from GitHub Actions has to be reworked to target the new platform.
- Connect Cloud hosts Streamlit, Bokeh and Jupyter Notebooks as well as Shiny, with unlimited rendered Quarto and R Markdown on every plan.
Compiled by The ScientistSomething wrong?How this is made
Why it matters
- cost A shop that was paying for the top shinyapps.io plan purely to point its own domain at an app hands back $290 a month, or $3,480 a year.
- constraint The recommended replacement is unavailable to free-tier users whose code sits in a private repository, so the cheapest customers keep the maintenance burden.
- decision Every team with an Actions deploy job must pick before the cutoff: give the platform read access to the account, or re-plumb the workflow around a Content ID.
- capability Keeping your own pipeline stays the only way to ship a bundle containing data that never lived in the repository, which trims egress on high-traffic apps.
The break is narrow and mechanical, which is why it tends to sit untouched until a deploy fails. The pattern published on r-bloggers three years ago was a commit hook: push to the repository, and a GitHub Actions job bundled the Shiny source and sent it to shinyapps.io [7]. Most of that machinery survives, because the deployment methods that worked against shinyapps.io still work against Posit Connect Cloud [8]. What changes is the paperwork at each end. The Actions route now begins by obtaining a Content ID [9]. The Git-backed route wants a manifest.json committed alongside the code, which in R is usually one call to `rsconnect::writeManifest()` [10]. Neither is difficult. Both are edits to a workflow file nobody has opened since it was written, on content Posit will move for you in early 2027 whether the edit happened or not [2].
The post's own recommendation is to stop deploying from Actions and let Connect Cloud watch the branch, on the grounds that the deployment work no longer consumes your GitHub Actions allowance [11]. That saves compute minutes, and it also moves where trust sits, since the platform is granted access to the GitHub account [10]. The same post lists the cases where that trade does not close, and they are not exotic for anyone with a review process. You give up deploying only after earlier pipeline checks have passed [12]. You may be barred from granting a third-party tool access to an account that holds sensitive code elsewhere [13]. On the free tier with a private repository, the option is not on the table [14].
The migration therefore sorts teams by how their deployment was built rather than by what their app does. Anyone who shipped by clicking Deploy in RStudio and thinking no further about packages or containers [19] has little to do beyond noting that a free tier survived [5]. Anyone with a gated pipeline has a small rewrite with a deadline attached. On price the direction is not uniform: paid plans sit above their nearest shinyapps.io equivalents [6], while the custom domain that used to require the $349 per month Professional tier now appears on the $59 per month Enhanced tier with an SSL certificate [16][17].
The schedule is the part worth writing down. According to the r-bloggers account, Posit gave roughly eleven months between the January 2026 announcement and the end-of-2026 close to new apps [21], then named a part of a year rather than a date for the automatic migration [2]. A pipeline that breaks during that migration breaks at a moment somebody else picked.
What to watch
- Whether Posit names an actual date for the early-2027 automatic migration rather than a season.
- Whether migrated content arrives with a Content ID and credentials existing CI/CD can reuse, or has to be re-registered by hand.
- Whether Git-backed deployment from private repositories stays off the Connect Cloud free tier.
Clarity's read
What the record supports and how the coverage leans. The claims behind it follow.
Reality
- Evidence52
- Adoption
- Insufficient
- Hype gap+8
- Incentives45
- Confidence55
Claim ledger
Ranked by verification strength, evidence, and original report placement.
- [1]
In January 2026 Posit announced that shinyapps.io would close to new apps at the end of 2026, with all users moving to Posit Connect Cloud.
- [2]
Existing content on shinyapps.io will continue to work before automatically migrating to Posit Connect Cloud in early 2027.
- [3]
Posit Connect Cloud is not restricted to Shiny: it also supports Streamlit, Bokeh and Jupyter Notebooks, and all plans allow unlimited hosting for rendered Quarto and R Markdown documents.
- [4]
Posit Connect Cloud adds the ability to set secret variables, regenerate content on a schedule, higher maximum compute limits, and SSL certificates with custom domains.
- [6]
Paid tiers of Posit Connect Cloud are priced higher than their nearest shinyapps.io equivalents.
- [7]
Three years ago the same publisher posted an example of automating deployment of a Shiny application to shinyapps.io from GitHub Actions: a new commit pushed to the repository triggered a pipeline that bundled the source and sent it to shinyapps.io.
- [8]
The existing deployment methods used for shinyapps.io still work with Posit Connect Cloud, and new options exist, including deployment via the Quarto CLI's quarto publish command.
- [9]
To deploy to Posit Connect Cloud from GitHub Actions, the first step is to obtain a Content ID.
- [10]
Git-backed deployment requires granting Posit Connect Cloud access to your GitHub account so it can monitor the target branch, plus committing and pushing a manifest.json file, often generated by running rsconnect::writeManifest() in R.
- [11]
The post recommends Git-backed deployment in most cases as a replacement for GitHub Actions deployment, because the deployment work is handled by Posit Connect Cloud rather than using up your GitHub Actions allowance.
- [12]
One reason to keep automating deployment from your own CI/CD process is wanting deployment to happen only after earlier pipeline checks are successful.
- [13]
Another reason to keep your own CI/CD is having sensitive code elsewhere in your GitHub account and being unwilling, or not allowed, to grant repository access to a third-party tool.
- [14]
Users on the free tier of Posit Connect with code in a private GitHub repository are listed as a case where deployment must still be automated from your own CI/CD process.
- [15]
A further reason to keep your own pipeline is including extra resources not stored in the GitHub repository, such as a moderately sized read-only dataset, to build a self-contained bundle, which can reduce data export costs on busy applications.
- [16]
On shinyapps.io, a custom domain required the highest $349 per month Professional tier.
- [17]
On Posit Connect Cloud, a custom domain with SSL certificate is available on the $59 per month Enhanced tier and above.
- [18]
Users who followed the previous methodology for automating shinyapps.io deployment from a GitHub Actions workflow will need to adjust their deployment strategy.
- [19]
The shinyapps.io workflow was to build the application, click Deploy in RStudio and have it appear online, without having to think about R packages, building a Docker container or setting up a cloud compute instance.
- [20]
A team that bought a shinyapps.io plan only for a custom domain moves from $349 to $59 per month, a reduction of $290 per month or $3,480 a year.
- [21]
The gap between the January 2026 announcement and the end-of-2026 close to new apps is roughly eleven months.
Sources
1 independent publisher whose own reporting we read for this story.
- r-bloggers.comUsing GitHub Actions to deploy to Posit Connect Cloud
1 article · August 21, 2026
Topics and entities
Follow any of these and your For You feed starts watching them — no settings page required.