Your Zo is a personal server, so there’s more than one way to put things online from it. Each option is built for a different kind of thing. This page is the map.
Every Zo user gets one personal domain at yourhandle.zo.space. Space is for quick, focused creations that live at a stable URL: a landing page, a tip calculator, a webhook endpoint, a small React widget. There’s no project to set up. Just ask Zo to “make my zo.space home page a personal landing page” or “create an API at /api/data on my zo.space” and it’s live.Pages on your Space are private by default (only you can see them when logged in), but you can make them public. APIs are always public, and uploaded assets are always publicly accessible.
Reach for Space when you have one small thing in mind and you don’t want to think about folders, frameworks, or deploys.
A Site is a full website project that lives as a folder on your Zo. It’s built on Hono and Bun, and if you ask for a database it’ll use SQLite by default. Because the site lives on your personal server, it can read and write files in your workspace, save form responses to a database next to your other files, and pull in any folder you mention while chatting with Zo.Sites are private by default. Only you can open the URL while signed in to your Zo. When you click Publish, the site becomes a public service at sitename-yourhandle.zocomputer.io.
Reach for Sites when you want a real project you’ll keep evolving, or when the site needs to integrate with your files, your AI, or a database.
A service is a long-running process on your Zo: any program that listens on a port or runs in the background. Services give you the most flexibility, because you can run anything Sites doesn’t cover, in any technology you want. To set one up, you only need a port, an entrypoint, and a working directory. Open the Sites page and go to the Services tab to see what’s running.Services have three modes:
http is a web service. It’s public by default at *.zocomputer.io with no auth. You can also set it private, in which case it lives at *.zo.computer and requires you to sign in. Private services are currently in beta and not available on every account.
tcp is a non-HTTP service exposed at a host and port. TCP services are always public.
process is a supervised background process with no public endpoint. Use it for workers, schedulers, bots, sync loops, or internal-only services bound to localhost (like a Postgres on 127.0.0.1). Process services don’t count toward your hosted-service limit.
You can also point a custom domain at any public service or published site.
Reach for Services when you need a custom server, a database engine, a long-running worker, or anything where you care about the runtime, not just the code.
zo.pub/<your-handle> is your public namespace for sharing files. Ask Zo to “publish this folder to zo.pub” and you’ll get back a link anyone can open. Visitors don’t need a Zo account; they land on a clean listing page and can browse the folder, click any file to view or download it, and grab the whole folder as a zip or tar archive.zo.pub is for sharing, not for running. There’s no private mode and no password protection. Anything you publish is fully public.
Good things to publish to zo.pub: photos, datasets, portfolio PDFs, meeting recordings, static reports, anything you’d otherwise email as a download link. If you need code, auth, or per-user logic, use Sites or Services instead.
