OllyGarden Tulip

Commercially supportedOTel Collector.

Run the OpenTelemetry Collector you already trust—with curated components, predictable releases, and OllyGarden support when things get weird.

Quarterly releases with LTS builds every 18 months—CVE backports and production-grade bug fixes.

Drop-in Replacement

Getting Started is Simple

Replace your existing OpenTelemetry Collector image with OllyGarden Tulip. Same configuration, same collectors—now with professional support.

deployment.yaml

 apiVersion: apps/v1
 kind: Deployment
 metadata:
   name: otel-collector
 spec:
   template:
     spec:
       containers:
       - name: otel-collector
-        image: otel/opentelemetry-collector-contrib:latest
+        image: cr.olly.garden/ollygarden/tulip/tulip:25.11.0
         ports:
         - containerPort: 4317
         - containerPort: 4318

That's it. One line change. Your existing collectors, processors, and exporters continue to work exactly as before.

Before switching: Check the component manifest to ensure all your required components are included in Tulip.

Ship telemetry pipelines you can depend on.

Tulip combines upstream discipline with commercial support so you can run the OpenTelemetry Collector with confidence, not guesswork.

Production-grade defaults

Vetted components tuned for real-world observability pipelines and documented extension points.

Predictable release cadence

Quarterly stable releases and LTS releases every 18 months. All CVE issues backported, plus critical functional and performance bug fixes.

Support-first partnership

OllyGarden engineers triage incidents, ship hotfixes, and advocate fixes upstream so your team stays focused on product work.

Support tiers that meet you where you deploy.

Pick the level of coverage that matches your operational tempo. Every plan starts with the Tulip manifest and grows with your environment.

Recommended

Standard Support

$499/month

Best for teams adopting the curated Tulip manifest with predictable releases. Billed annually at $5,988.

3 business days response
Two concurrent active tickets
Knowledge base and release advisories
Guided version transitions with migration checklists

Enterprise Support

Custom pricing

Tailored coverage for platform teams with stringent SLAs or long-term support needs.

One business day response
Named support engineer and onboarding plan
Higher ticket concurrency by agreement
Optional long-term support release tracks

Frequently Asked Questions

Common questions about Tulip support, releases, and how we work with teams running OpenTelemetry Collector at scale.

What's included in Tulip support?

Bug triage, regression analysis, security guidance, and version transition coaching for every component listed in the Tulip manifest. We keep the curated bundle healthy and documented so you can focus on your services.

Can we add our own components?

Yes. Tulip support covers the curated manifest end-to-end, and we'll flag best-effort considerations when you extend it. Custom modules stay your responsibility, but we share integration tips along the way. Need a component that's not in the manifest? Reach out—we're always open to discussing additions that benefit the community.

What hours do you cover?

Standard support runs on business hours with 3 business days response time. Enterprise support provides one business day response time with tailored coverage and escalation paths during onboarding to match your operational tempo.

What is your release cadence?

Tulip ships quarterly stable releases. Every 18 months, we designate a Long-Term Support (LTS) release with extended maintenance. The first release is planned for November 2025, and the first LTS will be in May 2026.

What gets backported to supported releases?

All CVE security issues are backported to supported releases. Performance regressions and critical functional bugs (like data loss or core collector failures) are evaluated and backported when confirmed. Non-critical bugs and feature enhancements are not backported—we encourage upgrading to the latest stable release for those.

How does Tulip relate to upstream OpenTelemetry?

Tulip is built directly on upstream OpenTelemetry Collector releases. We curate and package specific versions with vetted components, but the core is pure upstream code. When we find bugs, we contribute fixes back to the OpenTelemetry project so the entire community benefits.

Tulip Support

Ready for a collector you can lean on?

Share a few details about your deployment and the Tulip team will guide you through the fastest path to production-ready support. We respond according to the SLA for your chosen tier.

Map your existing collector topology against our curated manifest.
Plan version transitions with migration guidance and regression coverage.
Bring tricky incidents to engineers who live and breathe OpenTelemetry.