Sponsorbook
FFireship channel photoYouTube creator

Fireship
& the brands behind the videos.

Fireship’s short technology videos give sponsors room for a compact problem-and-tool explanation. In these examples, Blacksmith is introduced as part of building software with GitHub Actions, while Hyperagent is connected to a custom research agent used for a newsletter. Both reads name a specific workflow instead of relying on a generic developer-tool pitch. The useful starting point is the task itself: running a build or gathering material for a newsletter.

Blacksmith · Did Anthropic just kill the indie hacker...?▶ Watch integration
BBlacksmith logo

Fireship × Blacksmith

Did Anthropic just kill the indie hacker...?

BRANDS IN THE VIDEOS

BBrilliant logoBrilliant
ddaily.dev
HHostinger logoHostinger
CClerk logoClerk
10
Sponsored videos
Sep 2025 – Aug 2026
37
Sponsor brands
All-time tracked
12
Returning sponsors
All-time tracked

The repeat partnerships

Brilliant leads the sponsor relationships shown here, with 26 sponsored videos. daily.dev follows with 10.

12 of 37 brands (32%) appear in more than one sponsored video in Sponsorbook’s history of Fireship.

Most frequent sponsorsSponsored videos · All-time tracked
  1. 01
    Brilliant26
  2. 02
    daily.dev10
  3. 03
    Hostinger9
  4. 04
    Clerk7
  5. 05
    Blacksmith4

Fireship sponsor reads explain developer tools through concrete workflows

The brands, creative choices and product connections worth paying attention to.

What makes the integration useful to developers?

The Blacksmith read begins with the creator’s work of building things and introduces the service as a replacement for GitHub-hosted runners. The host explains the stated CI workflow, calls out observability for investigating pipeline behavior, and gives a signup call to action. This structure is efficient for a developer audience: identify where the tool fits, state the job it handles, then give a reason to explore it. For a brief, a specific build step or pipeline problem gives the host a stronger opening than a broad claim about developer productivity.

Hyperagent is shown through a custom research agent called Mr. Bittens. The creator describes it reviewing previous newsletter issues, finding topics in public tech sources, posting selected ideas to team Slack and learning from corrections. That concrete application makes the platform more understandable than a feature list. The read also describes agent access to tools, which should be scoped carefully in any proposed demo.

How does the channel keep sponsor copy concise?

Both segments follow the video’s fast-paced commentary, then close with the creator’s familiar sign-off. A good brief should fit that pace: one developer task, one product feature that helps perform it and a direct next step. A build pipeline gives an infrastructure tool a practical setting. A research workflow does the same for an agent product. That specificity helps the read earn its place in a short video.

See the integrations

Watch how the product becomes part of the video.

2 examples · Jump straight to the read
OpenAI gets sued for stealing, again… Sponsor at 4:02
Hyperagent17 Jul 2026

OpenAI gets sued for stealing, again…

The creator demonstrates a Hyperagent research workflow that collects topics, posts them to team Slack and incorporates corrections. It is a specific custom-agent story, not evidence that every agent works autonomously or has unrestricted access.

Find your next partnership.

Explore sponsorship histories, discover who works with whom, and build a shortlist in Sponsorbook.

Explore Sponsorbook ↗