CRED re-architected its machine learning model serving from a Python monolith to a two-layer engine for request orchestration and model execution, enabling it to handle 9 million predictions per day.

{
  "signal_id": "d3a7667f-5871-5bbd-a5e6-81bfbf8ed03e",
  "signal_type": "reddit-company",
  "signal_subtype": "techAdoption",
  "detected_at": "2026-09-21T09:48:52+00:00",
  "company": {
    "name": "CRED",
    "domain": "cred.club"
  },
  "data": {
    "nsfw": false,
    "stage": "switched",
    "awards": 0,
    "timing": "completed",
    "topics": [
      "mlops",
      "software architecture",
      "scalability",
      "machine learning",
      "python"
    ],
    "post_id": "1wm89g5",
    "summary": "CRED re-architected its machine learning model serving from a Python monolith to a two-layer engine for request orchestration and model execution, enabling it to handle 9 million predictions per day.",
    "category": "ML model inference architecture",
    "comments": [
      {
        "url": "https://www.reddit.com/r/softwarearchitecture/comments/1wm89g5/comment/pbis2d0/",
        "depth": 0,
        "score": 1,
        "author": "Ok_Statistician_997",
        "excerpt": "Splitting execution from orchestration usually pays off once you have more than one model version live at a time. The orchestration layer becomes the place that owns retries, timeouts, batching and routing to the right model version, while the execution layer stays dumb and swappable.\n\n Two things tend to bite teams doing this: keeping the contract between the layers stable when a model needs extr",
        "posted_at": "2026-09-23T07:14:17.000Z",
        "author_url": "https://www.reddit.com/user/Ok_Statistician_997/"
      }
    ],
    "evidence": [
      "[post] Separating model execution from request orchestration: how CRED went from Python monolith serving to a two-layer engine doing 9M predictions per day"
    ],
    "link_url": "https://engineering.cred.club/scaling-ml-model-inference-through-architectural-separation-32b2629f554a",
    "virality": "low",
    "post_date": "2026-09-21T09:48:52.000Z",
    "post_kind": "link",
    "sentiment": "neutral",
    "subreddit": "softwarearchitecture",
    "event_date": "2026-09",
    "post_flair": [
      "Article/Video"
    ],
    "post_title": "Separating model execution from request orchestration: how CRED went from Python monolith serving to a two-layer engine doing 9M predictions per day",
    "prominence": "core",
    "source_url": "https://www.reddit.com/r/softwarearchitecture/comments/1wm89g5/separating_model_execution_from_request/",
    "entity_role": "buyer",
    "post_author": "nilukush",
    "upvote_ratio": 0.8636363636363636,
    "mention_count": 2,
    "mention_surge": false,
    "subreddit_url": "https://www.reddit.com/r/softwarearchitecture/",
    "total_upvotes": 16,
    "comments_total": 1,
    "total_comments": 1,
    "post_author_url": "https://www.reddit.com/user/nilukush/",
    "signal_category": "adoption",
    "comments_included": 1
  }
}

curl https://signals.autobound.ai/v1/signals/d3a7667f-5871-5bbd-a5e6-81bfbf8ed03e \
  -H "X-API-KEY: $AUTOBOUND_API_KEY"

curl -X POST https://signals.autobound.ai/v1/companies/enrich \
  -H "X-API-KEY: $AUTOBOUND_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"domain":"cred.club","limit":20}'