Hosting Options

This page is a stub. It lists the ways OCL can be run today; each option still needs a full write-up.

OCL is open source under MPL-2.0. You can use the hosted service, have a deployment run for you, or run it entirely on your own infrastructure — and move between these as your needs change. The terminology content and the APIs are the same in every case.

OCL Online (hosted by OCL)

The hosted service at app.openconceptlab.org. Browsing, searching and publishing public terminology is free; paid plans add private repositories, the OCL Mapper and higher limits. Nothing to install — upgrades, backups and monitoring are handled for you.

Best for: most individuals and teams, and anyone who wants to start today.

Managed deployment (run for you by OCL)

A dedicated deployment operated by the OCL team — your own instance, sized to your workload, with uptime commitments, a formal SLA and named support contacts. Suited to national deployments and to organizations integrating OCL transactionally with their own systems (EMR, data warehouse, HIE).

Best for: production and mission-critical use where you want a dedicated instance without running it yourself.

Contact us at info@openconceptlab.org to discuss a managed deployment.

Self-hosting (run by you)

Run OCL on your own servers, in your own cloud account, or inside an air-gapped network. There is no license fee. You are responsible for deployment, upgrades, backups and monitoring.

See Self-hosting OCL for configuration notes.

Best for: organizations with data-residency or network constraints, and those with the operational capacity to run it.

Choosing between them

	OCL Online	Managed deployment	Self-hosted
Who operates it	OCL	OCL	You
Dedicated instance	No	Yes	Yes
Uptime guarantee / SLA	—	Yes	Your own
Runs inside your network	No	By arrangement	Yes
Cost	Free tier plus paid plans	Custom	Infrastructure only

To be expanded: requirements and sizing for each option, data residency, upgrade paths, migration between options, and support boundaries.