Check the changes on your phone.
Open the preview and click around to make sure everything works. You can check the layout and try the app yourself before pushing to prod.
Review your changes
from anywhere.
If you're working with an agent while you're away from your computer, ask it to run your project on a Sprite. You'll get a live URL you can open on your phone or send to a colleague.
Use a copy on a Sprite to review your changes before pushing them to prod.
SEE HOW IT WORKS
Interactive example
your-agent / portfolio
Copy project and current changes
Install dependencies on the Sprite
Start the app as an HTTP service
01 / BRING THE WORK
The working copy includes your uncommitted edits. It runs separately from your production site.
src/app/page.tsx+24 −8
02 / GIVE IT A COMPUTER
The app runs on a Sprite with its own files, dependencies, and web server.
$
npm run dev
03 / OPEN IT ANYWHERE
Your preview is ready. Public access means your reviewers don't need a Fly.io login.
portfolio-demo.sprites.app
Example URL
ONE PROJECT. TWO VERSIONS.
alex®Independent designer & builder
HELLO, I'M ALEX
I design and
I design and
build websites.
I'm a designer and web developer based in San Francisco.
01 Brand design
02 Web development
AVAILABLE FOR SELECT PROJECTS
Websites for
Websites for
small businesses.
I help small businesses get their websites up and running.
ORBIT®Brand and website design
good thingsWebsite for a design studio
12:42
alex®YOUR SPRITE PREVIEW
Websites
Websites
for small
businesses.
good things
sprites.app
Open the same preview on your phone.
Use a Sprite as your second computer.
Once your project is running there, you can open its URL from your phone or another computer.
Send the preview to a colleague.
Make the URL public and send it over. They can open the app on their own computer without signing into Fly.io.
You can close your laptop.
Once your files are copied and the app is set up on the Sprite, you can keep checking the preview from another device.
TRY IT YOURSELF
Ask your agent to put it on a Sprite.
If you're already working with a coding agent, give it the prompt below. It can copy your current project to a Sprite and send you a preview link.
New to Sprites? Start hereYour agent needs access to your project files and your Sprites account. If the latest changes are on your laptop, it needs to be reachable while the agent copies them. You can also work directly on the Sprite.
A PROMPT FOR YOUR CODING AGENT↗
Create a separate Sprite preview of this project, including my current uncommitted changes. Keep secrets, production credentials, and private data out of the copy. Install the dependencies and run the app as an HTTP service that starts when the Sprite wakes. Check what the app exposes, make its preview URL public, and verify it opens without a Fly.io login. Give me the URL and a summary of the changes so I can review them. Leave production unchanged.
PREFER THE TERMINAL?
Make your preview public.
Once your app is running on a Sprite, run these commands from your terminal:
sprite config update -s my-preview --url-auth public
sprite info -s my-preview
Replace my-preview
with your Sprite name. Anyone with its URL can open the web app without a Fly.io login.
Before you
share the link.
What exactly becomes public?
The web app served at your Sprite's HTTPS URL. Public mode removes the Fly.io login requirement for that URL; it doesn't give visitors a shell or access to the Sprites management API. Any authentication inside your app still applies. Only share an app and data you intend others to access.
Does my laptop need to stay on?
Once the project and its changes are on the Sprite, the app runs there independently. Your laptop needs to be reachable only if your agent still needs to copy files from it. Configure the app as an HTTP service so it can start again when the Sprite wakes.
Will this change my production website?
A separate Sprite preview runs its own copy of the project. Keep it connected to preview data and services, and leave your production deployment alone. Reviewing a preview doesn't merge a branch or ship your changes.
Can I make the preview private again?
Yes. Switch URL authentication back to Sprite authentication to require organization access again. You can also stop the HTTP service or remove the preview Sprite when you're finished.
How is this different from a tunnel?
A tunnel forwards requests to an app running on another machine, often your laptop. Here, the project and web server live on a Sprite. You get a cloud development computer with its own HTTPS URL.
Try your changes
on a live website.
Ask your agent to run your project on a Sprite and send you the URL.
Try Sprites