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.

Backend-neutral commercial support

Send data to any backend: Datadog, New Relic, Splunk, or your own infrastructure. Unlike backend-tied distributions, you get support regardless of where your telemetry goes.

Guaranteed bug fixes with patch releases

Hit a bug? We fix it in upstream OpenTelemetry Collector and ship you a patch release—same version, just the fix, no breaking changes. No waiting for upstream or forced upgrades to get critical fixes.

Predictable releases, including CVE backports for supported versions.

Tulip provides predictable quarterly stable releases and an LTS every 18 months, with all CVEs backported to supported versions and critical functional and performance fixes included. OllyGarden engineers take ownership of triage and fixes, while you stay in control of when to upgrade.

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.

1 business hour response for critical issues
Support portal and email access
Up to 2 concurrent open cases
3 designated contacts
Bug fixes and security patches for supported versions
Knowledge base and release advisories
Guided version transitions with migration checklists

Enterprise Support

Tailored coverage for platform teams with stringent SLAs or mission-critical deployments.

1-hour response for critical issues (24×7)
Dedicated Slack Connect channel
Phone support for critical issues
Named support engineer
10 designated contacts
Unlimited concurrent open cases
Quarterly business reviews
Priority access to new features and beta programs

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?

Commercial support for all components listed in the Tulip manifest. When issues arise in supported components, we deliver fixes through patch releases, without requiring disruptive upgrades or relying on new upstream releases. We also backport CVE fixes, provide security guidance, and assist with version transitions to keep telemetry pipelines stable in production.

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 operates during business hours (09:00–18:00 CET, Monday–Friday) with response times starting at 1 business hour for critical issues. Enterprise support provides 24×7 coverage for Severity 1 and 2 issues, with business-hours coverage for lower severities. Enterprise customers also get a dedicated Slack Connect channel and phone support for critical incidents.

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?

CVEs rated Critical, High, or Medium (CVSS 7.0+) are backported to all supported releases. Severity 1 and selected Severity 2 bugs affecting production stability are evaluated and backported when confirmed. Critical upstream OpenTelemetry Collector fixes that affect Tulip users are also backported. 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.

How is Tulip different from other OTel Collector distributions?

Tulip provides vendor-neutral commercial support for OpenTelemetry Collector pipelines. You can send data to any backend—Honeycomb, Grafana Cloud, AWS, Splunk, or your own infrastructure—and still receive full Tulip support. Tulip is designed to remain flexible even as you customize your deployment. You can derive your own images from the Tulip manifest, and Tulip continues to support all components included in that manifest.

What types of bugs do you fix?

Tulip fixes bugs in supported components that impact production stability, correctness, or security. This includes issues such as data loss, core Collector failures, memory leaks, crashes, and security vulnerabilities (CVEs). When a bug is reported, we triage it to confirm whether it affects a supported component. If confirmed, we take ownership of the issue and deliver a fix through a patch release.

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.