Sponsor Media Kit

Reach engineers who run production

Ship It Weekly is a focused DevOps, SRE, platform and cloud engineering show for people close to infrastructure, reliability, delivery, and cloud operations. It is built around signal, operator trust, and sponsor fit instead of broad consumer reach.

Ship It Weekly podcast cover art

Ship It Weekly

Weekly commentary on incidents, launches, outages, security issues, and production lessons for teams who operate the systems everyone else depends on.

53Published episodes in the current catalog
#1Apple Podcasts (US) for the “SRE” keyword (June 2026)
Top 1%PodSEO visibility ranking across all indexed podcasts (June 2026)
July 2026Most recent release window in the live archive
53Episodes
17.7K+Cumulative downloads June 2026
Top 1%PodSEO visibility June 2026
73%Mobile listening
45%US-based listeners
81%iPhone of phone listens
Trusted by sponsors who’ve run on the show @Scale: Systems & Reliability (Meta) Guardsquare

Recent evidence that supports the sponsor story

Narrow, source-backed snapshots — not permanent claims about ranking, scale, or endorsement.

Hear the show in 30 seconds

Latest episode — a representative sample of the show's current voice and pacing, useful for confirming brand fit before a sponsorship conversation.

Audience fit
DevOps, SRE, platform and cloud engineering
A focused B2B technical audience for infrastructure, reliability, platform, security, and production-minded engineering teams.
Evergreen signal
Cross-platform search visibility
#1 Apple Podcasts and #3 Amazon Music for "SRE"
Ship It Weekly ranks #1 on Apple Podcasts US and #3 on Amazon Music for the "SRE" keyword, with continued visibility on YouTube Music (#8) and Spotify (#16). Top placement on the two platforms where the show indexes strongest for a niche technical keyword.
PodSEO snapshot, June 2026
Apple search: sustained Top 5 for "DevOps"
Top 5 in Apple Podcasts US for "DevOps" since February 2026
Ship It Weekly has held a top-5 Apple Podcasts US position for "DevOps" continuously since February 2026, peaking at #1 in March-April 2026 and ranking #2 as of June 2026.
PodSEO snapshot, June 2026
Spotify search: #2 for "Cloud Provider Incidents"
#2 in Spotify for "Cloud Provider Incidents"
Ship It Weekly ranks #2 on Spotify for the niche keyword "cloud provider incidents," reflecting the show's focus on real-world production incidents and postmortems.
PodSEO snapshot, June 2026
Apple search: top 10 across 7 keywords
Top 10 for SRE, Cloud Platform, DevOps, Tech News Weekly, Cloud News, Dev, Platform Engineering
Ship It Weekly ranks in the Apple Podcasts US top 10 for seven tracked keywords: #1 SRE, #2 Cloud Platform, #2 DevOps, #4 Tech News Weekly, #7 Cloud News, #7 Dev, and #8 Platform Engineering.
PodSEO snapshot, June 2026
Apple Tech News chart signal
Top 10 in US Tech News, later reaching #2
Ship It Weekly reached the Apple Podcasts US Tech News Top 10 on Dec 28, 2025, and later hit #2 again in January 2026, based on captured chart milestones and show updates.
Reached Top 10 Dec 28, 2025; #2 again Jan 10, 2026
Catalog reach and recent traction
Over 17,500 downloads in six months; 334+ per episode and climbing
In just over six months, the catalog has totaled 17,690 downloads across 53 published episodes — averaging roughly 334 downloads per episode and still climbing. Recent releases consistently reach 300+ downloads within their first 2-3 weeks of publication.
RSS.com analytics, June 2026
What the price actually buys

Framed per qualified listener, not as raw CPM

Raw effective CPM on a niche B2B technical podcast is mathematically high because the audience is filtered narrow on purpose. The number that matches the buying decision is cost per qualified listener — what does each senior DevOps, SRE, or platform engineer reached actually cost?

