Open source with self-hosted infrastructure costs; some AI Gateway governance and budgeting capabilities are documented without a public list price.
↻ Billing notes
MLflow does not publish a standard monthly or annual software subscription on the provided official pages. The official site presents MLflow as forever free and open source under Apache 2.0, while the gateway budget documentation describes daily, weekly, and monthly budget windows plus alert and reject actions. No public trial length, seat minimum, renewal rule, or discount schedule is disclosed in the supplied documents. For deployment, the documents indicate teams may self-host the stack and manage related infrastructure themselves.
The official site describes MLflow as 100% open source under Apache 2.0 and says it is forever free. Public documents do not disclose a subscription fee, seat minimum, or tiered software license pricing.
MLflow AI Gateway budget policies
Not publicly disclosed
Not publicly disclosed
Budget alerts
Reject policies with HTTP 429 responses
Alert webhooks
Daily, weekly, and monthly reset windows
Workspace-scoped budget enforcement
Local or Redis budget tracking
The documents describe configurable spending thresholds and enforcement behavior, but they do not publish a separate product price for budget policies or a paid add-on fee.
The gateway is documented as the control plane for routing, tracing, budget policies, traffic splitting, and fallbacks. The materials explain how to configure endpoints and budgets, but they do not provide a public usage fee, overage rate, or seat-based add-on price.
⚠ MLflow’s public materials make clear that the software itself is open source, but they also show that teams may need to budget for the infrastructure required to run it. The comparison content says running MLflow beyond a basic local use case requires setting up a tracking server, a backing database, artifact storage, and authentication yourself. That means the real cost is usually implementation and operations rather than a software license.
⚠ The MLflow article on avoiding runaway agent costs shows that the AI Gateway can reduce cost shock, but it also implies ongoing spend on the underlying model providers. The post explicitly notes that the illustrated costs vary by provider, pricing tier, and token volumes, so your total cost depends heavily on usage patterns and third-party model pricing rather than MLflow list pricing.
Yes. The official site says MLflow is open source under Apache 2.0 and describes it as forever free, no strings attached. The supplied documents do not show a public paid license for the core platform. However, if you self-host, your organization still pays for infrastructure, maintenance, and any third-party model usage.
Not in the supplied documents. The official pages describe features such as tracing, evaluations, prompt management, and AI Gateway budgets, but they do not provide a public plan table with monthly or annual subscription amounts. If a team is looking for a quoted enterprise package, that is not publicly disclosed in the provided sources.
The gateway documentation says budgets can be set as daily, weekly, or monthly thresholds, and the system can either alert via webhook or reject subsequent requests with HTTP 429. The docs also note that budgets can be scoped to workspaces and tracked locally or through Redis. Public pricing for these controls is not disclosed.