Repository navigation
feat(blog): add Volcano, built on Volcano post #240
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
marckong
wants to merge
2
commits into
main
Choose a base branch
from
blog/volcano-built-on-volcano
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| 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", "..."] | ||
| } |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| 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" | ||
| --- | ||
|
|
||
| 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. | ||
|
|
||
|  | ||
|
|
||
| *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) | ||
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
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
BlogHomesays the listing is "newest first" (src/components/blog-home.tsx:9). ButgetSectionPages(src/lib/sections.ts:60) and the category pages order posts only by navigation order fromcontent/blog/meta.json. That file listsintroducing-volcano-agent-cloud(2026-11-19) andintroducing-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"tometa.jsonbefore"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
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed in 4fc6811:
meta.jsonnow names this post after the launch post and before the October sandbox post.