Access, plans and scope

Request-led access#

Care CMS is currently private development software. Request access through the ZoraWebDesign CMS page. Project suitability, installation, hosting and support are agreed personally by email; the public documentation does not provide a download or shared administrator credentials.

Proposed service plans#

• Individual: one website/installation licence with agreed monthly maintenance.
• Agency: up to ten website/installation licences, each practice with its own installation and accounts.
• Plus: optional hosting support added to the agreed service, with compatible self-hosting still possible.

The limit concerns installations, not repeated update downloads. Pricing, release rights, support scope, response times, backup responsibilities and cancellation terms must be agreed before purchase. Billing and entitlement enforcement are not implemented.

Ownership and existing releases#

Making the development repository private does not revoke rights already granted for earlier MIT releases. Dependencies and fonts keep their respective notices. Future service agreements and code-licence terms require their own review. Client content, provider credentials, authentication and future billing must remain separate concerns. A subscription problem must not silently erase content or disable the public website.

Remaining product work#

Fine-grained designer/client permissions, a canonical reusable content model, a form builder, reviewed release distribution, stronger production abuse controls and complete real-provider acceptance tests remain development work. WordPress migration is out of scope for this phase. Do not describe the current prototype as a certified patient-management platform, an unrestricted plugin ecosystem or a ready-made enterprise multi-tenant SaaS.