How you receive the software

Licensed versioned archives from Code 44 — not public Packagist.

Coaptive CMS (standalone). Clients receive a versioned install archive such as coaptive-cms-0.7.6.tar.gz (plus SHA256SUMS) and a separately signed license — not a public Packagist package. The archive includes Composer vendor/ with a mirrored code44/coaptive-cms package and built frontend assets. Verify the checksum, unpack, copy .env.example → .env, migrate, place the license, and follow the included deploy/INSTALL.md. Open-source Laravel dependencies may still resolve from Packagist on rebuild; Coaptive product code does not. Annual-license updates are new host archives from Code 44.

Coaptive GME. Delivered only as a custom institutional deploy (quote-driven) — not self-serve checkout. Institutions receive a versioned coaptive-gme-{version}.tar.gz (for example coaptive-gme-0.4.28.tar.gz embedding CMS 0.6.1) with mirrored private packages (coaptive-cms, coaptive-gme, licensed modules). GME is not on public Packagist and requires PostgreSQL for operations data.

Summary. Clients do not pull Coaptive product code from public Composer. They receive licensed Code 44 distributions; Composer is used inside the release build (and optionally for client rebuilds of OSS deps).

Next: Install · Developer notes · Pricing