> Godmode v0.19.2 documentation · Reviewed 2026-11-17
> Source: https://godmode.build/docs/v0.19.2/providers

# Provider catalog

Connect the services your product needs for code, hosting, payments, research, or distribution.

## Choose a provider

Start with your product's next task, then open the matching guide. You only need the providers you use.

- [GitHub](/docs/v0.19.2/provider-github): Keep your product's code, issues, and release workflows in one place.
- [Cloudflare](/docs/v0.19.2/provider-cloudflare): Put your product online with hosting, data storage, and domain settings.
- [Vercel](/docs/v0.19.2/provider-vercel): Deploy your web app and manage its domains and project settings.
- [Supabase](/docs/v0.19.2/provider-supabase): Manage the database and sign-in services behind your app.
- [Stripe](/docs/v0.19.2/provider-stripe): Add payments to your product and test the checkout before going live.
- [PostHog](/docs/v0.19.2/provider-posthog): Understand how people use your product and manage feature flags.
- [Notion](/docs/v0.19.2/provider-notion): Keep product plans, research, and operating notes in pages your agent can update.
- [Gmail](/docs/v0.19.2/provider-gmail): Read and send product-related email through a mailbox you choose.
- [Google](/docs/v0.19.2/provider-google): Research search terms and track how people find your site in Google Search.
- [Higgsfield](/docs/v0.19.2/provider-higgsfield): Create images and videos for your product and its marketing.
- [Zernio](/docs/v0.19.2/provider-zernio): Publish product updates through your connected social accounts.
- [Prodigi](/docs/v0.19.2/provider-prodigi): Order and ship printed products for your customers.

## Open setup

Read the required credentials before entering a key. For example, to connect Cloudflare:

```sh
godmode provider cloudflare
godmode setup cloudflare
```

`provider` prints the local guide. `setup` opens key entry. If the provider's own tool already has a working login, you can keep using it. See [Credentials and native logins](/docs/v0.19.2/credentials).

## Check access

Confirm the intended account and resource before your agent changes them.

1. Review the guide's access scope; some bundled setups request broad permissions.
2. Select the account and project, then check access with a read.
3. Pass only the required credentials and verify the result of the authorized change.

A saved key still needs an access check. It does not authorize purchases, publication, or deletion.

## Catalog source

Use the source catalog and official links to resolve differences in a provider's current setup.

The guides use the catalog bundled with CLI v0.19.2, reviewed against public documentation on November 13, 2026. That review did not test signed-in account access.

[Download the catalog JSON](/docs/v0.19.2/providers.json).
