Table of Contents
- What this audit measures
- Headline findings
- How to interpret each status
- What the sample reveals
- Practical verification checklist
- Compare fit before hosting
- Frequently Asked Questions
What this audit measures
This audit measures whether eight prominent live projects in OpenAlt’s Notes & Knowledge Base category have a concrete third-party managed-hosting path through PikaPods or Elestio. It measures visible catalogue or project-page evidence, not whether hosting is reliable, secure, affordable, supported, geographically suitable, or ready for purchase.
The sample contains the eight most-starred live projects in OpenAlt’s production catalogue snapshot. The projects include adjacent document and knowledge tools because the sample follows the live category; it is not a hand-curated Notion-only shortlist. Stars rank the sample only. They do not measure hosting quality.
OpenAlt tested two provider signals on 2026-09-23:
- PikaPods concrete app cards: 4 of 8.
- Elestio project-specific pages: 6 of 8.
- At least one tested provider: 6 of 8.
- OpenAlt catalog managed flag: 3 of 8.
The measured projects were Stirling PDF, Memos, Joplin, Paperless-ngx, AppFlowy, AFFiNE, SiYuan, and Docusaurus. Stirling PDF and Stirling-PDF refer to the same project context, with the provider naming reflected where it appeared in the measured result.
Headline findings
Six of the eight sampled projects had evidence of at least one concrete third-party provider page, while two had neither tested provider. The result is useful as a discovery signal: most of this sample has a visible route to managed hosting, but the route is not universal and the evidence does not establish the quality of the service.
In OpenAlt’s eight-project sample, 6/8 projects had at least one concrete third-party managed-hosting page, 4/8 appeared as PikaPods app cards, and 6/8 had project-specific Elestio pages; the remaining 2/8 had neither tested provider.
The most important cases are the mismatches:
- SiYuan and Docusaurus had neither tested provider.
- AppFlowy and AFFiNE appeared on Elestio but not PikaPods.
- Stirling-PDF, Memos, and Paperless-ngx had concrete third-party provider pages even though their OpenAlt catalog managed flag was false.
- AppFlowy, AFFiNE, and Joplin had the OpenAlt catalog managed flag set to true.
These differences are not contradictions. They show that the signals answer different questions.
How to interpret each status
PikaPods available means OpenAlt found the project name as a concrete app card in the public PikaPods catalogue HTML fetched on 2026-09-23. It does not mean the search query parameter worked, and it does not mean checkout was completed.
That distinction matters because a generic catalogue page can be visible without proving that a filtered search, deployment flow, account setup, or payment step works for the project. The measured condition is catalogue presence, not successful provisioning.
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. OpenAlt did not attempt checkout.
This is stronger evidence of a project-specific managed-hosting route than a generic provider homepage, but it still stops before purchase and deployment. A page can exist while important commercial or operational questions remain unanswered.
Catalog managed is OpenAlt’s current project-level managed-hosting flag. It may describe an official vendor cloud or another hosted path, so it is not expected to match the PikaPods and Elestio catalogues exactly.
| Signal | Measured result | What it supports |
|---|---|---|
| PikaPods app card | 4/8 | The project name appeared in the public catalogue HTML |
| Elestio project page | 6/8 | A project-specific managed-service page returned HTTP 200 |
| Either tested provider | 6/8 | At least one measured third-party route was visible |
| OpenAlt catalog managed | 3/8 | OpenAlt currently labels the project as having a managed path |
None of these statuses proves reliability, security, support quality, price, data residency, service-level commitments, backup behavior, upgrade policy, or purchase readiness. They are availability indicators for a narrowly defined test date.
What the sample reveals
Elestio provided the broader measured footprint in this sample, with six project-specific pages versus four concrete PikaPods app cards. AppFlowy and AFFiNE demonstrate why checking one provider is insufficient: both appeared on Elestio but not PikaPods.
The reverse interpretation is also important. A project can have a concrete provider page without OpenAlt’s catalog flag being true. Stirling-PDF, Memos, and Paperless-ngx all had third-party provider evidence while their catalog managed flag was false. That flag should therefore be treated as OpenAlt’s current project-level classification, not as a complete inventory of every external hosting option.
Joplin is the only sampled project named in all three positive groups: it had a PikaPods card, an Elestio project page, and an OpenAlt catalog managed flag. That alignment makes it easier to discover a managed route, but it still does not turn the result into a hosting recommendation.
SiYuan and Docusaurus are the clearest caution cases. Neither had a measured PikaPods card nor a measured Elestio project-specific page. This does not prove that no managed hosting exists anywhere. It means only that these two tested provider paths produced no qualifying evidence in this report.
A generic provider homepage should not be called a one-click or managed app page. It may describe the provider, list capabilities, or link to a catalogue, but it does not identify a deployable project-specific route.
Likewise, an unfiltered search URL should not be called a one-click app page. Unless the project appears as a concrete card or the destination resolves to a qualifying project-specific page, the URL does not prove that the provider recognized the project or can deploy it.
Practical verification checklist
Use this checklist before treating an availability result as a real hosting option:
-
Confirm the project identity. Check that the provider page names the intended repository or application, especially where names differ, such as Stirling PDF and Stirling-PDF.
-
Confirm the page type. Prefer a concrete app card or a project-specific managed-service page. Treat a provider homepage, category page, or generic search result as discovery material only.
-
Confirm the date. Availability can change. This report records evidence from 2026-09-23, not a permanent guarantee.
-
Confirm the deployment path. Determine whether the page leads to an actual application setup flow, or merely describes a possible service.
-
Check operational details separately. Review pricing, regions, storage, backups, upgrades, authentication, support, exit options, and data-residency terms directly with the provider.
-
Test the important workflow. If the project matters to your team, verify installation, import, export, upgrades, and recovery before committing production data.
-
Download the evidence. The page shell provides a downloadable CSV source and direct links to the tested project pages and provider catalogues.
The checklist preserves the report’s central boundary: a qualifying page is a lead worth verifying, not a purchase recommendation.
Compare fit before hosting
Hosting availability is only useful after the project fits the job. Readers comparing tools can start with OpenAlt’s Notes & Knowledge Base category, then review the Notion alternatives comparison path.
For project-specific evaluation, see the AppFlowy and SiYuan pages. These routes help separate product fit from hosting availability, which is particularly important when a project has no qualifying page from the two tested providers.
OpenAlt’s conclusion is deliberately narrow: six of eight sampled projects showed a concrete third-party managed-hosting path in the measured provider checks, while two did not. Use that result to prioritize verification, not to infer service quality or make a deployment decision without further checks.
Frequently Asked Questions
Does available mean I can buy hosting immediately?
No. available means OpenAlt found the defined catalogue or project-page evidence on 2026-09-23. No checkout was completed, and the status does not prove that deployment, payment, or account setup will succeed.
Why can the provider result differ from OpenAlt’s managed flag?
The signals cover different scopes. OpenAlt’s Catalog managed flag is a current project-level classification that may include an official vendor cloud or another hosted path, while PikaPods and Elestio measure specific third-party catalogue evidence.
Are SiYuan and Docusaurus impossible to host?
No. The report shows only that neither had a qualifying PikaPods card nor a qualifying Elestio project-specific page in this test. Other providers, self-hosting methods, or future catalogue changes may produce different results.
Where can I verify the underlying project results?
Use the downloadable CSV and the direct tested-page links supplied in the page shell. The provider sources are the PikaPods apps catalogue and the project-specific Elestio pattern https://elest.io/open-source/<repo>.