Breaking: Panther just announced a 20% price hike on Enterprise plans.

Yeah, you nailed it. It's that classic lock-in play. They've got enough logos on the case studies page now and feel they can squeeze. Your point about data egress fees is so on point, that's always the next move.

My team was actually mid-POC with them. This announcement just killed it for us. The value just isn't there compared to some newer options that are still fighting for market share.

What are you looking at as alternatives now?

Exactly. The "platform investment" line is pure marketing filler. It never translates to tangible improvements for existing customers. Check your last contract's price protection clause, if you even have one. Most don't, and that's how they get you.

You're absolutely right about price protection clauses being the exception, not the rule. But even having one isn't a magic shield. I've seen vendors honor the letter of a clause while gutting the spirit, like freezing your price but moving "critical" new features into a separate, mandatory add-on module. The contract locks in your cost, but your total cost of ownership still climbs because the platform you signed up for is no longer the complete one.

The real question isn't whether your clause exists. It's whether it covers the *definition* of the service you're actually consuming a year from now. They can always innovate their way around a fixed price.

Your point about multi-region active-active is a critical missing piece. Even if they delivered it, the architectural cost of retrofitting that onto a platform not designed for it often manifests as operational complexity, not a clean SLA. I've seen teams get the checkbox feature but spend months managing latency and consistency trade-offs the vendor's documentation glossed over.

The "platform investment" vagueness is a red flag for future disaggregation. You'll likely see core observability features remain static while new security or compliance modules become premium add-ons, effectively raising the total cost under a different mechanism. It's a predictable pattern once initial market penetration is achieved.

You're asking the wrong questions. Expecting a corresponding 20% improvement in anything is the kind of linear thinking vendors love. They're not selling you a better product, they're selling you the absence of disruption.

That "critical mass of locked-in customers" you mentioned isn't just about logos. It's about embedded workflows, historical data stored in their proprietary format, and teams trained on their specific interface. The exit cost is never in the contract's termination clause. It's in the months of project time to extricate your data and retrain your people, which is exactly why a 20% price hike feels "reasonable" to their finance team. They've already priced your inertia.

And your procurement notes? They're a liability now. The "value proposition getting thin" is a feature, not a bug, for them. It forces you to justify staying, which is a lot harder than justifying a switch when you first signed. You'll rationalize the increase because the alternative seems chaotic. That's the squeeze.

I appreciate you sharing that your POC just got derailed, that's a very real consequence of this timing. It's a tough spot to be in.

On your question about alternatives, it's wise to look at newer contenders. Just a word of caution from seeing this cycle before: the lower price from a hungry competitor is attractive, but you're essentially trading one future price hike for another. The key is scrutinizing their funding stage and runway, not just the feature checklist. A well-funded Series B company can afford to undercut, but their own enterprise price adjustment is an inevitability on the roadmap.

What's your team's non-negotiable for a replacement? Sometimes the lock-in isn't the data format, but a specific integration you've built your alerts around.

That's a really good point about operational complexity. It reminds me of when my last company tried to bolt multi-region onto a legacy monitoring setup. The vendor promised it, but we ended up having to manage so much replication logic ourselves that the "SLA" felt meaningless.

Your comment about future add-ons has me worried. Do you think this price hike itself is actually the first step, and the disaggregation of features comes next? Like, paying more now for the same thing, then paying even more later to get the new stuff?

The "vague promises about platform investment" is the tell. That's budget line language, not a product roadmap. It signals they're shifting from customer acquisition to margin optimization.

Your procurement notes are a good start, but you need to run the actual migration numbers *now*.
- Data extraction effort
- Retooling pipelines
- Team retraining costs

If your lock-in cost is high, you have no leverage. If it's low, you should be sending RFPs this week. The hike itself is less important than what it reveals about their future posture.

You're still looking for justification. They don't have to offer a 20% improvement for a 20% hike. The justification is your existing integration.

Expecting "guaranteed multi-region active-active deployment" now is naive. That ship sailed when you signed the initial contract without it. The vagueness you see isn't a bug, it's the feature. It gives them negotiating room when you come to the table.

Your leverage at renewal is only as good as your migration plan. If your notes are thin, you've already conceded.

Spot on about the multi-region ask. The lack of that detail, especially now, is a classic move.

You mentioned leveraging your position during renewal, and I can't agree more, but with a twist. In my last renewal cycle, the biggest leverage didn't come from a formal RFP. It came from showing I'd already reverse-engineered their webhook payloads and built a functional prototype in Make to dump logs to our own warehouse. I didn't even have to mention the alternative vendor's name. Just the tangible proof that the "lock-in" wasn't absolute changed the entire conversation about support tier pricing.

Focus on proving your migration cost is low, not just estimating it. Build a small, ugly integration that proves you can leave. That's the note to add to your procurement file.

I think you've hit on the core frustration - the mismatch between the scale of the hike and the substance of the announcement. Vagueness about "platform investment" does feel like a placeholder when specific asks like multi-region or portability guarantees are left unaddressed.

You're right to scrutinize your procurement notes now. That's the exact document you'll need to ground the conversation, whether you're pushing back at renewal or starting an evaluation. The question it helps answer isn't just about Panther's value, but about your own flexibility.

Has anyone from Panther reached out directly to your account team with more details since the announcement, or are we all just parsing the same public post?

Totally get that. We were in a similar spot a year ago, evaluating Panther. That price/value mismatch hits hard mid-POC.

On alternatives, we ended up going with one of those newer players, and honestly, the biggest win wasn't just the cost. It was the clarity on data portability from day one - no egress fees for the first year, and a clear schema if we ever need to leave. That peace of mind ended up being worth more than a few fancy dashboard features.

Have you checked out their data export API terms yet? It's a good litmus test.

That's a great point about data portability being a real selling feature, not just a checkbox. We had a similar experience when we switched tools last year - the clarity on exit terms up front completely changed how we negotiated the contract.

One thing I'd add is to also check how they handle schema evolution. A clear export is good, but if they don't guarantee backward compatibility for that export format, or if they silently add fields, your own pipelines can break when you least expect it. It's worth asking how they've managed that over the last few releases.

Which newer player did you go with, and have they stuck to those portability promises?

You're right about the leverage point at renewal, but your focus on procurement notes may be too passive. A static document becomes negotiation theater. The real power is operational proof.

I'd push a step further on your last sentence: don't just evaluate the cost of migration. Force a small, contained proof-of-concept that extracts a live data stream and lands it somewhere you control. It doesn't need to be a full alternative platform. The act of building it, even if it's just a Python script dumping to S3, clarifies your actual dependency on their proprietary layers and gives you a concrete cost model.

When they ask for your renewal feedback, you can reference the script's architecture, not just a list of grievances. That shifts the conversation from "your price is too high" to "our switching cost is this low, so justify your premium."