How Maestrino works

A safer way to distribute commercial Composer packages.

1. Step 1 — Vendor

   Connect a private GitHub repository

   Install our GitHub App, pick the repositories you want to publish, and we ingest tagged releases.

2. Step 2 — Vendor

   Publish package versions

   We build dist artifacts, validate composer.json, and surface readiness checks before publishing.

3. Step 3 — Buyer

   Purchase access

   One-time or subscription. We grant entitlements that the registry enforces on every install.

4. Step 4 — Buyer

   composer require

   Configure the registry, create an install token, and pull the package like any other dependency.