Managed Pimcore Care – so it stays right.
We don't build it and leave. We keep your Pimcore current, secure, and fast: updates, monitoring, support, and ongoing development as a predictable service.
Pimcore is alive. Versions change, security issues surface, new requirements show up. Without continuous care, exactly the kind of technical debt builds up that later triggers an expensive rescue. With Managed Care, your system stays up to date long-term, looked after by a team that already knows it, not one that has to relearn it first.
Six Components
Update and security management
Monitoring & alerts
Performance care
Priority support
Ongoing development
Annual health check
How Technical Debt Builds Up When Nobody's Watching
A Pimcore system that was built cleanly once doesn't stay clean on its own. Three mechanisms make sure quality erodes without ongoing care:
Dependencies drift apart. Composer packages, PHP versions, and third-party bundles keep evolving independently of your system. Without regular updates, the gap between what you're running and what's currently supported widens every month, until a single update suddenly turns into a major project.
Security vulnerabilities go public before they get patched. Known vulnerabilities in Pimcore itself or in embedded libraries aren't a theoretical risk, they get actively scanned for. A system without ongoing security patching isn't a question of "if," but "when."
Performance problems build up quietly. Data volume grows, new attributes get added, reports get more complex. Without monitoring, nobody notices that response times have crept past the point users actually feel, until complaints start piling up.
Each of these three points is unremarkable on its own. Combined and left unattended for years, they add up to exactly the picture we regularly inherit in rescue projects.
Why Continuity Is Worth More Than a Ticket System
Classic support starts from zero every time: a new ticket, a new handler, relearning a system they don't know. Managed Care with us works differently, because the same senior contacts stay with the system over time, often the same people who built or rescued it. That doesn't just shorten response time on a specific problem. It stops knowledge about your system from getting lost in the first place when an employee leaves or a vendor changes.
Proactive Instead of Reactive: The Real Lever
The biggest difference between Managed Care and ad-hoc support isn't reacting to incidents. It's preventing them from happening at all. Monitoring that catches a performance regression before users feel it. An update cycle that keeps version jumps small instead of letting them pile up for years. An annual health check that surfaces technical debt while it's still cheap to fix. Every dollar spent on proactive care replaces a multiple in reactive emergency work. That's simply how technical debt works, not a marketing line: it grows until someone actively pays it down.
Frequently Asked Questions
What exactly is included in Managed Pimcore Care?
Six components: update and security management, monitoring, performance, priority support, ongoing development, and an annual health check.
What does Managed Pimcore Care cost?
Depends on the condition and scope of your system. The range comes out of the audit, not an off-the-shelf price list. Two systems of the same size can carry completely different care effort, depending on how much technical debt built up before we got involved.
Can I book Managed Care if you didn't build the system yourselves?
Yes. It requires an onboarding audit: We need to know a system someone else built as well as one we built ourselves before we take responsibility for it. After that, ongoing care runs exactly the same as for a system we built from scratch.
How fast do you respond to a critical incident?
Priority response, with a concrete response time set out in your Care contract's detailed SLA. We deliberately don't quote one flat number for every system. The response time that makes sense for a small catalog is too slow for a business-critical enterprise system, and the reverse means paying for SLA depth you don't actually need.
What happens if I cancel Managed Care?
A clean handover. You get the documentation and the knowledge we built up over time, so a switch doesn't start back at zero, neither for you nor for whoever takes over next.
What's the difference between Managed Care and classic IT support?
Classic support reacts to tickets, often with rotating handlers who relearn the system every time. Managed Care is proactive and continuous: the same senior contacts, ongoing monitoring instead of waiting for the next incident report, and an update rhythm that stops backlog from building up in the first place.
How often should a Pimcore system be updated to avoid building up backlog?
Security-relevant updates should be applied promptly after release, and larger version jumps should happen in regular, plannable cycles rather than right before support for your current version ends. That's exactly the core of the update and security management component.
Is Managed Care worth it if we already have our own internal IT department?
Yes, typically as a complement, not a replacement. Your internal IT knows the business processes, we bring Pimcore-specific depth. The combination is usually stronger than either side alone.
Who's taking care of your Pimcore tomorrow?
We discuss which care package fits your system size and risk.
Discuss Pimcore Operations