Cost per qualified listener
$2.50
$750 for a single-episode placement reaches 300+ downloads inside the first 30-day campaign window — about $2.50 per qualified listener — and continues to accumulate as the episode evergreens. The audience is already filtered by topic, technical seniority, and self-selection, so each download is a senior DevOps, SRE, platform, or cloud-engineering decision-maker rather than a broad consumer impression.
First 30-day campaign window
Host-read trust uplift
Peer recommendation, not banner ad
Industry benchmarks (IAB / PwC Podcast Advertising Revenue Study) put general-podcast CPMs around $15–30 and B2B / technical-vertical CPMs at $30–80+, where host-read placement consistently outperforms produced spots on brand recall and purchase intent. Equivalent reach via display channels lands at $0.02–0.08 per impression (roughly $20–80 CPM for B2B technical podcasts on AdvertiseCast / IAB benchmarks; $30–50 CPM for senior-engineer-targeted LinkedIn Sponsored Content) — but the unit is an unqualified scrolling impression, not a host-read endorsement to a vetted decision-maker.
Endorsement, not impressions
Evergreen value
Placements keep working past launch week
Episode pages, show notes, search visibility, and the YouTube companion keep delivering listens and click-throughs months after the drop date. Sponsorship copy compounds across the catalog rather than expiring when a campaign budget runs out, which is the opposite shape of paid social impressions.
Discoverable after release

Benchmark CPM ranges are drawn from the IAB / PwC Podcast Advertising Revenue Study and publicly reported marketplace pricing (AdvertiseCast). Per-listener and per-episode numbers above are derived live from the catalog so they stay in step with the rate card and recent reach.

Methodology note: search ranking data is from PodSEO keyword tracking (June 2026 snapshots), spanning Apple Podcasts, Spotify, Amazon Music, and YouTube Music. The visibility-ranking percentile reflects PodSEO's combined score across all tracked podcasts. Chart positions are from captured Apple Podcasts milestones. Listener benchmarks are from RSS.com analytics. Full current sponsorship metrics can be shared directly in conversation.
PodSEO contributing factors (June 2026)
Charts
6.1/10

Apple Podcasts chart positions and category visibility.

Search
7.4/10

Keyword rankings across Apple Podcasts, Spotify, Amazon Music, and YouTube Music.

Editorial
3.4/10

Curated platform features and editorial spotlights. Lower because the show is independent and earns visibility through content rather than platform features.

Built for signal, trust, and relevance

Not mass-market scale — trusted access to working engineers and technical leaders who care about production systems.

Operator trust

The show is hosted from a working-practitioner perspective, which makes sponsor messages land closer to peer recommendation than generic ad inventory.

Category relevance

Ship It Weekly is built for DevOps, SRE, platform and cloud engineering, infrastructure, and security-adjacent teams rather than broad consumer tech audiences.

Discovery beyond release day

Episodes, show pages, search presence, and clips keep working after the initial drop, which helps sponsors stay discoverable beyond one listen.

Multi-surface presence

Sponsors can show up across audio, video, website placement, episode pages, email episode alerts, and the broader Teller's Tech / On Call Brief ecosystem.

On Call Brief co-promotion

Every episode sponsor automatically gets a “Sponsored by” credit — a small byline in that week's On Call Brief email and on the brief page — putting your brand in front of the newsletter audience at no extra cost. A full, dedicated ad placement inside a brief is available as a paid add-on.

Episode-alert email

When a new episode drops, subscribers get a Ship It Weekly episode-alert email — and the sponsor's “Sponsored by” line rides along in it, adding a direct-inbox touchpoint alongside the audio and web placements at no extra cost.

Who this show is actually for

Intentionally narrow — technical practitioners, reliability-minded teams, and people who influence what gets adopted in engineering orgs.

Estimated age signal

Directional audience data suggests the core listener base skews toward ages 25–44, which aligns well with working engineers and technical decision influencers.

Directional, not audited

Estimated gender mix

Directional podcast-audience tooling suggests a mix around 60% male and 40% female, which is more balanced than many technical media properties.

Estimated from third-party tooling

Regional concentration

Recent analytics and directional tools point to North America and Europe as the strongest listening regions for the show.

Recent snapshot

Recurring audience signal

Directional third-party audience data suggests recurring reach among technical listeners, supporting the show’s consistency with a niche B2B engineering audience.

Directional third-party estimate

What the audience actually shows up for

