Use · Together AI

Is it good enough?

Ownership levelPartialnone·limited·partial·substantial·fullAnalytical input B · 75.2/100

This page is a projection of the one entry record, the Reliability factor that Use 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

Models served

Together serves a broad open-weight catalogue rather than a single family:

Llama 3.x / Llama 4 (Meta)
DeepSeek V3 / R1
Qwen3, including the 235B
Mistral / Mixtral
gpt-oss 20B / 120B
plus embedding and image models

For adopters this is the point of the provider: the pricing page and independent third-party provider analysis both show one OpenAI-compatible endpoint fronting most of the models documented elsewhere in this library, so you can A/B a workload across families without changing integration code.

Inference features

Together's OpenAI-compatibility docs describe OpenAI-compatible chat/completions with streaming, tool use and structured outputs, plus embeddings and image generation. How fully each higher-level behaviour works still depends on the specific served model's own capabilities - see each model's entry in this library - and was not individually re-verified on Together's endpoints, so treat per-feature support as "documented at the API, inherited from the model, confirm per model."

How this scores

The ownership factor this domain covers, drawn from the one entry record.

ReliabilityDoes it stay up and stay secure?

Moderate

SOC 2 Type II is announced via an independent audit and the security docs describe encryption and pen-testing, but there is no public uptime SLA, status page or SOC 2 report obtained.

How this scores (AOI sub-dimensions)

Reliability2/5whether it stays up, with an SLA and status historyNo incidents surfaced in research, but no public uptime SLA, status page or failover documentation was found or independently verified.

Security4/5the controls protecting your traffic and dataThe SOC 2 announcement and security docs describe encryption in transit and at rest, audit logging, MFA/RBAC and regular pen-testing, and the DPA requires encryption of controller data in transit and storage.

Compliance4/5which independent certifications and attestations it holdsSOC 2 Type II is announced via an independent multi-month audit, and a GDPR DPA binds Together to EU Standard Contractual Clauses.

What this means for adoptionYou own your workloads here in the ways that matter most: the Terms leave you owning your inputs and outputs, ZDR-by-default with no-training keeps them yours, and the open-weight catalogue on an OpenAI-compatible API is a clean portable exit. But overall ownership is partial, not substantial: the no-retention posture is Together's own self-attestation rather than independently audited, and the US HQ with DPA-confirmed North America default routing carries standing CLOUD Act exposure even for EU-hosted workloads, so data-control is moderate rather than strong. Pin the EU region on a paid tier if residency matters, and teams needing an audited no-retention guarantee should contract it in the DPA rather than rely on the default terms.

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.

Privacy Policyread2026-07-25

Privacy Policy: inputs and outputs are not stored by default (zero data retention); under ZDR content is not stored, retained, or used for model training or product improvement except as needed to provide the Services; temporary caching may be used for performance; training on data is opt-in and off by default, controlled by an org-admin Privacy & Security setting.

Documentationread2026-07-25

Privacy and security docs: HIPAA-aligned data encryption in transit and at rest, audit logging and business associate agreements; layered security architecture with MFA/RBAC, continuous monitoring and regular vulnerability assessments; ZDR restated.

Vendor announcementread2026-07-25

SOC 2 Type II announcement: achieved via an independent, multi-month audit validating access management, data encryption, incident response and change management; regular penetration testing.

Documentationread2026-07-25

EU data centres and dedicated model deployment - dedicated endpoints on targeted data centres including EU locations (Sweden GPU capacity) - are available only on Scale and Enterprise tier plans.

Vendor announcementunverified2026-07-25

Serverless per-token pricing page (live rates not published): gpt-oss-120B ~$0.15/$0.60, Qwen3-235B ~$0.20/$0.60, DeepSeek-V3 ~$1.25/M - approximate and move frequently.

Documentationread2026-07-25

OpenAI-compatibility docs: an OpenAI-compatible /v1 REST API at api.together.ai/v1, used by pointing an existing OpenAI client at Together's base URL and API key (TOGETHER_API_KEY), with chat/completions, streaming, tool use and structured outputs across the open-weight catalogue.

Terms of serviceread2026-07-25

Terms of Service: as between you and Company you exclusively own all right, title and interest in Your Content and Output, granting Company only a limited license to operate them to provide the Services; Together does not use your data to train its models without your explicit opt-in and consent; the Company owns Company IP and Usage Data.

Third-party analysisread2026-07-25

Independent third-party price/performance analysis of Together AI corroborates the approximate serverless rates and shows the same open-weight models served across many providers (portability).

Data Processing Addendumread2026-07-25

Data Processing Addendum: Together (US) Inc.