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,
multi-tenant service at orkyo.app; Orkyo Community is the self-hosted, single-tenant
edition you run on your own infrastructure. The planning product — utilization, requests,
spaces, people, insights, settings — is identical in both.
What differs
| SaaS | Community | |
|---|---|---|
| Hosting | Operated for you at orkyo.app |
Self-hosted on your infrastructure |
| Tenancy | Multi-tenant; each organization has its own orkyo.app/… workspace |
Single tenant per installation |
| Multiple organizations | Yes — Switch Organization and the Select Organization page | One organization per deployment |
| Plans and tiers | Free, Professional, Enterprise (paid tiers listed as Coming Soon — register interest from the Plans tab) | No tiers — everything is available |
| Reporting API & Audit Log | Included from the Professional tier | Included |
| Platform configuration | Managed in the SaaS admin console | Environment variables at startup |
| Installation & operations | None — sign up and go | See Install Orkyo Community |
Two practical consequences:
- Features that are tier-gated on SaaS — the read-only Reporting API and the Audit Log — 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
Pick SaaS when you want zero operations and a hosted workspace your team can reach immediately. 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.