Topics across the published catalog, ranked by how often each area is covered. Higher coverage signals deeper editorial fit for sponsors selling into that category.

AI & agents 47 eps
GitHub 40 eps
CI\/CD & GitOps 35 eps
AWS & cloud providers 34 eps
Kubernetes 24 eps
Incidents & postmortems 23 eps
Security & CVEs 22 eps
Episode appearances per topic

Weekly cadence, proven over six months

Each dot is one calendar week (Sunday–Saturday) since launch on November 20, 2025 — the show's actual run, week by week. Filled dots mark weeks where a regular episode shipped: visible, measurable consistency rather than a promise. Darker dots mark weeks with more than one release. Empty dots are weeks where no regular episode shipped — visible rather than smoothed over.

34/35 weeks shipped (97% of the window)

Episode shipped in 34 of 35 weeks. 19 of those weeks had more than one release.

Launch week This week
One episode Multiple episodes No episode

Methodology: a calendar week reads as filled when any regular episode shipped during it, including Ship It Conversations releases; darker dots are weeks with two or more releases. Calendar weeks run Sunday to Saturday; trailers and specials excluded.

Where each covered topic sits on the engineering map

Bubble size is real coverage — the count of episodes touching that topic. Position is a qualitative read: how fast-moving the topic is (X) and how operationally heavy it is in production (Y).

Adoption maturity → ↑ Operational depth 47 AI & agents 40 GitHub 34 AWS & cloud providers 24 Kubernetes 23 Incidents & postmortems 22 Security & CVEs 16 Conversations & interviews
Bubble size = episodes covering that topic Position = qualitative engineering-map read

One sponsor message, multiple touchpoints

A single sponsorship doesn't sit alone on the audio feed. The same message rides through video, episode-page web copy, social cutdowns, the Ship It Weekly episode-alert email, and the On Call Brief newsletter — reinforcing in places the audience already trusts.

Sponsor campaign Episode email "Sponsored by" line, every episode Audio Host-read placement Video YouTube companion Web Episode page + notes Clips Social cutdowns On Call Brief "Sponsored by" credit in the newsletter
Sponsor campaign hub Reinforcement surface

DevOps and platform engineers

Operators looking for signal on CI/CD, cloud infrastructure, incidents, developer platforms, and the tooling choices that matter in production.

SRE and reliability-minded teams

Listeners who care about outages, operational lessons, resilience patterns, and the tradeoffs that show up once real systems are under load.

Technical decision influencers

Senior ICs, architects, and engineering leaders who evaluate tools, influence standards, and help shape what gets adopted across a team.

Security-conscious builders

The audience consistently overlaps with cloud security, software supply chain, identity, and platform-risk conversations rather than generic consumer tech.

Recent conversations on the show

Practitioners who have actually shipped

The show regularly hosts guests who run production, lead platform teams, or build the tools sponsors sell into. A campaign here lands next to real operator voices, not a generic interview funnel.

Where the audience actually listens

Snapshot from RSS.com analytics, June 2026 — the recent monthly window of direct downloads, running at roughly 3,000 downloads a month. That recent pace is what built the cumulative-since-launch total (17,690 downloads in just over six months, 334+ per episode) surfaced in the proof section above.

Top countries

Share of recent downloads by listener country.

United States 44.7%
United Kingdom 6.1%
Australia 4.1%
Germany 3.7%
Brazil 2.7%
France 2.4%
Sweden 2.0%
India 1.9%
Switzerland 1.7%
Bangladesh 1.4%

Plus 19+ more countries with recurring downloads. North America and Europe together are roughly 80% of the listener base.

Device & platform mix

How the audience consumes the show.

73%mobile listening

Among phone listeners specifically, 81% are on iPhone — a strong indicator of senior-engineer / premium-device skew typical of US, UK, and EU technical audiences.

Mobile 72.6%
Computer 26.8%
Smartwatch 0.6%

Smartwatch listening (1%+) is a small but growing surface that suggests in-context, on-the-go consumption during work commutes and incidents.

Top listening apps

Where podcast-app listens come from.

