$12 server arena: one comment turned into a repo, 34 days, 713 stars, 327 PRs
What it is A public arena: anyone can implement the same 5-endpoint small API on SQLite in any language. The author benchmarks all entries on a 1 vCPU / 2 GB $12 server and ranks them, then turns the results into a video.
Why it took off The author's own YouTube series (700k to 800k views per episode) turned the "which language is fastest" argument into a challenge people could submit to, get ranked on, and be named in a video. Participants sharing their rankings then spread it further.
CHow you could follow it Don't build another $12 server arena. Creators with a channel can follow the same loop (comparison video that provokes debate → a repo with rules fixed in code → results turned into the next episode), swapping in a new hard constraint and a debate-prone topic. Those without a channel do better to submit an obscure implementation to an existing arena and ride the exposure from video shout-outs.
- Data (updated daily) · Repo created 2026-10-03 · 745 stars · 7 days +174
GitHub · stars Data 2026-10-09 → 2026-11-08 (31 days, 31 observations). Points before 10-28 come from deeply / archive backfill, not every day has one
twelve-dollar-server-challenge is a public arena: in any language, write the same 5-endpoint small API on SQLite, and the author runs it on a 1 vCPU, 2 GB RAM, $12/month server, benchmarks everything under the same conditions, and cuts the results into a YouTube video. Created in Oct 3, it reached 6 stars, 713 forks, and 337 PRs by Nov 327. Below: what it is, where the stars came from, why someone else starting it probably wouldn't take off, and what you can learn from it if you want a project that earns stars.
A comment with 214 likes
In 2026 Oct 2, tech YouTuber Arjay McCandless (136K subscribers) posted a video: "Which Programming Language Can Handle the Most Users on a $12 Server?" He wrote the same API in 8 languages (Node, Bun, Python, Go, Java, Rust, C#, PHP) and ran each one until it crashed on the same $12 machine. The last line of the video description reads: "Are you an expert in one of these languages? I'd love to test your version. Email me."
By Nov 6 the video had 825k views and 1,610 comments (YouTube, 11-06). The comment section was both praising and arguing: some said using Laravel for PHP wasn't fair, others asked for every language to be retested on SQLite. One comment with 214 likes was nearly the blueprint for this repo:
I propose having a github repo with actions pipeline for initial test (41 unit tests), and then you as the owner can accept a contribution to pass into the server and get the result aggregated and added to a leaderboard
The next day, the repo was up.
What it actually is
The rules were strict: implement a Twitter-like feed API with 5 endpoints and a fixed table schema, seeded with 50k users, 500k posts, and 2M likes. First pass the 42 checks in test/test.sh, then the author load-tests at k6. The score is "the most concurrent users sustained for 5 minutes" (p95 < 500ms, p99 < 1s, error rate < 1%). No cross-request caching, writes must actually hit disk, no detecting load-test traffic, no kernel tuning.
To enter, you fork the repo, add a submissions/<language>-<framework>-<username>/ directory, and open a PR. CI runs the tests automatically. So the fork count is half the star count (337 / 713), which comes from the submission process itself, not just from lots of onlookers.
As of Nov 6 (GitHub, 11-06): 327 PRs opened, 209 merged, 113 contributors, and 170 implementations in the repo. 23 in C, 14 in Go, 12 in Rust, 11 in Java, 10 in C#, plus 6 in assembly, 3 in Lean, 2 in Fortran, and oddballs like Ada, Mojo, and WebAssembly text format. The top of the leaderboard is Rust + io_uring, sustaining 310k users; Bash came in at 3,500.
For comparison: the author's best result in the 10-02 video was 14,050 users. The first line of the first arena video (10-13) read "you all took it to 64,000".
Where the stars came from: each video release gave a bump
| Date | What happened | Video views (11-06) | Stars |
|---|---|---|---|
| 09-25 | "How Many Users Can a $12 Server Handle?", series kickoff | 514k | — |
| 10-02 | 8-language comparison, hiring in the description | 825k | — |
| 10-03 | Repo created | 0 | |
| 10-13 | First arena results, repo link in the description | 734k | 10-15 in one day, +130, the all-time high |
| 10-23 | Part 2 "…Max Out a $12 Server (again)" | 197k | 10-24 single-day +60 |
| 10-30 | Short "Lean vs $12 server?!" | 424k | |
| 10-31 | A contestant brags on X about taking first place | 11-01 single-day +49 | |
| 11-03 | Part 3 "218 Developers COMPETE…", breaking down the top 10 entries' code one by one | 106k (3 days) | 11-06 single-day +45 |
(Video views: YouTube. Stars: GitHub daily counts, logged day by day from 10-17 on; earlier, only the single-day peak is known.)
Stars barely moved between the two videos: 10-17 to 10-23 gained about +5 a day. Traffic came almost entirely from one source: the author's own channel. He also has 106k followers on TikTok, where short clips pull out the "underdog language beats C" angle and share it on their own.
The second source was the contestants themselves. In Oct 31, Harsh Gupta (@hargup13 on X) posted that his Lean 4 submission took first in the $12 server challenge, "faster than Rust, C, even hand-written assembly." It got 44.9k views and 620 likes (X, 11-06). The day before, the author had posted a short about Lean that hit 420k views. Contestants spread the word to show off their rank, and the author looked for contestants' stories for his next video, so each drove traffic to the other.
Everything else was small: a long LinkedIn post by the author got 10-13 reactions, a r/dotnet thread discussed why the C# result looked odd, and Hacker News had one repost with 86 points, and 2 points at most. Some people have already built add-ons: a "k12-compatible load tester for the $6 server challenge" (kload), and a repo that walks through the leaderboard code (cursed-http-tour).
Why people are willing to submit code
- It turns arguments into homework. "Which language is fastest" is the argument programmers love most. The first round was a comparison of default, unoptimized code, so every language's fans naturally want to prove "you just wrote it badly." The most-liked comment on the first video was "I love that most language speedups are: call a C library" (3,069 likes), and the argument kept going in the comments.
- Low bar, high ceiling. You can write the 5 endpoints over a weekend. But the leaders use io_uring, read the B-tree directly around SQLite, and batch writes. The top entry climbed from 64k to 310k, which gives experts reasons to keep coming back.
- The reward is exposure, not prize money. The top finishers get named in videos with hundreds of thousands of views and have their code picked apart line by line. For developers, that's worth more than a few hundred dollars.
- The "$12 server" frame. It taps into the real question of how many people a small machine can actually handle, and using "concurrent users" as the score is far easier to grasp than "requests per second."
- The slot is open. The long-standing multi-language benchmark TechEmpower Framework Benchmarks (8,101 stars) was archived in March 2026. The community lacked a live arena where everyone submits code.
The repo itself makes no money; the money is elsewhere. Each video promotes the author's system design practice app, Devmaxx. The 10-23 episode included a $20 free credit from VPS provider Synteq, and the test machine later switched to Synteq. The leaderboard only shows the top 8 publicly, and the rest requires leaving an email to subscribe to his newsletter. The arena produces content for the channel and collects emails for him.
Who it's competing with
| Project | Launched | Scale (stars) | How it differs |
|---|---|---|---|
| 1BRC(gunnarmorling/1brc) | 2023-12 | 8,144 | Closest precedent: a well-known author sets the rules, the community sends PRs, and scores are run in a unified way. Limited to Java, spread through blogs and X. |
| TechEmpower Framework Benchmarks | 2013-03 | 8,101, archived | An institution-maintained framework throughput test, with no one presenting it and no competitive feel |
| the-benchmarker/web-frameworks | 2017-03 | 7,096 | Automatically tests hello-world style endpoints, with no commentary |
| HttpArena | 2026-03 | 147 | Also a multi-language HTTP benchmarking platform, very complete, but with no distribution |
| Anton Putra's load-testing videos | From ¥2020 | YouTube, 122k subscribers | The author writes code to compare, without taking viewer submissions |
| The author's own multicore / million-users version | 2026-10 | 79 / 47 | The same playbook with a different machine spec |
The last line matters most: the same author, the same channel, the same rules, and two more arenas on different machine specs, one with 79 stars and one with 47. The first arena absorbed the attention, and later follow-ups (even by him) got little of it. HttpArena shows the other side: however complete the thing is, without someone telling the story it sits at a hundred-odd stars.
If it were you
One-line verdict: the repo's stars came from a serialized video series, not from the repo itself. If you don't have a channel with tens of thousands of subscribers or an account with tens of thousands of followers, copying an "arena where everyone submits code" will most likely get you HttpArena's one or two hundred stars. What's worth learning is how it turns arguments into submissions. Following it is not a good use of your time.
Who it suits: tech creators who already have a developer audience on YouTube, Bilibili, or X and can keep publishing; or people with influence in a particular language or niche (the author of 1BRC is a familiar face in the Java scene).
Who it doesn't suit: solo developers hoping to get stars from the repo alone, with no distribution channel; anyone who can't publish results every two or three weeks, break down code, and call out top performers. Once the arena stops being updated, submissions and stars stop too.
How to do it:
- Start the argument first, then open the arena. Run a comparison using "default settings" and deliberately leave room for people to disagree. Wait until someone in the comments says "you wrote it badly," then open the repo.
- Fix the rules, make them cheat-resistant, and verify with CI automatically. The author only handles running benchmarks and telling the story, so a serialized series needs very little manpower.
- Pick a new hard constraint plus a topic people love to argue about, and avoid the "$12 server running a Web API" slot. Candidates (inferred, not checked for duplicates): how large a local model a Raspberry Pi can run, how many agents a consumer GPU can handle at once, how small a frontend framework's first screen can get, which database uses the least memory on the same task. A Chinese-language version could also use "a 2-core 2GB domestic cloud host."
- If you don't have a channel, try a different angle: submit an implementation in an obscure language or technique to this arena. Being named in a video and bragging about your rank on X is the cheapest exposure for someone with no audience. Harsh Gupta's tweet came about exactly that way.
How to get stars: put the repo link on the first line of each video description; name and break down the code every episode, so contestants have something to show off; cut the most surprising result (the underdog beating C) into its own short; make the leaderboard a standalone page that's easy to share.
When to move: this slot is already taken by it. If you build in a different niche, the window follows the topic: "how many users can local models / agents handle" is a hot topic right now, roughly the next few months.
Signs you've misread it: after the first comparison goes out, no one argues in the comments and no one says "I can write it faster"; or after two weeks the repo has fewer than ten external PRs. That means the topic isn't provoking enough disagreement, or you don't have enough viewers yet. Build your audience first, rather than opening another arena.
Research notes: competitor table, acquisition evidence, full research report
- Competitors
Name Where Launched Scale How it differs from this one TechEmpower Framework Benchmarks Open source 2013-03 8,101 stars, 2026-03, archived An institution-maintained standardized framework throughput test, with no author and no content. It's one person plus a video series plus calling out top performers. the-benchmarker/web-frameworks Open source 2017-03 7,096 star Automatically tests hello-world style endpoints, with no competitive feel and no commentary 1BRC(gunnarmorling/1brc) Open source 2023-12 8,144 star The closest precedent (a well-known author sets the rules, the community sends PRs, scores are run in a unified way), but limited to Java and spread through blogs and X. It isn't language-limited and runs on a YouTube series. HttpArena Open source 2026-03 147 star Also a multi-language HTTP benchmarking platform, but with no content distribution Anton Putra's load-testing videos Other 2020 YouTube, 122k subscribers; tutorials repo, 4,713 stars The author writes code to compare, without taking viewer submissions - Where users come from
- Verified creator's YouTube series: 10-02 language comparison 825k views, 10-13 arena episode 1 734k, 10-23 episode 2 197k, 11-03 episode 3 106k, each with the repo link in the description; the star spikes line up with the upload dates
- Verified YouTube Shorts / TikTok short videos: 10-30 short "Lean vs $12 server?!" with 424K views; TikTok @arjay_mccandless with 106K followers, has posted about the Assembly API slicing
- Verified a contestant bragging on X: @hargup13 posted 10-31 that his Lean 4 took first, with 44.9k views and 620 likes, plus a PR link. Stars rose by +11-01 afterward (49).
- Verified LinkedIn / Reddit: the author's long LinkedIn post got 10-13 reactions 86; threads or reposts appeared on r/dotnet and r/FreeITCourses.
- Inferred HN: only one repost of the video, at 10-09 points, 2 points.
arjaythedev/twelve-dollar-server-challenge research report
Channel: GitHub | Research date: 2026-11-06 | Data card: repo created 34 days ago, 713 stars / 337 forks, +7 in the last 207 days (+7 in the first 145 days), single-day peak +130 (2026-10-15)
One line
A tech YouTuber (Arjay McCandless, 136k subscribers) runs a public arena for his series "How many users can a $12 server handle". The rules are fixed (SQLite, 5 endpoints, 1 vCPU / 2 GB machine, 42 tests). Viewers submit PRs in any language, he runs the benchmarks in one setup, and then cuts the results into new videos. The repo isn't the product. It's a content production line: the code viewers submit becomes material for the next video, and the stars and forks are a by-product.
1. What it is
- README: implement a Twitter-like feed API (5 endpoints, fixed schema, seed database of 50k users / 500k posts / 2M likes), pass 42 checks via
test/test.sh. The author uses k6 on the same machine to find the limit. Score = the maximum concurrent users sustained for 5 minutes (p95<500ms, p99<1s, error rate <1%). The rules are detailed: no caching across requests, writes must be durable (WAL + synchronous=NORMAL or stricter), no detecting load-test traffic, no kernel parameter tweaks. - How to submit: fork → add a
submissions/<language>-<framework>-<username>/directory → open a PR, and CI runs the tests automatically. So the fork/star ratio of up to 47% is inherent to the submission process (you have to fork to open a PR), not just a sign of high engagement. - Scale (GitHub API, 2026-11-06): 327 PRs in total, 209 merged; the submissions directory holds 170 implementations; 113 contributors. Top languages: C 23, Go 14, Rust 12, Java 11, C# 10, plus assembly 6, Lean 3, Fortran 2, Ada, Mojo, WAT and other obscure languages.
- Leaderboard at benchmarks.arjaythedev.com/12-dollar-server: 177 implementations, 78 queued for testing. The top entry, Rust with io_uring, held up to 310,000 users, with Mojo, C, and Lean right behind at 4. Bash is at 3,500. The full leaderboard requires subscribing to the author's newsletter, The Dev Download (the top 8 are public, the other 169 require an email). The test machine switched from the DigitalOcean in the videos to sponsor Synteq's VPS.
2. Why it took off
2.1 Traffic source: the author's own YouTube channel, nearly the only one
Channel @arjay_the_dev (YouTube Data API, 2026-11-06): 136k subscribers, 49M total views, 426 videos; TikTok @arjay_mccandless 106k followers, 2.22M likes (TikHub). The rhythm of this series (YouTube Data API view counts):
| Date | Video | Views | Relation to the repo |
|---|---|---|---|
| 09-25 | How Many Users Can a $12 Server Handle? | 514k | Series kickoff: Node + Postgres single-machine benchmark |
| 09-29 | Rust vs Java on a $12 Server | 321k | Series continues |
| 10-02 | Which Programming Language Can Handle the Most Users on a $12 Server? | 825k, 1,610 comments | 8-language comparison; the video description says "What language do you master? Email me." Repo created on day two (10-03). Viewers demanded "your X code isn't optimized enough," and the author turned that into an arena. |
| 10-13 | I Asked Expert Programmers to Max Out a $12 Server | 734k, 1,251 comments | Results of the first round (26 valid submissions, top 64,000 users); the description links to the repo. Single-day star peak of +130 appeared on 10-15, right after this episode. |
| 10-15 | I challenged Rust Developers | 158k | Directly tagging a language community |
| 10-23 | I Asked Expert Programmers to Max Out a $12 server (again) | 197k | Second episode, with a repo link; stars 10-23 → 10-24 +60 |
| 10-30 | Lean vs $12 server?! (short video) | 424k | A short video built on the contrast of "a theorem-proving language beating assembly" |
| 11-03 | 218 Developers COMPETE to max out a $12 server | 106k (3 days) | Third episode: breaking down the top 10 entries one by one; with leaderboard and repo link |
Our database's daily data (daily data cards) lines up with the video timeline: 10-17 to 10-23 flat (about +5 per day), 10-24 jumps +60,10-31 → 11-01 +49,11-05 → 11-06 +45. Stars jump every time a video episode comes out and barely grow in between.
2.2 secondary spread: participants show off their own rankings
- Harsh Gupta(@hargup13)10-31 posted on X: "My Lean 4 submission took first place in the $12 server challenge, faster than Rust, C, and even hand-written assembly." 44.9k views, 620 likes (read via r.jina.ai from the x.com page). His PR #153 link is in the replies. The story of a niche language beating C was turned into a short video with 420k plays, creating a cross-traffic loop between the contestant and the creator.
- A long LinkedIn post by the author 10-13 (86 reactions, 18 comments) covers io_uring, dropping frameworks, and group commit, and ends with "I'm sponsoring the next video."
- Reddit: r/dotnet has a discussion thread "Arjay the dev 12$ server YouTube video" (discussing why the C# results are odd); r/FreeITCourses has a repost.
- Others have run this benchmark in their own projects: Praveen-1308/ferro-os published the report "The $12 Server Concurrency Challenge on FerroOS"; others built companion tools (3x3xX3N0N/kload, "a k6-compatible load tester for the $12 server challenge") and explainer repos (public/cursed-http-tour).
- HN: only one repost of the video with 2 points (10-09 comments); HN didn't take off. No related tweets were captured in the local x-radar corpus.
2.3 Why now, and why would people show up
- Hits the "language wars": "Which language is fastest" is the topic programmers love arguing about most, and the first video used "default, unoptimized" code, so fans of every language naturally want to prove "you just wrote it badly." The first video's description already recruited participants, with 1,610 comments. The arena turns arguing into action: you can submit and earn a ranking.
- Low barrier, high ceiling: the API has only 5 endpoints and can be written over a weekend, but top spots require io_uring, bypassing SQLite to read the B-tree directly, and group commit, leaving deep room for optimization that experts will keep grinding.
- The reward is exposure: the top finishers get named in a video with hundreds of thousands of views and have their code dissected (the 11-03 episode specifically broke down the top 10). For developers, that's a very tangible reputation payoff.
- The "$12 server" frame: it speaks to indie developers' real anxiety of "how many users can my little machine handle," and it's easier to grasp than "requests per second" (using "concurrent users" as the score).
- Timing: the veteran multi-language benchmark TechEmpower Framework Benchmarks (8,101 stars) has its repo 2026-03 archived (GitHub API archived=true), so there's no active arena where the community submits code anymore.
2.4 Where the money comes back
The repo itself doesn't earn; the money comes from the ring around it: ① each episode promotes the author's system design practice app Devmaxx (devmaxx.dev, 7-day free trial); ② video sponsorship (the 10-23 episode carried a $20 free credit from Synteq, and the test machine was also switched to Synteq); ③ the full leaderboard data requires subscribing to the newsletter "The Dev Download": the arena itself became a tool for collecting emails; ④ the author publicly recruits sponsors for the next video on LinkedIn.
3. Competitors
| Name | Where | Launched | Scale | How it differs |
|---|---|---|---|---|
| TechEmpower Framework Benchmarks | Open source | 2013-03 | 8,101 stars; 2026-03 archived | Standardized throughput testing for frameworks, maintained by an organization with no content and no personality; this is one person plus videos, and the challenge is "how many users can it handle," with a naming segment |
| the-benchmarker/web-frameworks | Open source | 2017-03 | 7,096 stars, still being updated | Automated testing of hello-world-style endpoints, with no competitive feel and no author commentary |
| 1BRC(One Billion Row Challenge,gunnarmorling/1brc) | Open source | 2023-12 | 8,144 star | The closest precedent in form: a well-known author sets the rules, the community submits PRs, and the author runs the benchmarks and publishes results. 1BRC is Java-only and spread through blogs and X; this one has no language restriction and spreads through a YouTube series. |
| HttpArena(MDA2AV/HttpArena) | Open source | 2026-03 | 147 star | Calls itself "the most complete HTTP benchmark platform," but has no content distribution and far fewer stars |
| Anton Putra's load-testing videos | YouTube | From ¥2020 | 122k subscribers; tutorials repo has 4,713 stars | Similar YouTube load-testing content, but all of it is the author writing code and comparing; none accepts viewer submissions |
| The author's own spin-off arenas: multicore-server-challenge / million-users-challenge | Open source | 2026-10-14 / 10-21 | 79 / 47 star | The same playbook with different machine specs clearly falls short of the original, showing the first arena absorbed most of the attention |
4. Differentiation
What's truly different is that benchmarking + serialized video + calling out viewers are bound together: viewers submit code → the author runs the benchmarks → it's made into a video praising people by name → the video draws more people to submit code. TechEmpower and web-frameworks only have leaderboards, with no one narrating; Anton Putra has videos but doesn't accept viewer code; 1BRC has a community arena but is limited to one language and has no serialized video. The rules are detailed enough to prevent cheating (no caching, writes must be persisted to disk, JWT verified in real time), so that "an obscure language beats C" holds up and becomes a story that can be made into a short video.
That differentiation is why it took off, but the precondition is that the author already has a channel with 130k subscribers. The same repo published by someone without traffic would probably get what HttpArena gets: one or two hundred stars.
5. How many people have seen it, and whether anyone is copying it
- Visibility: already fairly large in the developer YouTube circle (the two main videos each got 700k to 800k views, several million views total across the series), but small buzz on GitHub, HN, and X (HN 2 points; the largest X post is a participant's own post with 45k views), and no media coverage.
- Copycats: so far I haven't seen other creators copy the "viewers submit PRs + video benchmarks" model; only the author is replicating it (multi-core version, million-users version), along with satellite repos around it (kload, cursed-http-tour, the ferro-os report).
6. What others can learn
- Turning comment-section arguments into an arena you can submit to: first publish a "default config" comparison video that deliberately stirs things up, then open the repo for those who disagree to submit, and make the results into the next episode. Each episode brings in new submissions.
- Rules are fixed and cheat-resistant, CI verifies automatically, and the author only needs to run benchmarks and tell the story, so a serialized series can be run with very little manpower.
- The reward is exposure: being named and having code dissected in videos, with no cash prizes.
- The leaderboard is only partially public; the full data requires leaving an email, while promoting the author's own product and selling sponsorships, turning arena traffic into money.
- The approach can be applied to other scenarios: "how large a model can a $5 Raspberry Pi run," "how many agents can one 4090 handle," and so on. All it takes is one comparable hardware constraint plus a topic people love to argue about.
7. Uncertain
- The GitHub stargazers API returns 404, so per-day star timestamps can't be obtained; the 10-03 to 10-16 daily growth can only be inferred from max_day in the data cards (10-15 +130).
- Link click counts in video descriptions, newsletter subscriber numbers, and Devmaxx conversions are not public.
- Whether switching the test machine from DigitalOcean to Synteq was a sponsorship trade is unverified (the timing matches the Synteq credit in the 10-23 video).
- The specific popularity of the Reddit posts was not obtained (the reddit.json endpoint returned non-JSON).
Sources
- GitHub API: repos/arjaythedev/twelve-dollar-server-challenge (README, PR search, contributors, contents/submissions), users/arjaythedev/repos, competitor repo metadata (2026-11-06)
- YouTube Data API v3: videos sQXFhh_PiG4, QGWKCaglSBI, -BFt49ula08, TbsynnWC6BA, Cr69N5pG258, GFtFIxrAjIs, and the upload list of channel UCdSsl5RM4Tne4MhDRz2HjWw; @AntonPutra channel stats
- Leaderboard: benchmarks.arjaythedev.com/12-dollar-server
- LinkedIn:www.linkedin.com/posts/arjay-mccandless-9178b4198_last-week-…
- X:x.com/hargup13/status/2116422880221409621
- Reddit:www.reddit.com/r/dotnet/comments/1wxaue4/arjay_the_dev_12_se…
- HN Algolia (search "$12 server"); TikHub (TikTok @arjay_mccandless)
- Companion repos: github.com/Praveen-1308/ferro-os/blob/main/docs/reports/arjay_twelve_dollar_server_challenge.md, 3x3xX3N0N/kload, public/cursed-http-tour