Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion content/blog/meta.json
Original file line number Diff line number Diff line change
@@ -1,3 +1,3 @@
{
"pages": ["index", "introducing-volcano-agent-cloud", "introducing-volcano-sandbox", "..."]
"pages": ["index", "introducing-volcano-agent-cloud", "volcano-built-on-volcano", "introducing-volcano-sandbox", "..."]
}
50 changes: 50 additions & 0 deletions content/blog/volcano-built-on-volcano.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,50 @@
---
title: Volcano, built on Volcano
description: The volcano.dev app, docs, APIs, and billing all run on the same Volcano primitives you get on day one.
category: engineering
tags: [frontends, functions, database]
author: Mark Kim
published: "2026-11-19"

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 P2: New post will be listed after the older October post, so /blog is no longer newest first

BlogHome says the listing is "newest first" (src/components/blog-home.tsx:9). But getSectionPages (src/lib/sections.ts:60) and the category pages order posts only by navigation order from content/blog/meta.json. That file lists introducing-volcano-agent-cloud (2026-11-19) and introducing-volcano-sandbox (2026-10-19) by name, then "...". This post is picked up only through "...", so it comes last: below the October sandbox post on /blog, on /blog/category/engineering, and in the sidebar, even though it's dated 2026-11-19. To fix it, add "volcano-built-on-volcano" to meta.json before "introducing-volcano-sandbox". Put it after the launch post if that post should stay first among the same-day posts.

Found by claude-opus-5-5

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed in 4fc6811: meta.json now names this post after the launch post and before the October sandbox post.

---

Every screen you see on volcano.dev runs on Volcano. The sign-up page, the dashboard, the docs, the API behind them, and the billing system that charges your card all live on the platform you're about to use.

We've been building that application, which makes us Volcano's first users. Before any customer deployed a frontend or wrote a function, we did, and we run our own business on it every day.

Here's what that stack looks like, piece by piece.

![Diagram: every part of volcano.dev runs on a Volcano primitive. Frontend hosts the web app (Next.js) and the docs site. Function hosts the REST API, the billing API, the support API, and the Stripe webhook, which receives events from Stripe. Database holds billing data. Scheduler runs billing operations.](/blog/volcano-built-on-volcano/stack.png)

*Volcano's own building blocks carry the whole product. Stripe is the only outside piece, and it talks to us through a Volcano Function.*

## Two frontends, shipped on their own schedules

The volcano.dev web app is a Next.js application, hosted by [Volcano Frontend](/platform/frontends/overview). We build it and deploy it the same way you would.

The docs site is a second, separate frontend, also hosted on Volcano. It deploys independently, so a docs fix ships without waiting on an app release, and an app release never takes the docs down with it.

## Every API is a Volcano Function

The REST API behind volcano.dev is built and hosted on Volcano's [Function](/platform/functions/overview) primitive. So is everything else that keeps the business running:

- **Billing API**
- **Support API**
- **Stripe webhook** — billing runs on Stripe, and a function bridges Stripe's events into our system

That's the same primitive you get on day one. When it has a bad day, our revenue has a bad day, so it gets our full attention.

## Billing data lives in a Volcano database

Some of volcano.dev's most critical data sits in Volcano's own [database](/platform/databases/overview). Billing is the part where a mistake costs real money.

The Volcano scheduler runs our critical billing operations as [scheduled function invocations](/platform/functions/scheduled-invocations). Those jobs don't run on an outside cron service. They run on the same schedules you'd set up for your own functions.

## Why we run on it first

Frontends, Functions and their schedules, and the database. Everything you touch on volcano.dev runs on the same building blocks we hand to you.

That matters for one plain reason: we feel every rough edge before you do. A slow deploy slows down our releases. A flaky function breaks our billing. When we fix those things for ourselves, we've fixed them for you too.

So when you sign up, you're starting where we started.

[Start building with Volcano →](https://volcano.dev)
Binary file added public/blog/volcano-built-on-volcano/stack.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.