Apple Podcasts 38.6%
Overcast 37.5%
Podcast Addict 10.2%
Pocket Casts 7.2%
Spotify (direct download) 3.5%
AntennaPod 1.9%
Podcast Republic 1.1%

Overcast running neck-and-neck with Apple Podcasts is a recognizable engineering-audience signal — Overcast is the power-user choice for technical listeners. Spotify and YouTube Music in-app plays are counted on those platforms separately, and browser / web-player direct downloads are excluded here, so the mix reflects dedicated podcast apps.

Beyond the podcast feed

Owned-media reach

A campaign on Ship It Weekly can be amplified through adjacent owned channels where the same engineering audience already follows the show.

More than a single host-read slot

Strongest when a sponsor message appears where technical buyers already spend attention: the show, the video companion, episode pages, and owned-media surfaces.

Core surface

Audio podcast

Host-read placement in the core weekly show for engineers who want concise signal on production systems and platform tooling.

Visual surface

Video episode

YouTube and companion video placement creates an additional sponsor surface for visual branding, links, and repeated exposure.

Discoverable

Owned web presence

Episode pages, sponsor-aligned landing pages, and searchable site content keep sponsor messaging tied to discoverable technical content.

Direct inbox

Email episode alerts

Subscribers get a Ship It Weekly email when each episode drops, and the sponsor line rides along — a direct-inbox touchpoint beyond audio and web.

Expandable

Extended ecosystem

Short-form clips, LinkedIn-friendly amplification, and the adjacent On Call Brief property give the right sponsor more than one context to appear in.

Representative placement

See sponsorship in context

A representative example from a live episode — Episode 41 (May 2026) shows exactly where a sponsor lands. Guardsquare gets a card directly above the fold next to the listen CTAs, plus a click-through inline mention inside the show notes. Every regular episode follows the same pattern, including the most recent.

Above-the-fold sponsor card on Ship It Weekly Episode 41 — a 'Sponsored by Guardsquare' pill renders directly under the Watch Video / Apple / Spotify / Download listen buttons, above the episode summary
1. Above the fold — sponsor pill sits next to the listen CTAs, visible to every visitor before they scroll.
In-show-notes sponsor mention on Ship It Weekly Episode 41 — a 'Sponsored by Guardsquare' line with a click-through hubs.ly URL appears at the top of the show-notes link list, before the topic-by-topic resource links
2. In show notes — inline "Sponsored by Guardsquare" line with a click-through link, surfaced before the topic resources.

Plus a host-read mention woven into the episode itself — typically 30–60 seconds, delivered in-segment so it lands as part of the show rather than as a cut-away ad break.

Episode 41: CISA's GitHub leak, AI root-cause analysis, Copilot agents, Claude Code in CI/CD, and Kubernetes seccomp risk. View the live episode page →

What the show is covering right now

Sponsor alignment stays tied to live engineering conversations — incidents, launches, security stories, platform tradeoffs — not generic tech news.

EKS Rollbacks, GitHub Actions Supply Chain Attacks, AI Agentjacking, CloudWatch Log Alarms, and Why Safety Nets Don’t Replace Ownership

This week on Ship It Weekly: Amazon EKS added Kubernetes version rollbacks, Novee Security published Cordyceps research on GitHub Actions supply chain risk, Tenet Security showed how fake telemetry can hijack AI coding agents,…

Ship It Conversations: Evan Phoenix of Miren on Deployment Pain, Terraform, Waypoint, and Better Defaults for Small Teams

This is a guest conversation episode of Ship It Weekly, separate from the weekly news recaps.In this Ship It: Conversations episode, I talk with Evan Phoenix of Miren about why deployment is still painful,…

Amazon Q CVEs, Hijacked npm and Go Packages, AWS WAF HTTP/2 Issues, Lambda MicroVMs, and Why Execution Is the Boundary Now

This week on Ship It Weekly: Amazon Q Developer and the AWS language servers had a pair of trust-boundary CVEs, JFrog found hijacked npm and Go packages using hidden VS Code tasks to run…

Ship It Conversations: Kat Traxler of Vectra AI on AI Security, the Zero-Day Clock, IAM, and Cloud Risk

This is a guest conversation episode of Ship It Weekly, separate from the weekly news recaps.In this Ship It: Conversations episode, I talk with Kat Traxler of Vectra AI about AI security, the zero-day…

