Serving models on OpenAI is harder than it should be
MLOps2 posts from 2 people2d active+00 posts in the last 7 days, 1 the 7 days before (fading)Unverified
Posts per day
The posts behind it
2, newest first[Feature]: Support OpenAI Decisions API as an auto-router classifier backend...as a provider - calling `{api_base}/v1/decisions`. However, there is currently **no way to use the OpenAI Decisions API as the auto-router's classifier backend**. ### Current state The auto-router's `classifier_type` supports: PR #45200 introduces `classifier_type:...BerriAI/litellm · elvis-cai1 reactionsOpen ↗[FR] Add STACKIT Model Serving as a native AI Gateway provider...Serving directly discoverable when configuring LLM endpoints. > #### Why is it currently difficult to achieve this use case? STACKIT AI Model Serving is OpenAI-compatible, so users can potentially work around the lack of a dedicated provider by configuring it through an existing...mlflow/mlflow · haya-fatima1 repliesOpen ↗
Companies and products named
About this problem
Evidence
2 posts from 2 people in 2 places, about 1 a week over 22 days. Mostly on mlflow/mlflow, BerriAI/litellm. Tools named alongside: MLflow, Databricks, Cloudflare.
Frustration Frustration 0 of 3· Seen on GitHub issues
How it was grouped
Posts that state a pain and match the "model-serving" rule about OpenAI. First post Sep 18, 2026, latest Oct 9, 2026. Unverified: fewer than 3 posts, or one person or place only. Method
The same problem elsewhere
Other OpenAI problems
Fine-tuning OpenAI is costly and unpredictableOpenAI users keep asking for helpRunning OpenAI locally hits memory and speed limitsOpenAI upgrades break working setupsTrouble with OpenAI chatTrouble with OpenAI responsesOpenAI fails to return valid structured outputTrouble with OpenAI astraTrouble with OpenAI customTrouble with OpenAI imageOpenAI tables suffer from small files and skewTrouble with OpenAI crashes
History
steady to fading
Serving models on OpenAI is harder than it should be (2 posts)