PainHuntr
Follow on
Developer tools

Where to find customers who are platform engineers

Platform engineers are easiest to sell when a golden path, a service catalog, or a self-service ticket is the villain — not when they are posting a Kubernetes homelab. They compare Backstage plugins, argue about IDP ROI, and ask which portal will not become a graveyard of stale catalog YAML. If you sell developer portals, golden paths, IDP scaffolding, internal CI abstractions, or anything that sits between an application team and the cloud account, find them in r/PlatformEngineering, CNCF Slack, Backstage Discord, PlatformCon talks, and G2 threads on Backstage, Port, and Humanitec. Ignore cluster-flex posts. Hunt comments that name a catalog nobody updates, a self-service flow that still opens a ticket, or a portal plugin that broke after a version bump. That is switching intent with a platform budget, not a DevOps engineer drowning in a pager this week.

Where platform engineers actually hang out

These are the rooms where platform engineers ask for recommendations, compare tools, and name the competitor they want to leave. Start here before you buy ads.

  • Redditgrowing, high signal
    r/PlatformEngineering

    This is the room that uses 'golden path' without irony. Threads titled 'Backstage catalog is stale within a sprint' or 'our IDP still opens a Jira ticket for a namespace' are buying notes. Commenters compare Port, Humanitec, Backstage, and homegrown portals with enough org shape — number of teams, regulated or not — that you can tell whether you fit. Search for named portals plus 'adoption,' 'ROI,' and 'still a ticket.'

    Rules gotcha: Kubernetes homework is noise. Disclose if you sell an IDP. Do not paste a landing page into a 'what is platform engineering' thread. Help with the adoption problem first.

  • Slackvery large, practitioner channels
    CNCF Slack #platform-engineering

    CNCF Slack is where platform teams debug Crossplane compositions, Argo app-of-apps, and Backstage plugin auth before they buy a vendor. Channels for platform engineering fill with 'we evaluated X and bounced because of Y' notes that never hit a G2 form. If your product sits next to Backstage, Crossplane, or Argo, this is where the comparison happens in real time. Search #platform-engineering and #wg-platforms, not just #general.

    Rules gotcha: Vendor spam in project channels gets you kicked. Help with the composition or the plugin first. Never scrape member lists. Practitioners first, always.

  • Discordlarge, portal-specific
    Backstage Discord

    Backstage Discord is where people hit the wall on software-catalog YAML, TechDocs, and plugin compatibility after an upgrade. Help channels turn into vendor comparisons when someone says they will not staff a full-time portal team. That is a warmer signal than a demo form. If you sell a Backstage alternative or a hosted portal, this is where the honest 'we cannot maintain the monolith' posts live.

    Rules gotcha: The Discord is for the OSS project. Pitching a competitor in #help without answering the error is a fast way to get muted. Disclose affiliation. Do not DM people who pasted a stack trace.

  • YouTubeevergreen comments
    PlatformCon and IDP talks

    PlatformCon talks age; comments do not. A platform engineer watches a session on scorecards or golden paths and then asks which portal the speaker actually ran after the keynote. Those commenters are often mid-RFI. Pair with 'we regretted Backstage' and 'IDP ROI' videos — the comments name replacement criteria like 'no dedicated portal squad' and 'works with our GitOps.'

    Rules gotcha: Conference channels delete obvious spam. Answer the question in the comment. Link only if someone asks for the product name.

  • Reviewsdecision-stage
    G2 reviews of Backstage, Port, and Humanitec

    When a platform engineer reviews Port, Humanitec, Backstage (or a hosted offering), or an IDP, they are usually mid-switch. Filter 2–3 stars and titles like platform engineer or developer experience. Cons paragraphs name catalog drift, plugin tax, GitOps that the portal ignored, and a self-service flow that still needed a ticket. Substitutes map the comparison you should monitor on Reddit and CNCF Slack.

    Rules gotcha: Do not astroturf. Vendor replies on G2 are fine when you are named. Do not email reviewers because they mentioned catalog YAML.

  • LinkedInslower, higher ACV
    Platform engineering operator posts

    Once a platform team is selling ROI to a CTO, they spend more time on LinkedIn than Reddit. Posts about golden-path adoption, 'we measured lead time,' or replacing a ticket-driven ops model collect comments from heads of platform who will forward a useful reply. A comment that names team count, GitOps, or a failed Backstage staffing plan can become an internal thread.

    Rules gotcha: Skip 'platform engineering is the future' carousels. Reply under posts that include a metric, a team count, or a named portal. Do not pitch in a hiring post.

  • Hacker Newsskeptical, high leverage
    Hacker News IDP and developer-portal threads

    Platform engineers still treat HN as the place to ask whether Backstage is a full-time product, whether to build the golden path, and which vendor just sold them a portal they cannot staff. The gold is the comment on a Backstage, Crossplane, or Internal Developer Platform thread where someone names catalog drift or a self-service lie. 'Ask HN: is anyone happy with their IDP?' is a buying committee.

    Rules gotcha: Anything that reads like marketing gets flagged. No tracking links. Answer the adoption or GitOps question in the comment itself.

How platform engineers talk about their problems

