Support & Maintenance
pgloader is open source, but running it in production is a migration project with real risk: delays, incompatibilities, and unexpected edge cases. This support offering gives you priority access, predictable maintenance, and direct influence to keep your migration and production systems under control.
“A migration to PostgreSQL must be approached as a project, and some risks need to be handled properly.” “Chances are that the project will take more time than anticipated… it could even run over time and over budget.”
Support Plans
Pick the level of support your production requires.
| Plan | Best for | Outcome | Price |
|---|---|---|---|
| Evaluate | Testing, non-critical | Best-effort support via GitHub | €0 |
| Production | Live systems | Your issues are prioritized so migration and operations don’t stall | €100/mo |
| Business Critical | Delivery-sensitive workloads | Structured handling of fixes and releases aligned with your needs | €800/mo |
| Strategic | Core dependency | Direct input on roadmap + reserved development capacity | €2k/mo |
Why pay for support?
Migration is not just tooling. It involves:
- Data migration - moving terabytes with consistency
- Code migration - often the most expensive part
- Service migration - maintaining uptime during switchover
- Opportunity cost - delays impact delivery timelines
Without support:
- Blockers delay CI/CD and release cycles
- Compatibility issues accumulate
- Migration timelines slip
Proven in real migrations
“made our migration… really easy (~1Tb)” “almost too easy… I just ran the one-liner and waited for 48 hours” “greatly reduced the time required to accomplish this complex migration”
Built on Continuous Migration
pgloader uses incremental migration instead of big-bang risk. This approach enables:
- Repeatable migrations that reduce surprises
- CI/CD integration ensures ongoing validation
- Predictable timelines without hero-mode deployments
FAQ
Why pay for OSS support? Open source gives you freedom to use and modify the software. But production use requires maintenance and prioritization—something that comes from funded, accountable support.
What happens without support? You get best-effort support via GitHub—helpful, but with no guarantees on priority or timing. Your blockers wait in the public queue.
What do I actually get? It depends on the tier, but generally: prioritization in the issue queue, regular maintenance releases, PostgreSQL compatibility updates, and roadmap access (for higher tiers).
