Getting started with OrbitPage
Choose an edition, create a workspace and publish a useful first page without overbuilding it.
Last reviewed 24 July 2026OrbitPage works best when the first version has a clear job. This guide takes a new page from an empty workspace to a public URL, while explaining which decisions are easy to change later.
Managed hosting and self-hosting solve different operational problems.
Managed OrbitPage includes accounts, storage, publishing, hosted URLs and maintenance. The open-source edition gives you the application and its source code, while you operate the server, backups, updates and public address.
The editor is built around the same page model in both editions. Choose according to who should operate the software, not according to which edition sounds more advanced.
- Choose managed hosting when editing the page is the job.
- Choose self-hosting when infrastructure control is a requirement.
- Start with Free when you need to validate the page structure first.
Reserve a durable username before polishing the design.
A managed workspace uses its username as the initial public slug. Pick a short, recognizable form of the person, project or business name. You can connect a custom domain later on a supported plan, but printed links and old campaigns may continue to circulate.
Email-and-password accounts must verify their address before the public page becomes available. Google sign-in uses the verified identity returned by Google.
Identity first, one primary action second.
Set the name, a short description and a recognizable image or logo. Then add the one destination that matters most. A useful first page can be only a profile, one primary action and two supporting links.
Use the mobile preview to check hierarchy, but open the real public page before sharing it. The published page is the final rendering surface.
Saving updates the workspace and the public snapshot.
Managed OrbitPage stores the workspace state, validates plan limits and produces a static public snapshot. Public traffic is served separately from the dashboard so a busy page does not need to render through the editor.
Before sharing the address, test every destination in a private window, check the browser title and favicon, and confirm that time-sensitive blocks are still current.