Search and replies land when you use their words, not your category name. These phrases show up in threads when they are close to buying or switching.

  • golden path nobody takes
  • Backstage catalog drift
  • self-service still a ticket
  • IDP ROI slide
  • plugin tax after upgrade
  • scorecards without coverage
  • InnerSource repo graveyard
  • platform as a product
  • Crossplane composition hell
  • no dedicated portal squad
  • paved road vs desire path

What platform engineers complain about — and what that means

PainHuntr classifies conversations by intent: actively asking, comparing, frustrated, discussing, or a passing mention. The quotes below are the shape of demand, not a promise that a specific post is live today.

  • Frustrated
    “Backstage catalog is stale within a sprint and we do not have a dedicated portal squad. I do not need another plugin marketplace. I need software entities that stay true without a full-time YAML gardener.”

    r/PlatformEngineering catalog threads, Backstage Discord help, and G2 cons on developer portals.

  • Comparing
    “Port vs Humanitec vs 'we keep Backstage and staff it.' 40 application teams, GitOps already, and a CTO who wants an ROI slide this quarter. What actually reduced tickets?”

    CNCF Slack platform channels, LinkedIn operator posts, and YouTube comments under PlatformCon talks.

  • Actively asking
    “Need self-service namespaces that do not open a Jira ticket and still pass the security questionnaire. Crossplane is fine if someone else owns the composition. What are you running for paved roads in 2026?”

    Ask HN IDP posts, r/PlatformEngineering self-service threads, and CNCF #wg-platforms.

  • Discussing
    “We published a golden path and teams still copy an old Helm chart. Every portal assumes adoption is a launch email. Nobody owns the desire path.”

    LinkedIn platform-as-product posts and slower Twitter/X threads after a PlatformCon keynote.

Search queries that surface platform engineers in buying mode

Paste these into Google, Reddit, or X search. They are the manual version of what PainHuntr runs when you paste a product URL.

  • site:reddit.com/r/PlatformEngineering (Backstage OR Port OR Humanitec OR IDP) (stale OR ticket OR ROI)
  • site:news.ycombinator.com (Backstage OR "developer portal" OR IDP) (staff OR stale OR alternative)
  • ("platform engineer" OR "developer portal") ("we moved off" OR "catalog" OR "still a ticket")
  • site:g2.com ("platform" OR Backstage OR Port) (cons) (catalog OR plugin OR adoption)
  • site:youtube.com PlatformCon (Backstage OR IDP OR golden path) (regretted OR ROI)
  • site:linkedin.com/posts (Backstage OR "platform engineering") (catalog OR adoption OR IDP)

How to reach platform engineers without getting ignored

Lead with the adoption constraint they already named — catalog drift, a self-service lie, no portal squad, GitOps the vendor ignored — and answer that before your product appears. Platform engineers reward people who have measured lead time, not a brand that says 'unlock developer productivity.' A team-count example, a GitOps note, or an ROI metric beats a deck of abstractions. Never ask them to book a demo from a Discord stack trace. Offer a public architecture, a plugin compatibility matrix, or a sandbox with 40 fake services. If you sell a portal, show staffing assumptions honestly. Follow up in the same thread. Do not scrape CNCF Slack into a sequence. The fastest way to get banned is pitching 'AI golden paths' into a thread about YAML drift.

Frequently asked questions

Are platform engineers the same buyer as DevOps engineers?

They share Kubernetes and still buy different jobs. DevOps and SRE own this week's pager and ingest bill. Platform engineers own golden paths, catalogs, and a multi-year IDP. Pitching Datadog cardinality into a Backstage staffing thread will miss. Pitching an IDP into a Friday deploy fire will miss. Keep the pages distinct.

Where do platform engineers complain about Backstage and IDPs?

r/PlatformEngineering, CNCF Slack, Backstage Discord, G2 cons, PlatformCon comments, and LinkedIn when ROI is political. HN when they are done pretending the catalog is fresh. Watch for catalog drift, plugin tax, and 'still a ticket' as buying criteria.

Is PlatformCon worth monitoring or just a vendor parade?

The hallway and the YouTube comments are worth more than the keynote. Practitioners ask speakers which portal they actually run. Those comments, plus LinkedIn recap threads the same week, are a dense cluster of comparison intent.

How do I tell a Kubernetes hobbyist from a buyer?

Look for a team count, a catalog, a ticket that self-service failed to kill, or an ROI slide. 'My homelab cluster' is not a buyer. '40 teams and the catalog is stale within a sprint' is a buyer. PainHuntr's asking, comparing, and frustrated labels exist for that cut.

What should I paste into PainHuntr if I sell to platform engineers?

Your product URL plus the incumbent they already staff — Backstage, Port, Humanitec, a homegrown portal. The engine looks for people asking for a replacement, comparing IDPs, and venting about catalogs and fake self-service. Pair that with the queries on this page if you still want to hunt by hand.

Related audiences

More in this sector

Reading 1,000 threads a month doesn't scale. PainHuntr does.

Paste your product URL. PainHuntr finds the conversations where platform engineers ask, compare, and complain on Reddit, X, Hacker News, YouTube, and review sites — then helps you reply, track what worked, and do it again.

Join the waitlist to get early access and help shape the product.