dendrobundle vs RelativeCI

RelativeCI is a mature, job-metered SaaS that provides deep per-build bundle analysis with strong GitHub and Slack integrations, and it added treemap visualisation in 2024. Its free tier caps at 100 jobs per month, after which plans start at $29/month and scale with build volume. dendrobundle charges a flat $20/month for unlimited snapshots on the Developer tier — no per-job metering — which makes costs predictable for teams that run CI frequently.

dendrobundle vs RelativeCI, feature by feature

feature dendrobundle RelativeCI
Per-commit history and trend charts Yes Yes
Interactive treemap visualisation Yes Yes (added April 2024)
PR comment / GitHub status check No (in development) Yes — PR comments, Check + Commit Status reports
Build-fail budgets Yes Yes (rule-based checks)
Email regression alerts Yes (Developer tier) No — GitHub and Slack only
Weekly/monthly digest emails Yes (Developer tier) No
README SVG size badge Yes No
Slack notifications No Yes
InfluxDB metrics forwarding No Yes
Pricing model Flat ($0 Community / $20/mo Developer) Job-metered ($0 to 100 jobs/mo; $29+/mo above)
Accepts existing stats files without a plugin Yes No — requires the RelativeCI agent plugin

Competitor details are researched but change over time — verify against RelativeCI’s current docs.

RelativeCI vs dendrobundle — FAQ

Should I use RelativeCI or dendrobundle?
RelativeCI is the stronger choice if your team already uses Slack for CI notifications, needs GitHub Check reports rather than email alerts, or is running a high-profile open-source project (its OSS tier is always free). dendrobundle suits teams that want email-based regression alerts and digests, a predictable flat monthly cost regardless of build frequency, and a simpler push path that works with stats files your bundler already emits.
Can I migrate from RelativeCI to dendrobundle?
Partly. dendrobundle reads the same webpack stats and rollup-plugin-visualizer output that RelativeCI agents consume; you replace the agent with a curl command or the GitHub Action. Historical RelativeCI data cannot be imported, so if your team relies on long-term trend comparisons, factor in starting fresh.
When is RelativeCI the better choice?
RelativeCI is the better choice when your primary notification channel is Slack, when you want to forward metrics to an InfluxDB/Grafana stack, when you need a GitHub App with native Check report formatting, or when you are on an open-source project that qualifies for its always-free tier.

Try dendrobundle free — the Community plan is $0 forever, no credit card, no build-count limits.

create a free account