Table of Contents
- What this audit measures
- The 2026 result
- How availability statuses were assigned
- What the counts mean
- Why page type matters
- How to verify a project
- Choosing the next hosting path
- Frequently Asked Questions
What this audit measures
OpenAlt measures whether a concrete third-party managed-hosting path can be found for the eight most-starred live projects in the Scheduling & Booking category.
This is an availability audit, not a hosting-quality ranking. The sample contains:
- Cal.com
- Cal.diy
- Rallly
- Fider
- Easy!Appointments
- QloApps
- Agenda
- Radicale
Stars determine the sample only. They do not measure hosting quality, operational maturity, security, support, performance, or user demand for managed hosting.
OpenAlt checked two provider surfaces on 2026-09-23:
- PikaPods public app catalogue
- Elestio project-specific open-source pages
The page shell also provides a downloadable CSV report, direct links to the tested project pages, and links to the provider catalogues.
The 2026 result
The measured result is 2 of 8 concrete PikaPods app cards, 3 of 8 Elestio project-specific pages, and 3 of 8 projects with at least one tested provider path.
| Measure | Result | Projects or interpretation |
|---|---|---|
| PikaPods concrete app cards | 2/8 | Rallly, Fider |
| Elestio project-specific pages | 3/8 | Rallly, Fider, Easy!Appointments |
| At least one tested provider | 3/8 | Rallly, Fider, Easy!Appointments |
| OpenAlt catalog-managed flag | 4/8 | Cal.com, Cal.diy, Rallly, Fider |
| Neither tested provider | 5/8 | Cal.com, Cal.diy, QloApps, Agenda, Radicale |
In this eight-project snapshot, only three projects had a concrete managed-hosting path on at least one tested third-party provider, while OpenAlt marked four projects as catalog-managed.
PikaPods showed concrete app cards for Rallly and Fider. Elestio returned concrete project-specific pages for Rallly, Fider, and Easy!Appointments. The overlap means Rallly and Fider appeared on both tested provider surfaces.
Cal.com and Cal.diy were marked catalog-managed by OpenAlt, but neither had a concrete page on the two tested providers. That finding does not deny Cal.com’s official cloud. It shows only that the tested third-party catalogue paths did not produce a qualifying concrete page for those projects.
Easy!Appointments demonstrates the reverse case: OpenAlt marked it catalog-unmanaged, while Elestio returned a qualifying project-specific managed page.
How availability statuses were assigned
The statuses use narrow page-level evidence, so each one needs to be read literally.
What PikaPods available means
PikaPods available means the project name appeared as a concrete app card in the public PikaPods catalogue HTML fetched on 2026-09-23.
That status does not mean:
- The search query parameter worked.
- The project was found through a successful filtered search.
- A deployment was started.
- Checkout was completed.
- The provider guarantees capacity, uptime, support, or continued listing.
The qualifying evidence is the concrete app card in the public catalogue. A generic PikaPods homepage, a search URL without a verified result, or a project name mentioned elsewhere would not meet this definition.
What Elestio available means
Elestio available means the generated project-specific /open-source/<repo> page returned HTTP 200 with a project-specific Managed ... as a Service title on 2026-09-23.
A 404 is unavailable under this test. No checkout was attempted.
The qualifying evidence is therefore specific: the generated project route returned HTTP 200 and the page title identified the project as managed service. A provider homepage, a generic open-source landing page, or an unfiltered search result is not equivalent.
What Catalog managed means
Catalog managed is OpenAlt’s current project-level managed-hosting flag.
It may describe an official vendor cloud or another hosted path. It is not limited to PikaPods or Elestio, so it is not expected to match either third-party catalogue exactly.
That is why Cal.com and Cal.diy can be catalog-managed while lacking a qualifying page on the tested providers. The flag answers a broader OpenAlt catalogue question; the provider checks answer narrower page-verification questions.
What the counts mean
The counts show discoverability of concrete paths, not whether those paths are good choices.
A qualifying catalogue card or HTTP 200 project page is availability evidence. It does not prove:
- Reliability or uptime
- Security controls or hardening
- Backup policy or recovery time
- Support quality or response time
- Pricing, billing terms, or total cost
- Data residency or regulatory fit
- Feature completeness
- Upgrade and migration behavior
- A successful purchase or deployment
The 3/8 result means OpenAlt could verify at least one concrete path for three sampled projects at the time of the snapshot. It does not mean the other five projects cannot be self-hosted, hosted by the project team, or available through providers outside this test.
Likewise, the 4/8 catalog-managed result should not be read as a four-project recommendation list. It identifies projects for which OpenAlt currently records a managed path at the project level. The source and nature of that path can differ.
The snapshot is also time-bound. Provider catalogues change, project repositories change, URLs are added or removed, and managed-service listings can be renamed. The report records what the tested surfaces showed on 2026-09-23.
Why page type matters
A provider homepage is not a managed app page because it does not identify the project, expose a project-specific deployment path, or establish that the provider currently offers that project as a managed service.
An unfiltered search URL is not a one-click page because the query may be ignored, rewritten, incomplete, or dependent on a later interaction. A URL that merely contains a repository name is also insufficient without confirming the resulting page content.
OpenAlt uses concrete evidence to avoid overstating the conversion path:
- Identify the project in the provider’s public catalogue or project route.
- Confirm that the result is project-specific.
- Confirm that the page presents a managed-service path.
- Record the result as of the measurement date.
- Stop short of claiming that deployment or checkout succeeded.
This distinction matters for readers comparing operational options. “The provider has a homepage” is a much weaker statement than “the provider exposes a project-specific managed page.” The latter is still not a purchase recommendation, but it gives the reader a verifiable starting point.
How to verify a project
Readers should verify the page and the path before treating availability as actionable.
- Open the direct project link supplied in the page shell.
- Confirm that the project name and repository identity match the intended software.
- Check whether the page is a concrete app card or a project-specific managed-service page.
- Confirm the page status and title rather than relying on a search URL alone.
- Review current terms, regions, backups, support, security, and migration details directly with the provider.
- If deployment matters, proceed through the provider’s current setup or checkout flow and verify the final configuration.
For PikaPods, begin with the public PikaPods app catalogue and verify the concrete card. For Elestio, use the project-specific route pattern shown in the report links: https://elest.io/open-source/<repo>.
The test itself did not complete checkout. A reader who needs a production decision must perform that separate validation.
Choosing the next hosting path
Official cloud and verified third-party hosting are different choices. An official cloud may be operated by the project team and may offer product-specific integrations, while a third-party managed page may provide an independent deployment route with different terms and responsibilities.
For broader category discovery, visit the Scheduling & Booking category. For alternatives-oriented research, use Calendly alternatives. For the Cal.com-specific path, see /cal-com.
Use those pages to narrow the project choice, then use the audit evidence and direct provider links to verify whether the hosting path is concrete today. The right conclusion is not “available means recommended.” The useful conclusion is “this project has a page-level path worth checking further.”
Frequently Asked Questions
Does available mean I can buy hosting immediately?
No. It means OpenAlt found the qualifying public page evidence defined for that provider on 2026-09-23. Checkout was not attempted, so current purchase flow, pricing, capacity, and account requirements still need verification.
Why is Cal.com catalog-managed but absent from both tested providers?
OpenAlt’s Catalog managed flag can include an official vendor cloud or another hosted path. It is broader than the PikaPods and Elestio tests, so Cal.com can be catalog-managed without having a qualifying page on either tested provider.
Is Easy!Appointments confirmed as a reliable managed service?
No. Elestio returned a project-specific HTTP 200 page with a qualifying managed-service title. That proves page-level availability evidence only; it does not prove reliability, security, support, price, data residency, or successful deployment.
Where can I verify the underlying results?
Use the downloadable scheduling hosting-audit CSV and the direct project and provider links supplied in the page shell. Recheck the live provider pages before making a hosting or purchase decision.