containerd CRI Vulnerabilities, Datadog PostgreSQL HA on Kubernetes, AWS DevOps Agent with Datadog MCP Server, EKS Control Plane Egress, and Why Users Feel the Wait

This week on Ship It Weekly: containerd disclosed a batch of CRI plugin vulnerabilities, Datadog tested PostgreSQL high availability on Kubernetes and found that failover is not useful if it cannot happen safely, AWS…

Ship It Conversations: Guardsquare’s Joel DeStefano on Mobile App Security, Runtime Protection, App Hardening, and Why Scanning Isn’t Enough

This is a guest conversation episode of Ship It Weekly, separate from the weekly news recaps.In this Ship It: Conversations episode, I talk with Joel DeStefano from Guardsquare about mobile app security, why it…

The show also publishes supporting updates through show-news posts and owned web surfaces, which helps sponsor-aligned content stay discoverable outside the main episode feed.

Topic coverage across the catalog

How often each area gets coverage

Counts are episode appearances across every published episode (titles and show notes). Most episodes touch multiple areas, so totals overlap.

AI & agents47 GitHub40 CI\/CD & GitOps35 AWS & cloud providers34 Kubernetes24 Incidents & postmortems23 Security & CVEs22 Conversations & interviews16 Cloudflare11

Great for technical vendors. Not generic consumer ads.

Strongest fit: product categories an infrastructure, reliability, security, or platform team would actually evaluate or trial in production.

Best-fit categories

Cloud security Observability and incident response Developer platforms and internal tooling Platform engineering and infrastructure tooling CI/CD and automation Kubernetes and container platforms Identity, access, secrets, and policy Software supply chain and DevSecOps Cloud cost and FinOps

Why that matters

Ship It Weekly works best as high-trust technical inventory. The value is relevance, repeat exposure, and credibility with teams evaluating real infrastructure decisions.

  • Better fit than broad, low-intent reach.
  • Strongest when the sponsor solves a real problem for technical teams.

Single episode placement

Best for launches, experiments, or a first campaign with concise sponsor messaging across the episode and companion surfaces.

Multi-episode campaign

Better for recall, trust, and repetition. Technical audiences usually need to hear a message more than once before it sticks.

Custom ecosystem package

For strong sponsor fit, campaigns can pair podcast placement with video, site visibility, and adjacent owned-media touchpoints.

Public card rates for campaign planning

Rates set expectations for strong-fit technical sponsors. Multi-episode campaigns are preferred — repetition matters with engineering audiences.

Single $750
6-episode $3,300
What you get Single episode $750 Most chosen3-episode campaign $1,950 6-episode campaign $3,300
Host-read audio placement 1 episode 6 episodes
YouTube video companion
Episode show-notes mention
Episode page card on the web
Per-episode brand exclusivity
Episode-alert email "Sponsored by" credit
On Call Brief "Sponsored by" credit
Dedicated ad placement in an On Call Brief 1 included
Sponsor-supplied creative ok
Evergreen placement (no roll-off)

The On Call Brief “Sponsored by” credit is a small automatic byline in the weekly brief and its email (included on every tier). A dedicated ad placement is a full sponsor slot inside a brief issue — an optional add-on on the 3-episode tier, with one included on the 6-episode tier.

Custom packages are available on request and typically pair audio with video, web visibility, and On Call Brief placements. Talk through a fit on the sponsorship contact form.

Inventory is limited by design. Only one sponsor rides each episode, so slots are genuinely finite — if you have target dates or a launch to line up against, share them early and we’ll try to hold the window.

Selective sponsor fit

The goal is strong alignment with infrastructure, security, developer platform, and reliability products rather than generic creator-ad inventory.

Technical credibility matters

Sponsor messaging should sound like it belongs in an engineering conversation, with clear relevance to production systems and operational work.

Evergreen visibility beats hype

The show aims for repeated exposure through episodes, video, and owned web surfaces instead of one short-lived vanity spike.

Recent snapshots, not stale bragging

Public proof points should be recent, dated, and source-backed. Fuller current numbers, examples, and package details can be shared directly during sponsorship conversations.

