Baseten
AI model deployment and inference platform for running ML models in production.
Baseten CLI 1.0.0 ships a stable command contract as regional deployments unlock enterprise compliance use cases.
◆Recent moves
- 17h ago
Baseten CLI 1.0.0
⚡ SPARKThe Baseten CLI reaches 1.0.0 with a stable command surface, marking the end of breaking changes in the primary interface for model deployment automation. This is a contract commitment, not a feature release—the signal is that the CLI is now safe to embed in CI/CD pipelines without tracking upstream changes.
View source ↗ - 3d ago
Baseten deprecates GLM 4.7, Kimi K2, Inkling, and DeepSeek v4 Pro on September 25
GLM 4.7, Kimi K2.7/K2.6, Inkling, Inkling Small, and DeepSeek v4 Pro are being deprecated on September 25th. Removing underutilized model variants keeps the API catalog manageable and is consistent with Baseten's pattern of rotating models as successor versions land.
View source ↗ - 4d ago
OIDC and AWS AssumeRole for training jobs
Training jobs can now authenticate via OIDC or AWS AssumeRole to pull private container images and download weights without storing long-lived credentials in Baseten. This removes a security anti-pattern that previously required teams to embed static cloud credentials to access private assets during builds.
View source ↗ - 4d ago
Model API costs
A new Management API endpoint returns per-day model API spend subtotals, giving teams programmatic access to billing data without manual dashboard exports. For organizations with chargeback requirements or cost monitoring pipelines, this fills a gap that previously required manual reconciliation.
View source ↗ - 5d ago
DeepSeek V4.1 Flash available on Baseten
DeepSeek V4.1 Flash, a 552B-parameter multimodal model built for agentic and coding workflows, is now available via Baseten Model APIs. Model catalog additions like this follow Baseten's pattern of adding frontier models shortly after release, giving inference customers immediate access without self-hosting.
View source ↗ - 5d ago
Regional deployments
Regional deployments allow every replica in a deployment to be pinned to a specific Baseten region, supporting data residency and compliance requirements. Configurable via the dashboard, CLI, or Management API, this also addresses latency-sensitive workloads that benefit from geographic proximity.
View source ↗