Buildkite

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

Yes. Buildkite requires an API key from your Buildkite 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 Buildkite, GitHub, Notion, Stripe, and the rest. Trigger Buildkite from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for continuous integration platform for running scalable pipelines and software build automation. Common builds include sync jobs, admin tooling, and agents that call Buildkite APIs from your backend. Local DB entities let you query synced Buildkite 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 Buildkite 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/buildkite in the open repo. When Buildkite 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 Buildkite data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Buildkite data on your behalf.