Creative specs & timeline

Everything you need to brief your team and plan a launch window — no back-and-forth required.

Ad format Host-read, woven in-segment Typically 30–60 seconds, delivered as part of the show rather than a cut-away ad break.
Creative You supply talking points or a script Default is sponsor talking points read in the host's voice; a fully written script also works.
Approval You review before recording The planned read is shared for sign-off so messaging stays accurate.
Lead time ~3–4 weeks to first live episode From signed agreement through copy review and the next production cycle. Tightly scoped reads can move faster.
Exclusivity One sponsor per episode Per-episode brand exclusivity is included by default — you never share a read with a competitor.
Shelf life Evergreen — never rolls off The read stays embedded permanently; back-catalog plays keep delivering exposure for months.

Trusted because it sounds like it comes from someone who has been there

Brian Teller

Brian Teller

Brian is the host of Ship It Weekly and the builder behind Teller's Tech, a media and training platform focused on DevOps, SRE, platform engineering, cloud infrastructure, and the real-world work of keeping production systems alive.

Brian started Ship It Weekly because most tech news says what happened—but not always why it matters to the people on-call when the headline becomes their incident.

DevOps Institute Ambassador ITIL Ambassador

Sponsor questions, answered

What kinds of sponsors fit best?

The strongest fit is B2B technical vendors in cloud, infrastructure, observability, platform engineering, security, CI/CD, and adjacent categories that solve real problems for production teams.

Do you offer custom packages?

Yes. The best campaigns are usually tailored around the sponsor's product, target audience, and whether the goal is awareness, launch visibility, or repeated presence across multiple episodes.

What's the typical lead time?

Plan on roughly three to four weeks from signed agreement to the first live episode. That covers package alignment, ad copy or talking-point review, recording into the next episode's production cycle, and publication. Faster turnarounds are sometimes possible for tightly scoped reads.

Can I provide my own ad copy, or is it host-read?

Both work. The default is a host-read placement built from sponsor-supplied talking points so the read sounds native to the show. Sponsors can also provide a fully written script. Either way, the sponsor reviews the planned read before recording so messaging stays accurate.

Do you offer per-episode sponsor exclusivity?

Yes — per-episode exclusivity is included by default. Only one main sponsor read per episode, so a sponsor never shares an episode with another brand.

Is the YouTube version of the show included?

Yes. The audio sponsor read is included automatically in the YouTube companion at no extra cost. Video-specific creative (lower thirds, on-screen graphics, custom cuts) can be quoted separately when the sponsor wants a richer visual presence.

Are sponsor placements evergreen, or do they roll off after a window?

Yes, every host-read placement is evergreen. The sponsor read stays embedded in the episode permanently, so the long tail keeps delivering exposure long after the campaign window. Several catalog episodes are still earning hundreds of additional downloads months after publication, which means a sponsor read continues to surface in searches, recommendations, and back-catalog plays well beyond the initial release week.

Do you do affiliate or performance deals?

Yes, with tracked URLs or promo codes when the product supports them. The default model is sponsorship rather than performance, but performance arrangements are workable for the right fit, particularly with multi-episode commitments.

Why are there no stale download charts here?

This page prioritizes evergreen fit and carefully labeled proof points over vanity metrics that drift quickly. Where we do show time-sensitive data, it is framed as a recent snapshot rather than a permanent claim.

Can sponsors review copy or talking points?

Yes. The goal is a sponsor message that feels technically credible and aligned with the audience, not a generic script dropped into an engineering show.

Interested in sponsoring Ship It Weekly?

If your product serves DevOps, SRE, platform, infrastructure, or security-conscious engineering teams, we can shape a campaign that feels technically credible, aligned with the audience, and backed by current metrics shared in context.

Prefer email? Reach us directly at tellerstech@gmail.com.

1. Reach outWe reply with fit and next-step guidance, typically within 48 hours.
2. Review fitWe share current package options and availability. Plan for about one week to align on package, exclusivity, and creative.
3. Go liveWe align on messaging, timing, and go-live details. Typical lead time from signed agreement to first live episode is three to four weeks.
Talk sponsorship
Scroll to Top