Rift

Rift vs Sprites

A Sprite is a cloud computer that keeps its disk. Rift syncs a folder to machines you own.

Sprites

Youlaptop
work
api
billing
runs
.env
Fly.io
It stores your files and can read them.
work
api
billing
runs
.env
an organization token
OpenClawOpenClawanother company's agent
uses an organization token
work
api
billing
runs
.env

Rift

Youlaptop
work
api
billing
runs
.env
Rift Cloud
It cannot read your files. It holds only ciphertext.
Fv+a8LdicjU6ce
efFPD/W3GEGTbB
FFu91EY6OfuOIc
j3iz+iV3W5kvab
1hZDb7nJAxjHmy
one folder, read
OpenClawOpenClawanother company's agent
holds its own key
apiread

What Sprites is

Sprites are persistent Linux computers for agents from Fly.io. Each has a 100 GB disk that survives between runs. A Sprite sleeps when idle and wakes in one to two seconds at most. Compute is billed only while it runs, and its filesystem can be checkpointed in about a second.

How they differ

A Sprite keeps its files on its own disk in Fly.io's cloud. Its documentation describes access by organization membership or an organization token. Rift keeps files on every machine you choose and grants one folder at a time.

SpritesRift
IdentitySpritesThe agent has none. It uses a token for the Fly.io organization.RiftA key that each machine and agent makes for itself. No account.
Smallest shareSpritesMembership of the organization, or its token, as its documentation describes it. One Sprite's web address can be made public.RiftA folder, a subfolder or one file, as read or write.
Who checks accessSpritesFly.io.RiftEach machine that receives a file checks the grant itself.
Who can read your filesSpritesNot established. The Sprites pages we read do not say how stored files are encrypted or who holds the keys.RiftOnly the machines you shared with. Rift Cloud holds ciphertext.
When your machines are offSpritesThe disk is kept while a Sprite sleeps. Its documentation does not say the files can be read without waking it.RiftFiles stored in Rift Cloud stay available.
When a run endsSpritesSleep keeps the disk. Destroying a Sprite deletes it for good.RiftFiles the run wrote to a Rift folder are already on your other machines.

Which to choose

Choose Sprites when

  • You want a computer that keeps its disk between runs.
  • You want to pay for compute only while it runs.
  • You want fast checkpoints of the whole filesystem.

Choose Rift when

  • The files should also be on your own machines.
  • Another person or agent should receive one folder and nothing else.

Using them together

A Sprite runs the code and Rift keeps the files. Rift runs on Linux, which is what a Sprite runs.

Use Rift with Sprites

Based on Fly.io's documentation and product page, read in October 2026. Sources: product page, Sprites, lifecycle, checkpoints, networking.

View as Markdown