DiPhyxDiPhyx
Workspace
Analytics

R, with the consoleand the plots beside it

RStudio Server, served straight to the browser.No desktop and no VNC — the IDE is the page.

RStudio 2026.09.0-1744 cores · 8 GBServed on 8787
hub://rstudio

$ dxflow workflow create --identity rstudio hub://rstudio --start --link

01Pick a machinecores, memory and a rate per hour
02Create the workflowpulled from the hub, once
03Run it, then stopstopped when the work is done
The application

The R desktop,without a desktop

An editor, a console, a plot pane and a package manager.

Editor and console

Write it, run it, and watch the plot pane redraw in the same tab.

Packages persist

install.packages() writes into the home directory on that volume.

One account

Sign in as USER, which is dxflow unless you change it on a start.

How you run it

An accountand a password

The sign-in page is PAM against a real user, so both halves are set at start.

USERThe account you sign in as, and the one your home directory belongs to. dxflow unless you say otherwise.
PASSWORDChecked through PAM against that account. It ships as dxflow, and everyone reading this knows that.
start it your way

$ dxflow workflow start rstudio --override env.app.USER=ada

$ dxflow workflow start rstudio --override env.app.PASSWORD=something-long --link

The session

One port,and PAM behind it

RStudio checks the password against the USER account.

8787Webthe IDE itself
/volumeStoragethe home directory
Open it from anywhereStart with --link and the page comes back on an HTTPS address.
Set a password firstPASSWORD defaults to dxflow, and everyone can read this page.
Good to know

The library liveson the volume

Home is /volume under the user's name, so what you install today is still installed next week.

install.packages just works

Packages land in the home directory on the volume. A stopped machine does not take them with it.

One account, checked properly

RStudio hands the password to PAM. There is no second door, and no token in a URL.

No desktop underneath

This is RStudio Server, served straight to the tab. No VNC, no window manager, nothing between you and the IDE.

The image

Pulled once,then it stays

RStudio Server arrives as one image. This is what comes down the first time, and what the disk should have free for it.

2.3Gamd64compressed, the way the registry counts it
50GOn diskunpacked, with room to work beside it
ghcr.io/dxflow-ai/rstudio:latestPublished from the hub, pulled on the first start and kept for the ones after it.
amd64 onlyOne architecture is published, so pick a machine that matches it.
What it asks for

What it wants,is what it needs

The definition asks for 4 cores and 8 GB, and the image wants all of it. A start given --fit still caps each step to whatever the machine actually has.

4 cores · 8 GBAsks forwhat the definition writes down
4 cores · 8 GBRuns onthe same figure, with nothing spare
Not neededGPUit works on the cores alone
The ask is the floorThe definition and the image agree on this one, so a smaller machine has nothing left to trim.
--fit caps it to the hostA start given --fit trims each step to what the machine actually has, for that start alone. The definition is never rewritten.

Machines that fit it

RStudio Server asks for 4 cores and 8 GB. Cheapest first.

E2 Standard-4
$0.168/ hour4 cores · 16 GBStart this machine
B4ms
$0.208/ hour4 cores · 16 GBStart this machine
T3 XLarge
$0.208/ hour4 cores · 16 GBStart this machine
Run RStudio Server on your own machinePick a machine that meets it, and it opens about a minute after you ask.
Start RStudio ServerBrowse workflows