Complete newbie here - is it okay to share pricing data?

Hey, welcome to the community! 😊

>Is it okay for a beginner like me to post anonymized pricing?

Absolutely, and it's really helpful for others. Just make sure you remove any specific company names, project IDs, or exact contact info from the quote. Sharing the general structure (like per-user costs, data retention tiers, and support levels) is super valuable.

If you're unsure, you can always paste the redacted version in a code block and ask for a quick check before posting the main thread. People here are pretty good about pointing out if you missed something.

Welcome user333, glad to have you here!

Sharing anonymized pricing is not just okay, it's one of the most useful things members can do. It helps everyone benchmark and avoid overpaying. The key is to remove anything that could identify the vendor or your company, like internal SKU numbers or unique discount names.

For your cloud monitoring quote, if you can share the metrics they charge for (per GB of logs, per host, per custom metric), the commitment term, and any included support, that would give folks exactly what they need to help you.

I strongly agree with the other replies about sharing anonymized data, it's fundamental for collective cost intelligence. However, I'd push you to go beyond just sharing the quote's face value.

When you post the redacted version, please also include your specific context. The unit costs are meaningless without the scale they apply to.

* What is your estimated daily or monthly volume for logs, metrics, and traces?
* What's your projected data retention period?
* Are you looking at a monthly commitment or an annual one?

A quote for $0.50 per GB of logs is terrible if you're ingesting 10 GB a day, but it's potentially catastrophic if your projection is 10 TB a day. The "reasonableness" of any number is entirely dependent on the underlying usage it's multiplied by.

Yes, do it. Sharing real numbers is the only way to cut through the vendor marketing fluff.

Just strip out any identifiable details. The "confidential" stamp on the quote is there to protect the vendor's margins, not you.

Totally okay, and a great way to start! Just to add one practical thing: try to find a comparable public price from a major vendor (like AWS CloudWatch or Datadog's published pricing page) to include. That gives everyone a baseline to compare your quote against. It makes the whole "is this reasonable?" conversation way faster.

Welcome to the jungle. The advice you've gotten so far is solid, but let me offer the cynical, practical reason why you should absolutely post that redacted quote.

Vendors thrive on information asymmetry. They'll hand you a 45-page PDF with a six-figure annual total at the bottom, hoping you'll just nod. Forcing the breakdown into the light is a public service. Just make sure your anonymization is thorough - think less "blacking out a name" and more "burning the original document and describing the ashes." Strip out any mention of the sales rep, any weird internal project code, and especially any "special limited-time discount" names. Those are often unique identifiers.

One thing others haven't mentioned: be ready for the feedback to sting a little. You might learn your "reasonable" quote is, in fact, highway robbery. Consider it a rite of passage.

That's a solid practical suggestion for providing a baseline, but it comes with a major assumption: that the quote is for a comparable service tier.

A vendor's public "starting at" price is almost always for their most basic, usage-capped, support-excluded tier. The quote in hand is likely for an enterprise tier with custom commitments and negotiated support. Comparing the two directly gives a false sense of markup.

A better baseline is to find the vendor's *public* price for the specific features and support level listed in the quote, which is often buried in a PDF deep on their site. If you can't find that, the comparison is mostly theater.

Finally someone points out the obvious. The "public pricing" mirage is a classic vendor tactic. I see this constantly with observability platforms.

They'll have a nice, simple webpage for startups showing $0.50 per million spans. Then you get your 200-page enterprise quote, and you realize you're now being billed per-seat for the UI, per-hour for data processing nodes, and have a completely different rate card for logs versus metrics. The public page is functionally a different product.

Finding the actual enterprise price sheet is the real challenge. They're usually behind a "contact sales" wall for a reason. Sometimes you can find an old RFP response or a publicly posted government contract that has the real matrix in an appendix. That's the only useful comparison.