Skip to Content
// Apache Hop Support

Community support,
and what comes next

Apache Hop is open source software maintained by a small, dedicated team. Community support exists and is genuinely helpful — but it has real limits. This page explains what those limits are, and what options are available when you need more.

// Community support

What community support looks like

The Apache Hop project is maintained by a small team of volunteers and contributors. Community support is best-effort — there are no SLAs, no guaranteed response times, and no commitment to fix specific bugs or implement specific features on any timeline.

This isn't a limitation unique to Apache Hop — it's how open source works. The community is generous with knowledge and time, but developer bandwidth is finite and unpredictable. If your project depends on a specific fix or feature shipping by a specific date, community support is the wrong place to rely on.

// When you need more

Paid support and services through Putki

Putki is know.bi's enterprise distribution of Apache Hop. It includes support, additional tooling, and access to the team that built and maintains much of the Apache Hop codebase. If you need a guaranteed response, an urgent fix, or a feature that isn't on the community roadmap, Putki is where that happens.

// Putki Subscription
Support desk + knowledge base
A Putki subscription gives your team access to a support desk with defined response times, a knowledge base, and the full Putki plugin ecosystem on top of Apache Hop.
Ticketed support with SLA
Access to the Putki knowledge base
Regular CVE patching and security updates
Odoo, Flyway, and additional plugins included
// Coaching packages
Hands-on guidance for your team
Coaching packages give your team direct access to Hop expertise — for architecture reviews, pipeline design, performance issues, or getting unstuck on something specific. Flexible, time-boxed, and focused on your actual project.
Architecture and design reviews
Pipeline performance and debugging
Best practices for production deployments
Available as one-off sessions or packages
// Development packages
Bug fixes and custom feature development
If you need a specific bug fixed or a feature built — and can't wait for the community roadmap — development packages let you commission that work directly. We're the team that contributes to Apache Hop upstream, so fixes often benefit the broader community too.
Urgent bug fixes with defined timelines
Custom transform and plugin development
Fixes contributed upstream where possible
Scoped and priced before work begins

Not sure which option fits?

Tell us what you're working on and what's blocking you. We'll point you to the right option — or tell you honestly if the community can handle it.