Push your event contracts to external schema registries so CDPs and collectors enforce them at ingestion time — before bad events ever hit your warehouse. suky maintains a one-way (or optional two-way) sync between your event schema and each destination.
Supported destinations
| Destination | What gets published |
|---|---|
| Segment Protocols | Event names, property schemas, and validation rules. Supports pull-for-diff to detect out-of-band edits. |
| RudderStack Tracking Plans | Event contracts published as tracking plan entries for ingestion-time validation. |
| Snowplow Iglu | Self-describing event schemas published as SchemaVer-versioned entries in your Iglu registry. Import existing Iglu schemas as suky contracts. |
| mParticle Data Master | Event schemas pushed to mParticle Data Plans as validated data points with JSON Schema enforcement. |
Setup
- In Integrations, find the destination card and enter the platform's API key or registry credentials.
- Enable the destination.
- Go to Schema Publish to push events — publish all events or filter by vendor. A dry-run diff shows exactly what will change.
Publish status
Each event shows its publish status per destination: Synced, Pending, Failed, or Not Published. Publish logs with timestamps are available for auditing.
suky does not ingest any event data from these platforms. The connection is used only to push schemas to the registry.