Skip to main content
RedditTech adoption

Reddit adopted SPIFFE and SPIRE to migrate to mutual TLS and automated workload identity credentials, converting 90% of in-cluster Go gRPC traffic.

Source: Autobound Signal API · 53 signals tracked for Reddit · updated

Get Reddit's live signals in Claude or ChatGPT, or by API

AskWhat changed at Reddit this week? Use Autobound signals for reddit.com.

What happened

Post: "Beyond Static Credentials: Reddit’s Journey to Workload Identity and mTLS"

Source

RedditNov 9, 2026By u/wind_lectric

r/platform_engineering

Beyond Static Credentials: Reddit’s Journey to Workload Identity and mTLS

upvotes
0
comments
0

Post

Highlighted: the lines this signal was extracted from

Written by Pratik Lotia How we introduced automatically rotated workload credentials and migrated an existing service fleet to mutual TLS without a coordinated cutover. One Service, Several Sets Of Credentials Imagine building a new internal service. It calls another service, requires user context, reads from a database, requires access to a cloud resource and publishes events. Each dependency may have a different answer to the same question: how does the caller prove who it is and how do you manage access control? With static credentials, the answer usually involves provisioning a secret, deciding where to store it, granting access to the consumers of the secret, setting up authorization rules and wiring it into the application. Repeat that for every dependency and for every Kubernetes cluster or cloud environment it deploys to. The service is eventually ready to run, but its credentials still need coordination across multiple teams making it a high friction and time consuming process. When a security control is cumbersome enough, your customers will often find a way to bypass it or adopt less practices which leads to other issues such leaking credentials in code, sharing tokens and lack of regular rotation. We had accumulated versions of this problem across our infrastructure. Service authentication used static tokens. Database integrations had their own credential...

Keep reading with a free account

The rest of this post, and every signal for Reddit, is in your free account.

Also quoted as evidence

  • We chose SPIFFE as the identity standard and SPIRE as its implementation.

    From the post

  • getting 90% of our in-cluster Go grpc traffic to use authenticated calls in the form of mutual TLS.

    From the post

Extracted by Autobound

From the Signal API record
Signal
Tech adoption

What this signalsUser posts often show product pain before it reaches reviews or churn.

Subreddit
r/platform_engineering
Stage
Switched
Event date
Nov 2026

Companies

  • SPIREAlso named
  • SPIFFEAlso named

The full record

From the Signal API record

People

  • Pratik Lotiamentioned · Named in the post

Numbers

Mentions
4

Details

Timing
Completed
Category
workload identity and security
Link URL
/r/RedditEng/comments/1xs39qk/beyond_static_credentials_reddits_journey_to/
Virality
Very low
Post kind
Crosspost
Prominence
Core
Company's role
Buyer

Topics and mentions

Topics

  • security
  • workload identity
  • mtls
  • grpc

Products named

  • SPIFFE
  • SPIRE
  • gRPC

Extraction

Sentiment
Positive
Detected
Nov 9, 2026
signal_type
reddit-company
signal_subtype
techAdoption

Use this data

Get every Reddit signal for Reddit and the companies you sell to, in the tools you already use.

  1. Ask Claude about it

    Connect Autobound to Claude, Claude Code or Cursor with MCP. Then ask: “What changed at Reddit this week?”

  2. Send it to your own tools

    The Signal API returns Reddit signals for any list of companies as JSON, for your CRM, warehouse or app.

  3. Try it free

    Sign up and spend your free credits on the companies you sell to.

    Start Free1,000 free credits

The API returns more than this page shows

This page shows a preview. The full reddit-company record in the Signal API and MCP can also have these 8 fields. Some fields are empty for some signals.

Company

  • linkedin_urlValue in the API
  • industriesValue in the API
  • employee_count_lowValue in the API
  • employee_count_highValue in the API
  • revenueValue in the API
  • descriptionValue in the API

Signal

  • signal_nameValue in the API
  • associationValue in the API
Show the full JSONThe record on this page and the API request

