Skip to main content
The data marketplace is where teams publish curated datasets, semantic models, and pipeline bundles so other groups can install consistent copies without re-implementing joins and business rules.

​
Enterprise feature

Marketplace capabilities—governed publishing workflows, semantic versioning, and org-wide discovery—are included on Enterprise plans. Other tiers may offer read-only consumption or no marketplace at all. Your account executive or admin confirms availability.

​
Publishing packages

A package bundles metadata and artifacts your admin allows: for example dbt-style models, Planasonix pipeline templates, catalog entries, or documentation manifests.
1

Prepare the artifact

Validate the pipeline or model set in a staging project; capture tests and owner contacts.
2

Create a package manifest

Define name, summary, tags, semantic version, and compatibility constraints (minimum platform version, required connectors).
3

Submit for review

Route through stewardship or platform approval if your org requires it.
4

Publish

After approval, publish to a channel (for example production, experimental) consumers can subscribe to.
Treat packages like internal open source: include changelog notes and breaking change flags when bumping major versions.

​
Installing packages

Consumers browse the marketplace, inspect README and lineage hints, then install into a target project.
  • Pin a version for reproducible builds; floating latest suits sandboxes only.
  • Upgrades may run migration helpers when the publisher supplies them.
  • Conflicts appear when local resources share names; resolve by renaming or namespacing.
Install baseline finance or product analytics packages to align metrics definitions on day one.

​
Versioning

Packages use semantic versioning (MAJOR.MINOR.PATCH):
  • Major: Breaking schema or API changes for downstream consumers
  • Minor: Backward-compatible additions
  • Patch: Fixes that do not alter contracts
Pair marketplace versions with data contracts so automated checks fail CI when a publisher violates column guarantees.

​
Marketplace governance

Admins configure:
  • Who can publish (roles, teams, or approval queues)
  • Which channels appear in production catalogs
  • License or data classification labels required before listing
  • Deprecation rules and minimum support windows
Publishing wide PII packages without classification tags creates compliance debt. Enforce tags at publish time, not only in the warehouse.

Data catalog

Search and document assets consumers discover.

Data contracts

Enforce expectations on published datasets.