# down.guide

> A free outage feed for people and agents. down.guide reads the official status pages of 404 cloud, SaaS and developer providers every minute, normalizes their incidents, and labels its own evidence (visitor reports) as its own. Built by Sazabi.

Every page has a markdown copy: add .md to the URL (the homepage is https://down.guide/index.md) or send `Accept: text/markdown`.

## MCP
- https://mcp.down.guide/mcp (also https://down.guide/mcp): Streamable HTTP, no auth. Tools: get_provider, list_feed, get_incident, search, check_stack, check_dependency, get_leaderboard, send_feedback, report_outage, report_affected.

## REST API (no key; JSON)
- GET https://down.guide/api/v1/providers/<slug>: Get provider (MCP tool `get_provider`, same JSON)
- GET https://down.guide/api/v1/incidents: List feed (MCP tool `list_feed`, same JSON)
- GET https://down.guide/api/v1/incidents/<id>: Get incident (MCP tool `get_incident`, same JSON)
- GET https://down.guide/api/v1/search: Search (MCP tool `search`, same JSON)
- POST https://down.guide/api/v1/check: Check stack (MCP tool `check_stack`, same JSON)
- GET https://down.guide/api/v1/dependency: Check dependency (MCP tool `check_dependency`, same JSON)
- GET https://down.guide/api/v1/leaderboard: Get leaderboard (MCP tool `get_leaderboard`, same JSON)
- POST https://down.guide/api/v1/feedback: Send feedback (MCP tool `send_feedback`, same JSON)
- POST https://down.guide/api/v1/reports: Report outage (MCP tool `report_outage`, same JSON)
- POST https://down.guide/api/v1/reports/affected: Report affected (MCP tool `report_affected`, same JSON)
- GET https://down.guide/api/v1/search: q takes free text and keys such as provider:, impact:major_outage, region:us-east-1, started:>30d, duration:>2h, has:rca, cause:dns and sort:relevance|started|duration|index. Terms are ANDed, commas OR values, a leading - excludes. Words match whole words and their English forms (errors finds error), a misspelled word also matches the indexed names closest to it (githb finds GitHub; match.text lists them as alsoAs), and "last week", "past month" or "today" read as a started: bound. A query with a problem (an unknown key or value) runs nothing and lists the problems
- Typed search parameters, each ANDed with q (q is optional when one is given): provider, category, impact and level (comma lists or repeated), kind (incident, maintenance, all), state (active, resolved) and started (one bound each, e.g. started=>=2026-10-01&started=<2026-10-08). With no words, results are newest first
- Each search result's match says why it matched: the fields each word hit (provider, title, summary, components, updates) and the key terms it meets. facets counts every match by provider, category, impact, level, kind and state (facets=false leaves it out). query echoes what ran
- With no matches, suggestions lists broader queries that do match. An empty answer is not evidence that nothing happened
- limit (1 to 100) and cursor (the next_cursor of the last page) page through the results; offset is a deprecated alias of cursor
- POST https://down.guide/api/v1/check takes manifest_name (optional), manifest_content, providers or stack_id (JSON), or the raw file; input is a deprecated alias of manifest_content
- POST https://down.guide/api/stack: save a stack from the same body; returns stack_id (keeps only provider slugs) for check_stack, https://down.guide/stack?stack_id=<id> and the CLI
- GET https://down.guide/api/v1/providers: the catalog with live state
- GET https://down.guide/api/v1/status: one line per provider
- GET https://down.guide/api/stats: catalog and usage numbers
- OpenAPI: https://down.guide/openapi.json

## Feeds
- https://down.guide/feed (RSS), ?format=atom, ?format=json. Filters: provider, category, impact, region, component, level, kind=all, state=active, filter=major. Example: https://down.guide/feed?provider=github,vercel&filter=major&format=json
- Badges: https://down.guide/badge/<provider>.svg

## Pages
- [What's down now](https://down.guide/index.md)
- [Live](https://down.guide/live.md)
- [Providers](https://down.guide/providers.md); one page per provider at https://down.guide/<slug> ("Is <provider> down?"), history at /<slug>/history
- Incidents: https://down.guide/<provider>/<DWN-id> (also https://down.guide/<DWN-id>)
- [Down Index](https://down.guide/leaderboard.md), [methodology](https://down.guide/leaderboard/methodology.md), weekly archives at /leaderboard/<YYYY-Www>
- [Rankings](https://down.guide/rankings.md), [Postmortems](https://down.guide/search?q=has%3Arca), [Cascades](https://down.guide/events.md), [Daily recaps](https://down.guide/recaps.md) at /recaps/<YYYY-MM-DD> (RSS: https://down.guide/recaps/feed.xml)
- [Check your stack](https://down.guide/stack.md), [About](https://down.guide/about.md), [Our own status](https://down.guide/status)

## Trust rules
- Provider words are quoted verbatim and linked; down.guide's own evidence is always labeled as ours.
- Denials are shown, never deleted.

## Corrections
- Wrong data, a missing provider or mapping, or a probe false positive: open an issue at https://github.com/sazabi/down.guide (public docs and issue forms, no source code). Private notes: the send_feedback tool or POST https://down.guide/api/v1/feedback.

## Optional
- [Full docs for agents](https://down.guide/llms-full.txt)
- [Agent skill](https://down.guide/.well-known/agent-skills/down-guide/SKILL.md)

## MCP tools in full
### get_provider
Is <provider> down? One provider's live state from its official status page (operational, degraded, partial_outage, major_outage, maintenance, or not_reporting when down.guide can't read the page), a one-line verdict, open incidents, early warnings (signs of a problem down.guide sees before the provider posts), 90 days of daily bars and reliability stats.

Input schema:
```json
{
  "type": "object",
  "properties": {
    "provider": {
      "type": "string",
      "description": "Slug or name, e.g. github, aws, openai"
    }
  },
  "required": [
    "provider"
  ],
  "additionalProperties": false
}
```

### list_feed
The newest incidents across providers (14 days), newest first, open ones on top. Filters combine: provider, category, impact, region, component, level (early_warning, confirmed, not_acknowledged), kind (incident, maintenance, all), state (active or recent) and filter=major (major outages plus 30+ minute incidents at the 50 most-depended-on providers). History imported from provider archives is never listed.

Input schema:
```json
{
  "type": "object",
  "properties": {
    "provider": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Provider slugs"
    },
    "category": {
      "type": "array",
      "items": {
        "type": "string",
        "enum": [
          "cloud",
          "hosting",
          "data",
          "ai",
          "devtools",
          "observability",
          "auth",
          "commerce",
          "messaging",
          "workplace"
        ]
      },
      "description": "Categories"
    },
    "impact": {
      "type": "array",
      "items": {
        "type": "string",
        "enum": [
          "operational",
          "maintenance",
          "degraded",
          "partial_outage",
          "major_outage",
          "unknown"
        ]
      },
      "description": "Worst impact reached"
    },
    "region": {
      "type": "string",
      "description": "e.g. us-east-1, eu, apac"
    },
    "component": {
      "type": "string",
      "description": "A component name or part of one"
    },
    "level": {
      "type": "array",
      "items": {
        "type": "string",
        "enum": [
          "early_warning",
          "confirmed",
          "not_acknowledged"
        ]
      },
      "description": "Detection levels"
    },
    "kind": {
      "type": "string",
      "enum": [
        "incident",
        "maintenance",
        "all"
      ]
    },
    "state": {
      "type": "string",
      "enum": [
        "active",
        "recent"
      ]
    },
    "filter": {
      "type": "array",
      "items": {
        "type": "string",
        "enum": [
          "major"
        ]
      },
      "description": "major"
    },
    "limit": {
      "type": "number",
      "minimum": 1,
      "maximum": 100
    }
  },
  "additionalProperties": false
}
```

### get_incident
One incident by down.guide id (DWN-…): every update the provider posted, verbatim, down.guide's own evidence (probe regions, report and social counts, always labeled as ours), lead time, a model-written summary (labeled with the model), root cause and postmortem link when published, and the cascade event it belongs to.

Input schema:
```json
{
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "description": "e.g. DWN-1a2b3c4d5e"
    }
  },
  "required": [
    "id"
  ],
  "additionalProperties": false
}
```

### search
Search incidents (400 days) and providers: the one tool for finding past and present incidents, by words or by fields. Pass q (free text plus query keys: provider:, category:, impact:, region:, component:, level:, state:, kind:, started: (>30d, 2026-10, <2026-01-01), duration: (>2h), has: (rca, summary, lead, event), cause: (deploy_config, dns, network, certificate, capacity, upstream, datacenter, security), event:, sort: (relevance, started, duration, index); terms are ANDed, commas OR values, a leading - excludes), the typed parameters, or both: each parameter is ANDed with q as its key term. With no words, results are newest first, so provider: ["github"] lists GitHub's newest incidents. Words match whole words and their English forms, a misspelled word also matches the closest indexed names (githb finds GitHub), and "last week" or "past month" read as a started: bound. Each result's match says why it matched: the fields each word hit (provider, title, summary, components, updates), the names a misspelled word was also searched as (alsoAs), and the key terms it meets. query echoes what ran, facets counts every match by provider, category, impact, level, kind and state, and problems lists anything the query couldn't use (a query with problems returns no results). With no matches, suggestions lists broader queries that do match; an empty answer is not evidence that nothing happened. Pass next_cursor back as cursor for the next page.

Input schema:
```json
{
  "type": "object",
  "properties": {
    "q": {
      "type": "string",
      "description": "Free text and query keys. Optional when a typed parameter is passed."
    },
    "provider": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Provider slugs or names (any of them)"
    },
    "category": {
      "type": "array",
      "items": {
        "type": "string",
        "enum": [
          "cloud",
          "hosting",
          "data",
          "ai",
          "devtools",
          "observability",
          "auth",
          "commerce",
          "messaging",
          "workplace"
        ]
      },
      "description": "Provider categories (any of them)"
    },
    "impact": {
      "type": "array",
      "items": {
        "type": "string",
        "enum": [
          "operational",
          "maintenance",
          "degraded",
          "partial_outage",
          "major_outage",
          "unknown"
        ]
      },
      "description": "Worst impact reached (any of them)"
    },
    "level": {
      "type": "array",
      "items": {
        "type": "string",
        "enum": [
          "early_warning",
          "confirmed",
          "not_acknowledged"
        ]
      },
      "description": "Detection levels (any of them)"
    },
    "kind": {
      "type": "string",
      "enum": [
        "incident",
        "maintenance",
        "all"
      ],
      "description": "incident or maintenance; both when omitted or all"
    },
    "state": {
      "type": "string",
      "enum": [
        "active",
        "resolved"
      ],
      "description": "active (still open) or resolved; both when omitted"
    },
    "started": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Start-time bounds, all applied: an age (>30d) or a date (>=2026-10-01, 2026-10); two bounds make a window, e.g. [\">=2026-10-01\", \"<2026-10-08\"]"
    },
    "limit": {
      "type": "integer",
      "minimum": 1,
      "maximum": 100,
      "default": 25
    },
    "cursor": {
      "type": "string",
      "description": "next_cursor of the last page"
    },
    "facets": {
      "type": "boolean",
      "description": "false leaves out the counts per facet"
    },
    "offset": {
      "type": "integer",
      "minimum": 0,
      "description": "Deprecated: use cursor"
    }
  },
  "additionalProperties": false
}
```

### check_stack
Which providers a project depends on, and whether any has a problem now. Pass manifest_content: the contents of a package.json, any lockfile, requirements.txt, go.mod, Gemfile, Terraform, docker-compose, a .env file (only variable names are read) or a list of domains (manifest_name, the file name, is optional and only breaks ties); providers: slugs; or stack_id: the id of a stack saved with POST https://down.guide/api/stack (the same body as /api/v1/check; only the provider slugs are kept). They combine. Returns each provider with the reasons it matched, live state, open incidents and a feed URL for exactly that stack. manifest_content is not stored. No providers matched means none found, not that the project has no providers.

Input schema:
```json
{
  "type": "object",
  "properties": {
    "manifest_name": {
      "type": "string",
      "description": "Optional. The file name (package.json, poetry.lock, main.tf, .env.example...); the format is detected from the content and the name only breaks ties."
    },
    "manifest_content": {
      "type": "string",
      "description": "The file's contents (2 MB max)"
    },
    "stack_id": {
      "type": "string",
      "description": "The stack_id returned by POST https://down.guide/api/stack"
    },
    "providers": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Provider slugs"
    },
    "input": {
      "type": "string",
      "description": "Deprecated: use manifest_content"
    }
  },
  "additionalProperties": false
}
```

### check_dependency
One dependency to the providers behind it and their live state: a package name (openai, npm:@aws-sdk/client-s3, pypi:stripe), an API host (api.github.com), an environment variable name (STRIPE_SECRET_KEY), a Terraform provider or resource, a container image or a provider name.

Input schema:
```json
{
  "type": "object",
  "properties": {
    "name": {
      "type": "string"
    }
  },
  "required": [
    "name"
  ],
  "additionalProperties": false
}
```

### get_leaderboard
The Down Index: a week's worst incidents scored 0-100 (impact 30, breadth 20, duration 15, reach 20, acknowledgement 15; maintenance and narrow-scope incidents excluded), or with view=reliability the monthly ranking (minutes per impact, incident count, median time to resolve, median acknowledgement lag, postmortem rate).

Input schema:
```json
{
  "type": "object",
  "properties": {
    "view": {
      "type": "string",
      "enum": [
        "index",
        "reliability"
      ]
    },
    "week": {
      "type": "string",
      "description": "YYYY-Www, this week by default"
    },
    "month": {
      "type": "string",
      "description": "YYYY-MM for view=reliability"
    },
    "category": {
      "type": "string",
      "enum": [
        "cloud",
        "hosting",
        "data",
        "ai",
        "devtools",
        "observability",
        "auth",
        "commerce",
        "messaging",
        "workplace"
      ]
    },
    "limit": {
      "type": "number",
      "minimum": 1,
      "maximum": 500
    }
  },
  "additionalProperties": false
}
```

### send_feedback
Send a note to the people who run down.guide: a wrong provider mapping, a missing provider, a bad summary. Not public.

Input schema:
```json
{
  "type": "object",
  "properties": {
    "message": {
      "type": "string",
      "maxLength": 4000
    },
    "page": {
      "type": "string",
      "description": "The down.guide URL it is about"
    },
    "contact": {
      "type": "string",
      "description": "Optional email for a reply"
    }
  },
  "required": [
    "message"
  ],
  "additionalProperties": false
}
```

### report_outage
Report that a provider isn't working for you (or for the agent's user) right now. Reports count only in aggregate against the provider's own baseline, are deduplicated per caller per 10 minutes, and alone never make a public claim.

Input schema:
```json
{
  "type": "object",
  "properties": {
    "provider": {
      "type": "string"
    },
    "incident_id": {
      "type": "string"
    }
  },
  "required": [
    "provider"
  ],
  "additionalProperties": false
}
```

### report_affected
Say an existing incident affects you. Counted in aggregate on the incident page, deduplicated per caller per 10 minutes.

Input schema:
```json
{
  "type": "object",
  "properties": {
    "provider": {
      "type": "string"
    },
    "incident_id": {
      "type": "string"
    }
  },
  "required": [
    "provider",
    "incident_id"
  ],
  "additionalProperties": false
}
```

## Down Index
- Impact: 30 points
- Breadth: 20 points
- Duration: 15 points
- Reach: 20 points
- Acknowledgement: 15 points
See https://down.guide/leaderboard/methodology.md.

## FAQ
### What is down.guide?
A free outage feed for people and agents. It reads the official status pages of 404 cloud, SaaS and developer providers every minute, normalizes their incidents, and adds its own evidence: probes from four regions, reports from visitors and chatter on Bluesky, Hacker News and Mastodon.

### Where does the data come from?
Each provider's own status page (Atlassian Statuspage, incident.io, Instatus, Better Stack, status.io, and the AWS, Google Cloud, Slack and Salesforce feeds, with RSS as a fallback). Their words are quoted verbatim and linked. down.guide's own evidence is always labeled as ours, with numbers.

### What do the probes do?
One unauthenticated GET per provider endpoint per region per minute, from Washington, San Francisco, Frankfurt and Singapore, with the User-Agent down.guide-probe and a link to this page. No credentials, no bodies read; any answer below HTTP 500 counts as reachable. A single region failing is treated as a network blip, never a signal.

### What happens when I press "I'm seeing a problem"?
It adds one to an hourly count for that provider. Reports are only ever shown in aggregate, deduplicated per visitor every 10 minutes, capped per hour, and weighed against the provider's own normal rate so one network can't make a spike. We keep a daily-salted hash, not your IP.

### What is the Down Index?
A 0-100 score for every confirmed incident from impact, breadth, duration, the provider's reach and how long it took to acknowledge. The weekly table lists the worst. The methodology page has the exact weights.

### How is uptime calculated?
From each provider's own incidents, per component, the way Statuspage computes its own: a major outage counts as full downtime and a partial outage as 30%; degraded performance and maintenance don't count. An incident counts against the components it names, and one that names none counts as a single component unless the page lists no components at all. An incident confined to named cloud regions (us-east-1, europe-west2) is a regional outage: it counts as a partial outage at most, and only for that share of the provider's regions, so one AWS region down isn't all of AWS down. Minor or regional issues (below) never count. The window starts at the provider's first data point.

### What are minor or regional issues?
Incidents confined to a slice of a provider rather than the provider itself: at any provider, a title naming one country, continent or market region ("EU", "US Region", "APAC"), one data center, cluster, city or point of presence, or a named subset of customers ("a small number of users"); one carrier route or local market at a messaging or voice API (Twilio, Sinch, Bandwidth, Plivo, Telnyx); one carrier at a shipping API (Shippo, EasyPost); one chain or network at a blockchain node API (Alchemy, Infura); and one asset, network or funding method at a crypto exchange (Kraken, Coinbase). They're listed on the provider's page but never set its state, and they stay out of the open-incident count, the Down Index, the major filter and uptime. A title about all regions, countries or destinations, global or worldwide, all assets, trading, sign-in or the dashboard is a normal incident; one naming a cloud region code (us-east-1) is a regional outage, which counts toward that region's uptime.

### Why is an incident on two provider pages but counted once?
Some catalog entries read the same status page (GitHub Actions and GitHub, SendGrid and Twilio), and some pages cross-post each other's incidents (Akamai and Linode). Each provider page shows it, but sitewide numbers (open incidents, Happening now, downtime, the Down Index) count it once.

### How do agents use it?
An MCP server at https://mcp.down.guide/mcp (also /mcp on this site), a REST API under /api/v1 with the same JSON as each MCP tool, RSS/Atom/JSON feeds you can filter by provider, category, impact, region or your stack, and a .md copy of every page.

### How do I get outage alerts in Slack or Discord?
Subscribe to a feed; there is no account or webhook to set up. https://down.guide/feed has every incident, /feed?provider=<slug> one provider, and the stack checker builds one feed for all of a project's providers. In Slack, install the RSS app and run /feed subscribe <feed URL> in a channel; in Discord, give the URL to a feed bot such as MonitoRSS. Add format=atom or format=json for Atom or JSON Feed.

### What does it cost?
Nothing, and there's no account to make. There is no token or coin, and there never will be.

### Who runs it?
Sazabi, which builds AI-native observability and security. down.guide is a free Sazabi Labs project, like cve.now. It uses no Sazabi customer data.

### A provider is missing or a mapping is wrong.
Open an issue at https://github.com/sazabi/down.guide: it has forms for wrong data, missing providers and probe false positives, and documents how the data is collected. For anything private, use send feedback (the form on any page, the send_feedback MCP tool, or POST /api/v1/feedback). A person reads every note.

## Providers
- 1password: 1Password (auth)
- ably: Ably (messaging)
- abstract-api: Abstract API (data)
- affirm: Affirm (commerce)
- agora: Agora (messaging)
- ai21: AI21 Labs (ai)
- airbyte: Airbyte (data)
- aircall: Aircall (messaging)
- airtable: Airtable (workplace)
- aiven: Aiven (data)
- akamai: Akamai (cloud)
- alchemy: Alchemy (commerce)
- amplitude: Amplitude (data)
- anthropic: Anthropic (ai)
- api-video: api.video (hosting)
- apify: Apify (data)
- apollo: Apollo GraphOS (devtools)
- apollo-io: Apollo.io (workplace)
- appwrite: Appwrite Cloud (data)
- asana: Asana (workplace)
- ashby: Ashby (workplace)
- assemblyai: AssemblyAI (ai)
- attio: Attio (workplace)
- autumn: Autumn (commerce)
- avalara: Avalara (commerce)
- aws: AWS (cloud)
- axiom: Axiom (observability)
- azure: Microsoft Azure (cloud)
- bandwidth: Bandwidth (messaging)
- basecamp: Basecamp (workplace)
- baseten: Baseten (ai)
- beehiiv: beehiiv (messaging)
- betterstack: Better Stack (observability)
- bigcommerce: BigCommerce (commerce)
- bitbucket: Bitbucket (devtools)
- bitrise: Bitrise (devtools)
- bland: Bland AI (ai)
- bolt: Bolt.new (ai)
- box: Box (workplace)
- braintrust: Braintrust (ai)
- braze: Braze (messaging)
- brevo: Brevo (messaging)
- brex: Brex (commerce)
- browserbase: Browserbase (devtools)
- browserstack: BrowserStack (devtools)
- bubble: Bubble (hosting)
- bugsnag: Bugsnag (observability)
- buildkite: Buildkite (devtools)
- bunny: Bunny.net (cloud)
- calendly: Calendly (workplace)
- canva: Canva (workplace)
- cartesia: Cartesia (ai)
- census: Census (data)
- cerebras: Cerebras (ai)
- chargebee: Chargebee (commerce)
- checkly: Checkly (observability)
- chroma: Chroma Cloud (data)
- chromatic: Chromatic (devtools)
- circle: Circle (messaging)
- circleci: CircleCI (devtools)
- clearbit: Clearbit (data)
- clerk: Clerk (auth)
- clickhouse-cloud: ClickHouse Cloud (data)
- clickup: ClickUp (workplace)
- close: Close (workplace)
- cloudflare: Cloudflare (cloud)
- cloudflare-workers: Cloudflare Workers (hosting)
- cloudflare-zero-trust: Cloudflare Zero Trust (auth)
- cloudinary: Cloudinary (hosting)
- cloudsmith: Cloudsmith (devtools)
- cockroachdb: CockroachDB Cloud (data)
- coda: Coda (workplace)
- codecov: Codecov (devtools)
- codemagic: Codemagic (devtools)
- codesandbox: CodeSandbox (devtools)
- cohere: Cohere (ai)
- coinbase: Coinbase (commerce)
- composio: Composio (ai)
- configcat: ConfigCat (devtools)
- confluence: Confluence (workplace)
- confluent: Confluent Cloud (data)
- contentful: Contentful (data)
- convertkit: Kit (messaging)
- convex: Convex (data)
- coralogix: Coralogix (observability)
- coreweave: CoreWeave (ai)
- couchbase: Couchbase Capella (data)
- courier: Courier (messaging)
- coveralls: Coveralls (devtools)
- crates-io: crates.io (devtools)
- crowdin: Crowdin (devtools)
- customerio: Customer.io (messaging)
- cypress-cloud: Cypress Cloud (devtools)
- daily: Daily (messaging)
- databricks: Databricks (data)
- datadog: Datadog (observability)
- datocms: DatoCMS (data)
- dbt-cloud: dbt Cloud (data)
- deepgram: Deepgram (ai)
- deepl: DeepL (ai)
- deepseek: DeepSeek (ai)
- deno-deploy: Deno Deploy (hosting)
- descope: Descope (auth)
- dialpad: Dialpad (messaging)
- digitalocean: DigitalOcean (cloud)
- discord: Discord (messaging)
- discourse: Discourse (messaging)
- docker-hub: Docker Hub (devtools)
- doppler: Doppler (devtools)
- drata: Drata (auth)
- dreamhost: DreamHost (hosting)
- dropbox: Dropbox (workplace)
- dropbox-sign: Dropbox Sign (workplace)
- duo: Duo Security (auth)
- dynatrace: Dynatrace (observability)
- e2b: E2B (ai)
- easypost: EasyPost (commerce)
- elastic-apm: Elastic Observability (observability)
- elastic-cloud: Elastic Cloud (data)
- elevenlabs: ElevenLabs (ai)
- env0: env0 (devtools)
- equinix: Equinix Metal (cloud)
- exa: Exa (ai)
- expo: Expo (hosting)
- expo-eas: Expo Application Services (devtools)
- fal: fal (ai)
- figma: Figma (workplace)
- filestack: Filestack (hosting)
- firebase: Firebase (data)
- firecrawl: Firecrawl (data)
- fireflies: Fireflies.ai (workplace)
- fireworks: Fireworks AI (ai)
- flagsmith: Flagsmith (devtools)
- fly: Fly.io (hosting)
- framer: Framer (hosting)
- front: Front (messaging)
- frontegg: Frontegg (auth)
- fullstory: FullStory (observability)
- fusionauth: FusionAuth Cloud (auth)
- gamma: Gamma (workplace)
- gcp: Google Cloud (cloud)
- ghost: Ghost(Pro) (hosting)
- gitbook: GitBook (hosting)
- github: GitHub (devtools)
- github-actions: GitHub Actions (devtools)
- github-copilot: GitHub Copilot (ai)
- github-pages: GitHub Pages (hosting)
- gitlab: GitLab (devtools)
- gitpod: Gitpod (devtools)
- gong: Gong (workplace)
- google-play: Google Play Console (devtools)
- google-workspace: Google Workspace (workplace)
- gotomeeting: GoTo (messaging)
- grafana-cloud: Grafana Cloud (observability)
- grafana-oncall: Grafana IRM (observability)
- grammarly: Grammarly (workplace)
- granola: Granola (workplace)
- greenhouse: Greenhouse (workplace)
- groq: Groq (ai)
- growthbook: GrowthBook (devtools)
- gusto: Gusto (workplace)
- harness: Harness (devtools)
- hashicorp-vault: HCP Vault (auth)
- hasura: Hasura Cloud (data)
- heap: Heap (data)
- helicone: Helicone (ai)
- help-scout: Help Scout (workplace)
- heroku: Heroku (hosting)
- hetzner: Hetzner (cloud)
- hex: Hex (data)
- hex-pm: Hex.pm (devtools)
- heygen: HeyGen (ai)
- hightouch: Hightouch (data)
- honeycomb: Honeycomb (observability)
- hookdeck: Hookdeck (devtools)
- hostinger: Hostinger (hosting)
- hotjar: Hotjar (observability)
- hubspot: HubSpot (workplace)
- huggingface: Hugging Face (ai)
- hume: Hume AI (ai)
- hygraph: Hygraph (data)
- imgix: imgix (hosting)
- imperva: Imperva (cloud)
- incident-io: incident.io (observability)
- infisical: Infisical (devtools)
- influxdata: InfluxDB Cloud (data)
- infura: Infura (commerce)
- inngest: Inngest (devtools)
- instatus: Instatus (observability)
- intercom: Intercom (messaging)
- iterable: Iterable (messaging)
- jenkins: CloudBees (devtools)
- jfrog: JFrog (devtools)
- jina: Jina AI (ai)
- jira: Jira (workplace)
- jumpcloud: JumpCloud (auth)
- keeper: Keeper (auth)
- kinde: Kinde (auth)
- kinsta: Kinsta (hosting)
- klarna: Klarna (commerce)
- klaviyo: Klaviyo (messaging)
- knock: Knock (messaging)
- koyeb: Koyeb (hosting)
- kraken: Kraken (commerce)
- lago: Lago (commerce)
- lambda: Lambda Cloud (ai)
- lambdatest: LambdaTest (devtools)
- langfuse: Langfuse (ai)
- langsmith: LangSmith (ai)
- lattice: Lattice (workplace)
- launchdarkly: LaunchDarkly (devtools)
- lever: Lever (workplace)
- lightstep: ServiceNow Cloud Observability (observability)
- linear: Linear (devtools)
- linkedin: LinkedIn (messaging)
- linode: Akamai Cloud (Linode) (cloud)
- liveblocks: Liveblocks (data)
- livekit: LiveKit Cloud (messaging)
- llamaindex: LlamaCloud (ai)
- loggly: Loggly (observability)
- logrocket: LogRocket (observability)
- logzio: Logz.io (observability)
- lokalise: Lokalise (devtools)
- loom: Loom (workplace)
- loops: Loops (messaging)
- lovable: Lovable (ai)
- lucid: Lucid (workplace)
- luma: Luma AI (ai)
- mailersend: MailerSend (messaging)
- mailgun: Mailgun (messaging)
- mailjet: Mailjet (messaging)
- make: Make (workplace)
- mapbox: Mapbox (data)
- marqeta: Marqeta (commerce)
- maven-central: Maven Central (Sonatype) (devtools)
- maxmind: MaxMind (data)
- meilisearch: Meilisearch Cloud (data)
- mercury: Mercury (commerce)
- messagebird: Bird (messaging)
- metabase: Metabase Cloud (data)
- metronome: Metronome (commerce)
- mintlify: Mintlify (hosting)
- miro: Miro (workplace)
- mixpanel: Mixpanel (data)
- modal: Modal (ai)
- modern-treasury: Modern Treasury (commerce)
- monday: monday.com (workplace)
- mongodb-atlas: MongoDB Atlas (data)
- moralis: Moralis (commerce)
- mural: Mural (workplace)
- mux: Mux (hosting)
- neon: Neon (data)
- netlify: Netlify (hosting)
- new-relic: New Relic (observability)
- ngrok: ngrok (devtools)
- nhost: Nhost (data)
- northflank: Northflank (hosting)
- notion: Notion (workplace)
- novu: Novu (messaging)
- npm: npm (devtools)
- octopus: Octopus Deploy (devtools)
- onesignal: OneSignal (messaging)
- openai: OpenAI (ai)
- openrouter: OpenRouter (ai)
- opsgenie: Opsgenie (observability)
- optimizely: Optimizely (devtools)
- oracle-cloud: Oracle Cloud (cloud)
- orb: Orb (commerce)
- otter: Otter.ai (workplace)
- paddle: Paddle (commerce)
- pantheon: Pantheon (hosting)
- paypal: PayPal (commerce)
- percy: Percy (devtools)
- perplexity: Perplexity (ai)
- phrase: Phrase (devtools)
- pinecone: Pinecone (data)
- ping-identity: Ping Identity (auth)
- pinterest: Pinterest (messaging)
- pipedream: Pipedream (devtools)
- plaid: Plaid (commerce)
- planetscale: PlanetScale (data)
- plivo: Plivo (messaging)
- pocketbase: Pocketbase (PocketHost) (data)
- poe: Poe (ai)
- polar: Polar (commerce)
- posthog: PostHog (data)
- postman: Postman (devtools)
- prisma: Prisma Data Platform (data)
- prismic: Prismic (data)
- pulumi: Pulumi Cloud (devtools)
- pusher: Pusher (messaging)
- pylon: Pylon (workplace)
- pypi: PyPI (devtools)
- qdrant: Qdrant Cloud (data)
- quay: Red Hat Quay.io (devtools)
- quip: Quip (workplace)
- radar: Radar (data)
- readme: ReadMe (hosting)
- recurly: Recurly (commerce)
- red-hat: Red Hat (cloud)
- reddit: Reddit (messaging)
- render: Render (hosting)
- replicate: Replicate (ai)
- resend: Resend (messaging)
- retell: Retell AI (ai)
- retool: Retool (workplace)
- revenuecat: RevenueCat (commerce)
- rippling: Rippling (workplace)
- rollbar: Rollbar (observability)
- rootly: Rootly (observability)
- rubygems: RubyGems.org (devtools)
- rudderstack: RudderStack (data)
- runpod: RunPod (ai)
- runway: Runway (ai)
- salesforce: Salesforce (workplace)
- sambanova: SambaNova Cloud (ai)
- sanity: Sanity (data)
- saucelabs: Sauce Labs (devtools)
- scaleway: Scaleway (cloud)
- scrapingbee: ScrapingBee (data)
- secureframe: Secureframe (auth)
- segment: Segment (data)
- sendgrid: SendGrid (messaging)
- sentry: Sentry (observability)
- serpapi: SerpApi (data)
- shippo: Shippo (commerce)
- shopify: Shopify (commerce)
- signoz: SigNoz Cloud (observability)
- sinch: Sinch (messaging)
- singlestore: SingleStore (data)
- slack: Slack (messaging)
- smartling: Smartling (workplace)
- smartsheet: Smartsheet (workplace)
- smithery: Smithery (ai)
- smtp2go: SMTP2GO (messaging)
- snowflake: Snowflake (data)
- snyk: Snyk (devtools)
- socket: Socket (devtools)
- sonarcloud: SonarCloud (devtools)
- sourcegraph: Sourcegraph (devtools)
- sourcehut: SourceHut (devtools)
- spacelift: Spacelift (devtools)
- sparkpost: SparkPost (messaging)
- split: Split (Harness FME) (devtools)
- spotify: Spotify Web API (messaging)
- square: Square (commerce)
- squarespace: Squarespace (hosting)
- stability: Stability AI (ai)
- statsig: Statsig (devtools)
- statuscake: StatusCake (observability)
- statuspage: Atlassian Statuspage (observability)
- stitch: Stitch (data)
- strapi-cloud: Strapi Cloud (data)
- stream: Stream (messaging)
- stripe: Stripe (commerce)
- stytch: Stytch (auth)
- substack: Substack (messaging)
- sumo-logic: Sumo Logic (observability)
- supabase: Supabase (data)
- superhuman: Superhuman (workplace)
- surveymonkey: SurveyMonkey (workplace)
- svix: Svix (devtools)
- tabnine: Tabnine (ai)
- tailscale: Tailscale (auth)
- tally: Tally (workplace)
- tavily: Tavily (ai)
- taxjar: TaxJar (commerce)
- telnyx: Telnyx (messaging)
- temporal-cloud: Temporal Cloud (devtools)
- terraform-cloud: HCP Terraform (devtools)
- todoist: Todoist (workplace)
- together: Together AI (ai)
- travis-ci: Travis CI (devtools)
- trello: Trello (workplace)
- trigger-dev: Trigger.dev (devtools)
- turso: Turso (data)
- twilio: Twilio (messaging)
- twingate: Twingate (auth)
- twitch: Twitch (messaging)
- typeform: Typeform (workplace)
- unit: Unit (commerce)
- uploadcare: Uploadcare (hosting)
- uploadthing: UploadThing (hosting)
- upstash: Upstash (data)
- v0: v0 (ai)
- vanta: Vanta (auth)
- vapi: Vapi (messaging)
- vectara: Vectara (ai)
- vercel: Vercel (hosting)
- vimeo: Vimeo (hosting)
- voyage: Voyage AI (ai)
- wasabi: Wasabi (cloud)
- webex: Webex (messaging)
- webflow: Webflow (hosting)
- windsurf: Windsurf (ai)
- wise: Wise (commerce)
- wistia: Wistia (hosting)
- wix: Wix (hosting)
- workos: WorkOS (auth)
- xai: xAI (ai)
- xata: Xata (data)
- zapier: Zapier (workplace)
- zilliz: Zilliz Cloud (data)
- zoom: Zoom (messaging)