SaaS or Community?
How the hosted Orkyo SaaS and the self-hosted Community Edition compare, and how this documentation covers both.
Orkyo ships in two editions built from the same core. Orkyo SaaS is the hosted service at
orkyo.com, and it hosts many isolated workspaces. Orkyo Community is the self-hosted
edition that you run on your own infrastructure, with one workspace per installation. The planning product — utilization, requests,
stations, assets, insights, settings — is identical in both.
What differs
| SaaS | Community | |
|---|---|---|
| Hosting | Operated for you at orkyo.com |
Self-hosted on your infrastructure |
| Workspaces | Many, isolated from each other. Each organization gets its own <slug>.orkyo.com subdomain |
One workspace per installation |
| Multiple organizations | Yes — Switch Organization and the Select Organization page | One organization per deployment |
| Plans and tiers | Free, Professional (Coming Soon — register interest from the Plans tab), Enterprise (by agreement — contact us) | No tiers — everything is available |
| Tier-gated features | Reporting API, Audit Log, Data export / import, Calendar subscriptions — included from the Professional tier | All included |
| Platform configuration | Managed in the SaaS admin console | Environment variables at startup |
| Installation & operations | None — hosted by Orkyo (access by invitation during early access) | See Install Orkyo Community |
Two practical consequences:
- Features that are tier-gated on SaaS — the read-only Reporting API, the Audit Log, data export / import, and calendar subscriptions — are simply available in Community.
- Community configuration happens at deployment time (environment variables), so its in-app Administration area is smaller; day-to-day settings are the same in both editions.
How this documentation handles editions
Shared behavior is documented once. Pages and sections that apply to only one edition carry an explicit badge — SaaS or Community — and edition-specific sentences say so inline (“On SaaS, …”). If a page carries no edition badge, everything on it applies to both.
Choosing
If you are not sure, use the fit check first. Pick SaaS when you want zero operations and a hosted workspace your team can reach without running anything — during early access that means applying to the Design Partner Program. Pick Community when your data must stay on your own infrastructure or you want full control of the deployment. Because both editions share the same core, the skills — and this documentation — transfer either way.