> ## Documentation Index
> Fetch the complete documentation index at: https://docs.context.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Trust & Maturity

> Who runs Context.dev in production, SOC 2 compliance status, uptime and SLA commitments, and the data-portability story for teams evaluating lock-in risk.

Evaluating Context.dev for a long-lived pipeline? This page collects the signals that usually matter in that review: who already depends on it, how it's secured, what uptime commitments exist, and what it takes to leave.

## Used in production

Context.dev powers production workloads at teams including **Mintlify**, **daily.dev**, **SiteGPT**, **Sourcely**, and **Propane**. Read the [customer stories](https://www.context.dev/customers) for how they use it.

Context.dev is built by a [Y Combinator](https://www.ycombinator.com)-backed company.

## Security and compliance

* **SOC 2 Type I certified**, with Type II in progress. Reports and live control status are available in the [Trust Center](https://trust.context.dev).
* **[Zero Data Retention](/optimization/zero-data-retention)** is available as an opt-in per-request mode on scraping and parsing endpoints.
* A **Data Processing Agreement** is available at [context.dev/dpa](https://www.context.dev/dpa); Enterprise plans include an MSA.
* API keys are secrets scoped to your organization; see the [quickstart](/quickstart) for handling guidance.

## Uptime and support

* Live uptime and incident history are public at [status.context.dev](https://status.context.dev).
* **Enterprise plans carry a 99.9% uptime SLA**, annual invoicing, and a dedicated support channel. See [pricing](https://www.context.dev/pricing).
* Every plan gets support at [hello@context.dev](mailto:hello@context.dev).

## No lock-in by design

The exit cost from Context.dev is intentionally low:

* **Your data already lives with you.** Every response — Markdown, HTML, JSON, images — is delivered to you at request time. There is no data warehouse you'd need to export from Context.dev to migrate away.
* **Standard formats.** Structured extraction is defined by JSON Schemas you write, classifications use official NAICS/SIC/EIC code sets, and scraped content is plain Markdown/HTML. None of it is proprietary to Context.dev.
* **Thin integration surface.** Integrations are HTTP calls (or the [open-source SDKs](https://github.com/context-dot-dev) generated from a published [OpenAPI spec](https://app.stainless.com/api/spec/documented/context.dev/openapi.documented.yml)). Replacing Context.dev means swapping an HTTP client, not re-architecting.
* **Stable contract.** The [API stability policy](/optimization/api-stability) documents versioning and a minimum 90-day deprecation window.

Context.dev is hosted-only — there is no self-hosted edition. In exchange, crawling infrastructure, browser rendering, proxy rotation, and anti-bot handling are operated for you and covered by the commitments above.

## Keep evaluating

<Columns cols={2}>
  <Card title="API Stability & Versioning" icon="shield-check" href="/optimization/api-stability">
    The versioning scheme, breaking-change rules, and deprecation windows.
  </Card>

  <Card title="Trust Center" icon="lock" href="https://trust.context.dev">
    SOC 2 reports, subprocessors, and live control monitoring.
  </Card>

  <Card title="Status Page" icon="signal" href="https://status.context.dev">
    Live uptime and incident history.
  </Card>

  <Card title="Zero Data Retention" icon="eye-slash" href="/optimization/zero-data-retention">
    Opt-in ZDR mode for sensitive scraping and parsing workloads.
  </Card>
</Columns>