Transparent pricing. No pipeline tax.
Pay by active pipeline sources, not by data volume or events processed. The meter doesn't run while data flows — only while sources are connected.
For individual engineers evaluating schema-drift detection on their first sources.
- 5 active pipeline sources
- Schema drift detection (60-min poll)
- Email alerts on drift events
- 100k events/day
- 7-day schema history
- Community support (GitHub Discussions)
- No YAML drift rules
- No Slack / PagerDuty alerts
For data teams running production pipelines across multiple sources.
- 25 active pipeline sources
- Schema drift detection (5-min poll)
- YAML drift response rules
- Slack + PagerDuty alerts
- 5M events/day
- 90-day schema history
- Team workspace (up to 10 users)
- Email support (1 business day SLA)
For teams running 50+ sources who need 1-min polling, SSO, and unlimited history.
- Unlimited active sources
- Schema drift detection (1-min poll)
- Custom drift response rules
- Webhook + custom alerting integrations
- Unlimited events/day
- 1-year schema history + audit log
- Unlimited users
- SSO (Google Workspace, Okta)
- Priority support (4h response) + private Slack
Pricing FAQ
An active source is a connected source connector that Queryvine is polling for schema changes. One Postgres database monitored for schema drift = one source. One Kafka topic cluster = one source. Pausing a source removes it from your active count; deleting it removes it permanently. You can connect more sources than your tier limit and rotate which ones are active.
Yes. Upgrades take effect immediately and are prorated for the remaining days in your billing cycle. Downgrades take effect at the start of your next billing month — your current tier stays active until then.
The Scale plan ($449/mo) covers most teams running 50+ sources. If you need volume discounts, on-premises deployment, custom SLA terms, or dedicated support, email [email protected] — we handle enterprise agreements directly.
On Starter (100k events/day) and Team (5M events/day), pipelines that exceed the daily cap are paused until midnight UTC, then resume automatically. You'll receive an email alert at 80% of your daily cap. The Scale plan has no event limit. If you're regularly hitting the Team cap, the Schema history and alerting for those runs is still preserved — only new ingestion is held.