I searched Google for what tools technical founders use to run their product's blog. The top results were lists of 12, 15, and 27 tools built for bloggers, and none of them mentioned repositories, builds, or APIs.
Here's the stack I use for my own product blogs: five pieces, what each one does, and where it falls short. I've spent more than fifteen years building digital businesses, and this is what I run today, including a Next.js blog for this product.
You'll also see what the data piece actually costs, with the numbers I paid to research this exact article. Let's start with the full map before going piece by piece.
- The five pieces
- Framework: Next.js or Astro
- CMS: Keystatic
- Deploy: Vercel
- Data: DataForSEO
- Process: seodraft
- What stack to set up this week
A product blog is built from five pieces
A technical product blog is built from five pieces: framework, CMS, hosting, search data, and editorial process. The lists that rank mix all of that with WordPress plugins and design tools.
That difference matters because a technical founder already has half of it solved. If your product lives in a repository and deploys itself, the blog can follow the exact same flow.
| Piece | What I use | What it's for |
|---|---|---|
| Framework | Next.js and Astro | Rendering the blog |
| CMS | Keystatic | Editing posts as repo files |
| Hosting | Vercel | Publishing on every commit |
| Data | DataForSEO | Knowing what people search |
| Process | seodraft | Calendar, briefs, and rules |
Next.js or Astro: pick based on where the blog lives
The blog's framework should be the one your team already knows, and between Next.js and Astro the decision comes down to where the blog lives. I run a Next.js blog today, but I've also liked building blogs with Astro.
Next.js fits when the blog shares a domain, components, and design with the product app. You reuse the layout, the design system, and even authentication if you ever want private content.
Astro fits when the blog is a separate content site. It ships HTML with zero JavaScript by default and comes with content collections built for Markdown.
Take this as usage opinion, not a benchmark: I didn't measure performance between the two. Both work fine with the rest of the pieces in this list.
Keystatic stores your posts in the repository
Keystatic stores every post as a file inside your repository, with no separate database. I use Keystatic as a CMS because I like the simplicity of working git-based.
According to its GitHub repository, Keystatic stores content as Markdown, YAML, or JSON files and integrates with Next.js, Remix, and Astro. Schemas are defined in TypeScript, so the content model gets versioned alongside the code.
Git-based means every content change is a commit. You can review it, revert it, or open it as a pull request, just like any other product change.
The limit is real too. Keystatic doesn't ship publishing schedules or an approval flow, and the project itself is still described as experimental. If someone on your team needs to edit without thinking about Git, Tina or Decap are other git-based options worth evaluating.
Vercel publishes every commit without manual steps
Vercel is where I deploy my blogs, and with a git-based CMS the publishing loop closes on its own. You save a post in Keystatic, that generates a commit, and Vercel builds and publishes the new version.
Every branch also gets its own preview URL. That lets you read the post the way it will actually look, with styles and images, before merging it.
A static blog on Next.js or Astro deploys to Vercel with no special configuration. For a one-person team, that's one fewer piece to maintain.
DataForSEO tells you what to write for cents
DataForSEO is the search data source I use, and it charges by usage instead of a monthly subscription. I use DataForSEO because it feels affordable for how much useful information it delivers.
The numbers from this article show it well. Measuring a batch of keywords costs about USD 0.11, and a SERP brief runs about USD 0.004 once the topic already has metrics.
That brief gave me what I used to decide the angle: the titles that rank, the related questions, and whether Google shows an AI Overview. For this search it does, so every section of this post opens with the answer.
DataForSEO delivers data through an API, so you need code or a tool on top of it to read it. If you prefer a dashboard with charts, you'll miss having an interface.
seodraft keeps consistency and quality steady
seodraft organizes the editorial process with a calendar, the business profile, briefs, and a set of rules that checks every draft. I use seodraft because it helps me keep consistency and quality across content.
The AI agent you already pay for writes the draft. The rules check structure, evidence, and filler phrases, and you approve before exporting to Markdown, the same format Keystatic reads.
What stack to set up if you're starting your blog this week
If you're starting this week, use your product's framework, Keystatic, and Vercel, then add data and process once you're publishing regularly. Those three pieces sit directly on the repository you already have.
Keystatic delivery pairs well with a Resend-based email system once you want to notify readers, and a consistent brand voice keeps every post recognizable regardless of who drafts it. See how the CMS delivery piece works in seodraft on the CMS delivery page, and check real search costs on the DataForSEO page.
If you want to try the full process, create your seodraft account: your agent writes, the rules decide, you approve.