GET /v1/signals/886e722c-e6c7-5890-a6c3-7f8dc03fdb87 returns this record as JSON. POST /v1/companies/enrich returns every signal for reddit.com.

{
  "signal_id": "886e722c-e6c7-5890-a6c3-7f8dc03fdb87",
  "signal_type": "reddit-company",
  "signal_subtype": "techAdoption",
  "detected_at": "2026-11-09T23:21:23+00:00",
  "company": {
    "name": "Reddit",
    "domain": "reddit.com"
  },
  "data": {
    "nsfw": false,
    "stage": "switched",
    "awards": 0,
    "people": [
      {
        "name": "Pratik Lotia",
        "role": "mentioned",
        "employer": "Reddit"
      }
    ],
    "timing": "completed",
    "topics": [
      "security",
      "workload identity",
      "mtls",
      "grpc"
    ],
    "post_id": "1xs766w",
    "summary": "Reddit adopted SPIFFE and SPIRE to migrate to mutual TLS and automated workload identity credentials, converting 90% of in-cluster Go gRPC traffic.",
    "category": "workload identity and security",
    "evidence": [
      "[post] Written by Pratik Lotia\n\nHow we introduced automatically rotated workload credentials and migrated an existing service fleet to mutual TLS without a coordinated cutover.",
      "[post] We chose SPIFFE as the identity standard and SPIRE as its implementation.",
      "[post] getting 90% of our in-cluster Go grpc traffic to use authenticated calls in the form of mutual TLS."
    ],
    "link_url": "/r/RedditEng/comments/1xs39qk/beyond_static_credentials_reddits_journey_to/",
    "virality": "very_low",
    "post_date": "2026-11-09T23:21:23.000Z",
    "post_kind": "crosspost",
    "post_text": "Written by Pratik Lotia\n\nHow we introduced automatically rotated workload credentials and migrated an existing service fleet to mutual TLS without a coordinated cutover.\nOne Service, Several Sets Of Credentials\nImagine building a new internal service. It calls another service, requires user context, reads from a database, requires access to a cloud resource and publishes events. Each dependency may have a different answer to the same question: how does the caller prove who it is and how do you manage access control?\n\nWith static credentials, the answer usually involves provisioning a secret, deciding where to store it, granting access to the consumers of the secret, setting up authorization rules and wiring it into the application. Repeat that for every dependency and for every Kubernetes cluster or cloud environment it deploys to. The service is eventually ready to run, but its credentials still need coordination across multiple teams making it a high friction and time consuming process. When a security control is cumbersome enough, your customers will often find a way to bypass it or adopt less practices which leads to other issues such leaking credentials in code, sharing tokens and lack of regular rotation.\n\nWe had accumulated versions of this problem across our infrastructure. Service authentication used static tokens. Database integrations had their own credential...",
    "sentiment": "positive",
    "subreddit": "platform_engineering",
    "event_date": "2026-11",
    "post_title": "Beyond Static Credentials: Reddit’s Journey to Workload Identity and mTLS",
    "prominence": "core",
    "source_url": "https://www.reddit.com/r/platform_engineering/comments/1xs766w/beyond_static_credentials_reddits_journey_to/",
    "entity_role": "buyer",
    "post_author": "wind_lectric",
    "upvote_ratio": 0.5,
    "mention_count": 4,
    "mention_surge": true,
    "subreddit_url": "https://www.reddit.com/r/platform_engineering/",
    "total_upvotes": 0,
    "comments_total": 0,
    "total_comments": 0,
    "other_companies": [
      {
        "name": "SPIRE",
        "role": "adopted"
      },
      {
        "name": "SPIFFE",
        "role": "adopted",
        "domain": "spiffe.io"
      }
    ],
    "post_author_url": "https://www.reddit.com/user/wind_lectric/",
    "signal_category": "adoption",
    "comments_included": 0,
    "products_mentioned": [
      "SPIFFE",
      "SPIRE",
      "gRPC"
    ]
  }
}

Long text fields are shortened on this page.

Looking up one signal by its id is free. Enrich costs 2 credits per signal returned; a call with no results is free.