<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <id>https://sengi.run/feed.xml</id>
  <title>Sengi blog</title>
  <link rel="self" href="https://sengi.run/feed.xml" type="application/atom+xml" />
  <link rel="alternate" href="https://sengi.run/" />
  <link rel="hub" href="https://pubsubhubbub.appspot.com/" />
  <author>
    <name>Sengi</name>
  </author>
  <updated>2026-10-27T00:00:00Z</updated>
  <entry>
    <id>https://sengi.run/blog/github-actions-agentic-coding-revenue</id>
    <link rel="alternate" href="https://sengi.run/blog/github-actions-agentic-coding-revenue" />
    <title>How much is agentic coding making GitHub in Actions dollars?</title>
    <summary>Our modelled estimate, checked October 27, 2026: AI coding agents drive about $9 million to $14 million a month of GitHub Actions billing, up from about $2.2 million before Claude Opus 4.5. The formula, every input and its source.</summary>
    <published>2026-10-27T00:00:00Z</published>
    <updated>2026-10-27T00:00:00Z</updated>
  </entry>
  <entry>
    <id>https://sengi.run/blog/claude-code-github-actions</id>
    <link rel="alternate" href="https://sengi.run/blog/claude-code-github-actions" />
    <title>Claude Code GitHub Actions on Sengi: run @claude at half the runner price</title>
    <summary>Run claude-code-action and codex-action on Sengi with one runs-on line: $0.003 a minute at 2 vCPU against GitHub's $0.006. Copy-paste workflows for @claude, PR review and Codex, the cost at 2, 4 and 8 vCPU, and the partner rate. October 2026.</summary>
    <published>2026-10-27T00:00:00Z</published>
    <updated>2026-10-27T00:00:00Z</updated>
  </entry>
  <entry>
    <id>https://sengi.run/blog/ai-coding-agents-github-actions-bill</id>
    <link rel="alternate" href="https://sengi.run/blog/ai-coding-agents-github-actions-bill" />
    <title>AI agents wrote 12× more PRs. Here is how to cut the CI bill in half</title>
    <summary>One agent-heavy repository went from 224 pull requests in May 2026 to 2,682 in the first 26 days of October: about 370,650 CI minutes, $2,224 at GitHub's 2 vCPU price, $1,112 on Sengi and $667 at the Sengi partner rate. What we changed, measured.</summary>
    <published>2026-10-27T00:00:00Z</published>
    <updated>2026-10-27T00:00:00Z</updated>
  </entry>
  <entry>
    <id>https://sengi.run/blog/speed-up-docker-builds-github-actions</id>
    <link rel="alternate" href="https://sengi.run/blog/speed-up-docker-builds-github-actions" />
    <title>Slow Docker builds in GitHub Actions: causes and fixes</title>
    <summary>Why Docker builds are slow in GitHub Actions and how to fix them: type=gha layer caching, mode=max, Dockerfile order, .dockerignore, and a runner that builds Docker images 1.9× faster than GitHub's at 74% less per build.</summary>
    <published>2026-10-23T00:00:00Z</published>
    <updated>2026-10-23T00:00:00Z</updated>
  </entry>
  <entry>
    <id>https://sengi.run/blog/github-self-hosted-runner-alternative</id>
    <link rel="alternate" href="https://sengi.run/blog/github-self-hosted-runner-alternative" />
    <title>GitHub self-hosted runner alternative: managed runners vs running your own</title>
    <summary>The alternative to self-hosted GitHub Actions runners: managed runners that keep your workflows in GitHub with no fleet to patch. Cost at 12,000, 50,000 and 200,000 minutes, Actions Runner Controller, and 5 GHz bare metal from $0.003 a minute.</summary>
    <published>2026-10-23T00:00:00Z</published>
    <updated>2026-10-23T00:00:00Z</updated>
  </entry>
  <entry>
    <id>https://sengi.run/blog/github-larger-runners</id>
    <link rel="alternate" href="https://sengi.run/blog/github-larger-runners" />
    <title>GitHub larger runners: pricing, specs and who can use them</title>
    <summary>GitHub larger runners, checked October 23, 2026: every Linux size's cores, memory, SSD and price per minute, who can use them, why included minutes never apply, and the 4 and 8 vCPU alternative at half the price.</summary>
    <published>2026-10-23T00:00:00Z</published>
    <updated>2026-10-23T00:00:00Z</updated>
  </entry>
  <entry>
    <id>https://sengi.run/blog/github-actions-runner-specs</id>
    <link rel="alternate" href="https://sengi.run/blog/github-actions-runner-specs" />
    <title>GitHub Actions runner specs: CPU, memory and disk for every hosted runner</title>
    <summary>GitHub Actions runner specs, checked October 23, 2026: ubuntu-latest is 2 vCPU, 8 GB and a 14 GB SSD on private repositories and 4 vCPU, 16 GB on public ones. Every hosted and larger runner, the CPU question, and 5 GHz runners from $0.003 a minute.</summary>
    <published>2026-10-23T00:00:00Z</published>
    <updated>2026-10-23T00:00:00Z</updated>
  </entry>
  <entry>
    <id>https://sengi.run/blog/faster-github-actions-runners</id>
    <link rel="alternate" href="https://sengi.run/blog/faster-github-actions-runners" />
    <title>Faster GitHub Actions runners: what makes a runner fast, measured</title>
    <summary>Faster GitHub Actions runners: what makes a runner fast, and Sengi's measured numbers against GitHub's runner of the same size. Up to 3× the multi-core CPU, 15× the random-read disk speed, Docker builds 1.9× faster, for up to 74% less per build.</summary>
    <published>2026-10-23T00:00:00Z</published>
    <updated>2026-10-23T00:00:00Z</updated>
  </entry>
  <entry>
    <id>https://sengi.run/blog/speed-up-github-actions</id>
    <link rel="alternate" href="https://sengi.run/blog/speed-up-github-actions" />
    <title>How to speed up GitHub Actions: find and fix slow CI</title>
    <summary>Speed up GitHub Actions by finding the critical path, fixing cache misses, avoiding duplicate work and choosing the right runner size.</summary>
    <published>2026-09-21T00:00:00Z</published>
    <updated>2026-09-21T00:00:00Z</updated>
  </entry>
  <entry>
    <id>https://sengi.run/blog/github-actions-jobs-stuck</id>
    <link rel="alternate" href="https://sengi.run/blog/github-actions-jobs-stuck" />
    <title>GitHub Actions stuck waiting for a runner: diagnose and fix it</title>
    <summary>GitHub Actions stuck waiting for a runner? Check runner labels, availability, dependencies, concurrency and approvals, then verify the fix.</summary>
    <published>2026-09-21T00:00:00Z</published>
    <updated>2026-09-21T00:00:00Z</updated>
  </entry>
  <entry>
    <id>https://sengi.run/blog/self-hosted-github-actions-runner-cost</id>
    <link rel="alternate" href="https://sengi.run/blog/self-hosted-github-actions-runner-cost" />
    <title>What a self-hosted GitHub Actions runner really costs</title>
    <summary>Self-hosted runner pricing is not zero: machines, idle capacity, ops time, patching and the postponed platform charge, worked through at three volumes against GitHub-hosted runners.</summary>
    <published>2026-09-13T00:00:00Z</published>
    <updated>2026-09-21T00:00:00Z</updated>
  </entry>
  <entry>
    <id>https://sengi.run/blog/github-actions-pricing</id>
    <link rel="alternate" href="https://sengi.run/blog/github-actions-pricing" />
    <title>GitHub Actions pricing in 2026: runner rates, included minutes, and what a month costs</title>
    <summary>GitHub Actions pricing, checked September 21, 2026: every hosted runner's per-minute rate, included minutes by plan, worked monthly examples, and a calculator.</summary>
    <published>2026-09-13T00:00:00Z</published>
    <updated>2026-09-21T00:00:00Z</updated>
  </entry>
  <entry>
    <id>https://sengi.run/blog/reduce-github-actions-costs</id>
    <link rel="alternate" href="https://sengi.run/blog/reduce-github-actions-costs" />
    <title>How to reduce GitHub Actions costs: the checklist</title>
    <summary>Nine dated ways to cut a GitHub Actions bill, checked September 13, 2026: the YAML for each, the mechanism, the worked saving in minutes and dollars, and the risk.</summary>
    <published>2026-09-13T00:00:00Z</published>
    <updated>2026-09-13T00:00:00Z</updated>
  </entry>
  <entry>
    <id>https://sengi.run/blog/github-actions-runner-options-cost</id>
    <link rel="alternate" href="https://sengi.run/blog/github-actions-runner-options-cost" />
    <title>Cheaper GitHub Actions runners: hosted, self-hosted and third-party compared</title>
    <summary>GitHub Actions runner options compared, checked September 13, 2026: per-minute rates, minimum commitment, ops burden and what stays in GitHub across GitHub-hosted, self-hosted and hosted third-party runners, worked at 12,000, 50,000 and 200,000 minutes a month.</summary>
    <published>2026-09-13T00:00:00Z</published>
    <updated>2026-09-13T00:00:00Z</updated>
  </entry>
  <entry>
    <id>https://sengi.run/blog/github-actions-pricing-changes</id>
    <link rel="alternate" href="https://sengi.run/blog/github-actions-pricing-changes" />
    <title>GitHub Actions pricing changes: every dated change and what it meant</title>
    <summary>Every GitHub Actions pricing change, dated: the January 1, 2026 cut of up to 39%, the self-hosted charge that was announced and postponed, and what each meant for a private-repo team.</summary>
    <published>2026-09-13T00:00:00Z</published>
    <updated>2026-09-13T00:00:00Z</updated>
  </entry>
  <entry>
    <id>https://sengi.run/blog/github-actions-free-minutes</id>
    <link rel="alternate" href="https://sengi.run/blog/github-actions-free-minutes" />
    <title>GitHub Actions free minutes: what each plan includes and what a quota buys on every runner</title>
    <summary>GitHub Actions free minutes, checked September 13, 2026: included minutes and storage on Free, Pro, Team and Enterprise Cloud, what the quota buys on Linux, Windows, macOS and arm64, what public repositories get, and what happens when it runs out.</summary>
    <published>2026-09-13T00:00:00Z</published>
    <updated>2026-09-13T00:00:00Z</updated>
  </entry>
  <entry>
    <id>https://sengi.run/blog/github-actions-billing-explained</id>
    <link rel="alternate" href="https://sengi.run/blog/github-actions-billing-explained" />
    <title>GitHub Actions billing explained: how a minute is counted and what else spends it</title>
    <summary>GitHub Actions billing explained, checked September 13, 2026: how a minute is rounded per job, matrix jobs and retries, storage on its own meter, which GitHub features spend your minutes, spending limits, and how to find what is eating them.</summary>
    <published>2026-09-13T00:00:00Z</published>
    <updated>2026-09-13T00:00:00Z</updated>
  </entry>
</feed>
