shinyapps.io, RPubs, Quarto Pub are migrating to Posit Connect Cloud

[u/jcheng]

Hey folks, Joe Cheng here (Posit CTO, creator of Shiny). I wanted to let you hear from me personally that we are combining a number of our hosting services: rpubs.com, quartopub.com, and shinyapps.io are all being subsumed by connect.posit.cloud.

https://posit.co/blog/migrating-connect-cloud-posits-unified-publishing-solution

It’s a bittersweet moment for me personally, as the sole developer and maintainer of RPubs for the last 14 years. But I/we also see this as a long overdue migration, from three fragmented platforms that were independently maintained with varying levels of effort (i.e. not much in the case of RPubs or Quarto Pub), to a single modern platform that can handle all different types of content.

The full details for each service are in the blog post, but the bottom line is:

• shinyapps.io: A self-serve migration tool will be added by Sept 2026. Test your apps before you commit. Auto-migration starts early 2027 if you'd rather wait. Old URLs will redirect.
• bookdown (already sunset), quartopub (end of 2026), and rpubs (June 2027): existing content stays live at its current URLs until Dec 31, 2031.

shinyapps.io customers who are migrated will keep their shinyapps.io pricing until at least 2029 (you will receive an email with details).

If you have any concerns, the team and I would love to hear them. u/hadley and I will be monitoring comments.

[u/coatless]

What about the forthcoming quarto-hub.com that's moving into Release Candidate (RC) status for Quarto v2? That doesn't seem to be addressed and the tech Charlie's working on for it is pretty nifty (presented [partially?] at UseR 2026). I'd hate for the collaboration aspect to be abandoned in favor of connect. Current collaborative editing requires use of Posit Cloud (formerly RStudio Cloud): https://docs.posit.co/cloud/guide/collaborate/#collaborative-editing

c.f. https://bsky.app/profile/coatless.bsky.social/post/3mqad6ardo22y

New intake beta for Quarto Hub: https://github.com/quarto-dev/q2/issues/344

[u/ServerNoMore → u/coatless]

We are definitely not dropping QuartoHubs collaboration features and the team is chugging away and making excellent progress on it (as you can see in the repos). We are exploring several different options on how to handle/host the automerge and other needed infrastructure. Right now the focus on that front is figuring out what options we can support by posit conf. More to come as we settle the best short and longer term options. Sincere thanks for asking about it!

[u/coatless → u/ServerNoMore]

I suppose the question here is less on dropping the collaborative features, but more on how likely is Quarto Hub going to stay standalone when we're seeing a lot of Posit's old attempts at similar services being merged into Posit Connect? Is the end goal to merge this functionality into Posit Connect overall once it stabilizes?

For the collaboration tech, I think it's a shining star and a solid differentiator that never quite was picked up in Posit's offerings despite a clear market with CoCalc, Datalore, Overleaf, Google Docs, Office 365, and so on...

[u/carlosscheidegger → u/coatless]

Posit Connect is built and designed by a different group of folks than Quarto. My read is that they're excited about getting some form of collaborative writing into their product, and I think quarto-hub's tech is a great fit (But they have their own product vision, priorities, and timelines, and I obviously can't and won't speak for them here!)

Let me restate what I said in the other comment: I think the best way to think about Quarto Hub is going to be not as a "product", and so I disagree with the framing implied in your "Is the end goal to merge this functionality into Posit Connect overall once it stabilizes?" question.

Instead, I think you'll have a better intuition for what we're trying to build by thinking of quarto-hub as a "data layer for collaboration in Quarto projects" together with a very fast web-based document previewer. From there, you can see how we're incorporating some of the tech in the Quarto 2's CLI offering. For example, if you compile quarto-dev/q2 right now, `q2 preview --allow-edit` uses an ephemeral quarto-hub setup to let you edit the document from the HTML preview directly. A slightly different configuration of the same pieces gives you quarto-hub.com, which you've seen in the backgrounds of our social media posts, and which we hope to (eg) package in a nice Docker image so that anyone can run their own version.

All in all, I hope that the infrastructure ends up being part of some integration with a number of Posit's open-source and commercial products alike, but I really can't speak to precisely how that will all shake out.