Write the Hosting Options page in OCL Docs

[paynejd]

docs/source/ocl/hosting-options.md was added as a stub so that the /pricing page on the community site can link to it without a dead link ("OCL's tools are open too, so you can start at OCL Online and move to a managed deployment or your own servers when you're ready").

Live at: https://docs.openconceptlab.org/en/latest/ocl/hosting-options.html

The stub covers three options at one paragraph each — OCL Online, managed deployment run by OCL, self-hosting — plus a comparison table. It needs a real write-up before the pricing page goes live, since that page is what sends people here.

To add:

• Requirements and sizing for each option (self-hosted and managed).
• Data residency and air-gapped deployment.
• How to move between options, and what migrates.
• Support boundaries — what OCL is responsible for in each case.
• Upgrade paths and release cadence for self-hosted.

Related: the existing Self-hosting OCL page is 38 lines of scattered configuration notes (TermBrowser logo, SMTP, cloud storage, OpenSearch) rather than a how-to. It should either become a proper self-hosting guide or be folded into this page.

Depends on the managed-deployment offer being defined — see OpenConceptLab/ocl_online#126.

[ocl-automation]

Automated Triage — 2026-09-23

Dimension	Score
Complexity	3
Scope	2
Clarity	4
Dependency	4
Risk	2

Decision: decision/blocked
Type: type/docs
Signals: signal/low-risk, signal/small-scope, signal/well-specified, signal/has-dependencies

Writing a real hosting-options page requires gathering sizing, residency, migration, and support details across two docs pages, but the requirements list is clear and well-specified; it explicitly depends on the managed-deployment offer being defined in ocl_online#126, which keeps dependency high. Risk is modest since it's documentation, but inaccurate content could mislead customers via the linked pricing page.

---

Generated by ticket-triage pipeline v3. Model: anthropic/claude-sonnet-5 (openrouter).