Skip to content

PACKAGING.md

Latest commit

 

History

History
20 lines (13 loc) · 1.02 KB

PACKAGING.md

File metadata and controls

20 lines (13 loc) · 1.02 KB
Raw

Packaging & metrics

For productizing MetaShift, these metrics can support packaging and pricing without overbuilding.

Suggested units

  • Per environment / tenant: one deployment or X-Tenant-ID scope.
  • Per conflict resolved: count of conflicts that reached resolved in a period.
  • Per events/month: count of telemetry events (e.g. system_events rows or ingest calls) in a period.

Where to get them

  • Environments/tenants: distinct tenant_id in use (from API usage or DB).
  • Conflicts resolved: count rows in conflicts where status = 'resolved' and resolved_at in the period; or use pipeline status / resolution log.
  • Events: count of system_events rows per tenant (or sum of ingest requests) in the period.

Implementation notes

  • No code changes are required to start; you can derive these from existing Supabase tables and API logs.
  • Optional: add a lightweight usage or metrics table (tenant_id, period, event_count, resolution_count) and a job or trigger to aggregate for billing.