Data Models

A truthful overview of the major records behind listings, releases, settings, support, and engine builds.

The data model behind Curator Marketplace is intentionally simple: listings, releases, settings, support tickets, and engine distribution records each have their own responsibility.

Listings

Listings describe a marketplace item such as a plugin or theme. A listing stores the public metadata users browse:

• name and slug
• summary and description
• category and tags
• pricing and billing type
• compatibility range
• docs and support links

Releases

Releases attach versioned artifacts and review state to a listing. This is the layer that turns a listing into something downloadable and reviewable over time.

Settings

The settings table is used for marketplace-wide switches and configuration values. That includes flags such as whether bundles are enabled and values used by SEO and operational tooling.

Support tickets

Support tickets act as the fallback inbox for the support form. If SMTP is not configured or email delivery fails, the stored ticket still preserves the message for follow-up.

Engine build distribution

Curator Engine distribution adds two important concepts:

• uploaded engine builds
• channel pointers that decide which build is current

That lets the public download routes resolve the current stable, beta, or nightly artifact without exposing raw storage paths directly.

Why this matters

Understanding which table owns which responsibility makes future admin and reporting work easier. If you are looking for a release problem, start with release records. If you are looking for a public download issue, inspect the engine build and channel state first.