Docker Hub

Install corsair and @corsair-dev/dockerhub, add the Docker Hub plugin, and connect with an API key. Then call methods like corsair.dockerhub.api.images.get() from your app. Corsair syncs data per tenant.

Yes. Docker Hub requires an API key from your Docker Hub account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.

Yes. One Corsair client can hit Docker Hub, GitHub, Notion, Stripe, and the rest. Trigger Docker Hub from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for container registry for storing, sharing, and distributing docker images and repositories. Common builds include sync jobs, admin tooling, and agents that call Docker Hub APIs from your backend. Local DB entities let you query synced Docker Hub records without hitting the API on every read.

The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per Docker Hub API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.

We maintain @corsair-dev/dockerhub in the open repo. When Docker Hub ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.

No. Corsair does not read your Docker Hub data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Docker Hub data on your behalf.