Implement · Baseten
Can you run it?
Ownership levelSubstantialnone·limited·partial·substantial·fullAnalytical input B ยท 76.8/100
This page is a projection of the one entry record, the Reliability and Data control factors that Implement covers. The full verdict is set by all four factors together, floor-weighted so the weakest caps the whole.
Which domain expands which factor
- AssessUse & modify + Transparency
- ImplementData control + Reliability
- UseReliability
- SupportTransparency
API integration
Hosted Model APIs support the OpenAI Chat Completions, OpenAI Responses and
Anthropic Messages APIs (docs.baseten.co overview). Custom deploys use customer-authored
Truss/Docker configs, not a Baseten-proprietary format, which aids portability of the
deployment definition.
Authentication & account setup
Public docs describe API-key-based access but do not detail org/workspace key-scoping
granularity. Confirm the exact setup in the Baseten console.
Region & residency configuration
Select a region per GPU model deployment with baseten model push --region eu (slugs us and
eu) or the Management API, then call the regional endpoint
(model-{model_id}-region-eu.api.baseten.co). All replicas of that deployment run in the chosen
region. Chains and training jobs cannot select a region, and the organisation's compliance policy
limits which regions are allowed. Regional environments (multi-region fallbacks, exclusion
rules) and Model APIs compliance policies need Baseten support to enable. Self-Hosted lets
the workload plane run in any customer-chosen region or VPC. Baseten operates the control plane
for every option, and the docs do not say where it runs.
Rate limits, tiers & quotas
Default Model API limits are published by account tier: Basic unverified 15 RPM and 100,000 TPM,
Basic verified 120 RPM and 500,000 TPM, Pro 120 RPM and 1,000,000 TPM, Enterprise custom. A model,
service tier or organisation can differ, and the Management API and response headers report the
live limits. Cached and uncached input tokens count equally toward the token limit.
Portability & exit
Terms & Conditions give a documented exit right: Customer Content may be exported for 30 days
after the Term ends, and Baseten will delete Customer Content on written request. Open-weight
models in the Model Library and customer-authored deploy configs keep the workload itself
portable beyond Baseten.
How this scores
The ownership factors this domain covers, drawn from the one entry record.
3
ReliabilityDoes it stay up and stay secure?
StrongThe SLA commits to 99.9% with service credits capped at 40% and a 24h claim window, and is worded as commercially reasonable measures. It is measured on a public status page that logs 7 major or critical incidents between 2026-09-20 and 2026-11-18, all resolved, including a 21-minute outage of all Model APIs on 2026-11-11. Reliability dimension 4 maps to strong.
How this scores (AOI sub-dimensions)
Reliability4/5whether it stays up, with an SLA and status historyA committed SLA (baseten.co/service-level-agreement, stamped September 15, 2026) undertakes "commercially reasonable measures" to reach 99.9% monthly availability for both Dedicated Inference and Model APIs.
Security4/5the controls protecting your traffic and dataIsolation is logical namespace separation for shared use (access controls, unique customer identifiers, namespace isolation), single-tenant dedicated Kubernetes namespaces with Calico/Cilium network policies ("GPUs never shared across users") and self-hosted deployment inside the customer's own VPC.
Compliance4/5which independent certifications and attestations it holdsSOC 2 Type II is confirmed with a named audit firm (Sensiba San Filippo LLP, clean opinion across Security/Availability/Processing Integrity/Confidentiality/Privacy criteria).
4
Doesn't extract your dataDo the binding terms keep your data and IP yours?
StrongTerms Sec 6.3 and DPA 4.4 bar training, and the Security Practices state a ZDR posture for Model APIs and Dedicated Inference (docs: 'Synchronous requests run under ZDR by default'). Customer Content is customer-owned, and Sec 11 sets a mutual confidentiality duty (data_governance 4). Caveats: Async Inference queues inputs for up to 72 hours, the Security Practices exempt retention that follows from customer configuration or customer code, and Model APIs residency needs a support-enabled policy.
How this scores (AOI sub-dimensions)
Data governance4/5retention, training-on-inputs and data ownershipThe binding documents set a strong posture.
Residency3/5where your data is processed and storedAn EU region is available for at least some workloads, which is the score-3 anchor.
What this means for adoptionYou substantially own inference here. The binding Terms and DPA bar training on your content (including deployed model weights), the Security Practices commit Model APIs and Dedicated Inference to Zero Data Retention, and confidentiality is mutual, a stronger standard-terms posture than most peers. A committed 99.9% SLA with credits adds reliability. Ownership falls short of full for four reasons. ISO 27001, PCI DSS and the SOC reports are vendor claims behind an access gate. The ZDR wording is a posture with a customer-controlled-factors carve-out and no explicit default. Async Inference keeps inputs for up to 72 hours. A self-serve EU region exists only for dedicated model deployments, and Model APIs residency needs a support-enabled policy. For EU residency of serverless traffic, or certificates confirmed first, deploy dedicated in the eu region or request the Trust Center documents.
Sources
The same evidence records as the entry sheet. Read means the text was verified; unverified means it is known to exist but not yet read.
Terms of serviceread2026-11-19
Baseten Terms & Conditions.
Securityread2026-11-19
Baseten Security Practices (Last Updated November 12, 2026).
Data Processing Addendumread2026-11-19
Baseten DPA (Last Updated September 15, 2026).
Vendor announcementread2026-11-19
Baseten blog post (originally published 2023-03-08, last updated 2026-11-02; vendor marketing) stating SOC 2 Type II, audited by Sensiba San Filippo LLP, covering Security/Availability/Processing Integrity/Confidentiality/Privacy criteria with a clean opinion across 70+ sub-criteria.
Securityread2026-11-19
Baseten Trust Center (Vanta; launched 2026-07-30; renders only in a browser, curl returns only a title).
Documentationread2026-11-19
Baseten Regional deployments docs.
Documentationread2026-11-19
Baseten regional-environments docs and the Model APIs overview.
Documentationread2026-11-19
Baseten hosting options and Self-Hosted docs (hosting-options/overview.md and observability/security.md).
Documentationread2026-11-19
Baseten security docs (docs.baseten.co/security.md and observability/security.md).
Slaread2026-11-19
Baseten status page (status.baseten.co statuspage JSON): 'All Systems Operational' across Dedicated Inference, Model APIs, Training, Model Management API, Web Application, Homepage and Docs, and Sandboxes (with Oregon, Virginia and Frankfurt Sandboxes components).
Slaread2026-11-19
Baseten Service Level Agreement (Last Updated September 15, 2026).
Vendor announcementread2026-11-19
Baseten pricing page.
Documentationread2026-11-19
Baseten Model APIs overview (docs.baseten.co/inference/model-apis/overview.md).
Documentationread2026-11-19
Baseten Model APIs pricing-and-limits and deprecation docs.
Documentationread2026-11-19
Baseten platform overview docs (docs.baseten.co/overview.md and the Model APIs overview).