Installation & deployment readiness

Kaporeal's source repository is not public, licensing is under review and no production deployment has been verified. There is no clone command, downloadable package or supported Docker quickstart in this documentation. Self-hostable by design is a deployment intention, not present availability.

Before installation instructions are published, the project must identify supported prerequisites, configuration, database migrations, attachment storage and expected operational behavior. Commands should be tested against the released source, not invented to make a documentation page look complete.

A future release should specify its version and license, supported environment, reproducible setup and safe handling of configuration secrets. Operators need to know which storage contains core records, which contains attachments and how those stores remain consistent through backup and restore.

Upgrade guidance should explain migration order, compatibility and recovery expectations. A successful startup is not enough: a restore exercise and a complete load / event / document scenario should establish what the deployment actually supports.

• Public source and announced license terms.
• Verified prerequisites and reproducible configuration.
• Tested migration and upgrade procedure.
• Backup coverage for records, attachments and configuration.
• Documented restore validation and security responsibilities.

A future backup plan should cover relational records, attachment objects and the metadata connecting them. Operators should define recovery objectives appropriate to their operation, test a restore into an isolated environment and confirm that a load's stops, event history and documents still read back coherently. Recovery is not established merely because a database dump completed.

Monitoring should distinguish application availability from operational processing health. A working page can coexist with failed integration deliveries or inaccessible attachments. Proposed observability should make queue age, rejected mappings, storage failures and migration errors reviewable without inventing live metrics or logging credentials. No monitoring service or recovery guarantee is implemented by this documentation.

Enterprise & Hosted is the fifth, future roadmap phase. There is no launched cloud subscription, uptime guarantee or support SLA. Potential managed services require a sustainable operating model and tested responsibilities before availability can be promised.

Organizations interested in the design can bring deployment requirements to Kordspace, but should not treat that conversation as an available Kaporeal hosting package. The roadmap records direction without release dates or unsupported delivery estimates.