Skip to main content
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 for how they use it. Context.dev is built by a Y Combinator-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.
  • 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; Enterprise plans include an MSA.
  • API keys are secrets scoped to your organization; see the quickstart for handling guidance.

​
Uptime and support

  • Live uptime and incident history are public at status.context.dev.
  • Enterprise plans carry a 99.9% uptime SLA, annual invoicing, and a dedicated support channel. See pricing.
  • Every plan gets support at [email protected].

​
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 generated from a published OpenAPI spec). Replacing Context.dev means swapping an HTTP client, not re-architecting.
  • Stable contract. The API stability policy 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

API Stability & Versioning

The versioning scheme, breaking-change rules, and deprecation windows.

Trust Center

SOC 2 reports, subprocessors, and live control monitoring.

Status Page

Live uptime and incident history.

Zero Data Retention

Opt-in ZDR mode for sensitive scraping and parsing workloads.