OpenWorkers
Serverless runtime in Developer tools
Self-hosted, open-source alternative to Cloudflare Workers with the same developer experience and no vendor lock-in, though it is not yet polished.
Self-hosted, open-source alternative to Cloudflare Workers with the same developer experience and no vendor lock-in, though it is not yet polished.
19 people gave an opinion
- recommend it
- 15
- criticize it
- 4
- approval share
- 79%
Recommended in 1 of 13 months
- November 2025: not recommended
- December 2025: not recommended
- January 2026: recommended
- February 2026: not recommended
- March 2026: not recommended
- April 2026: not recommended
- May 2026: not recommended
- June 2026: not recommended
- July 2026: not recommended
- August 2026: not recommended
- September 2026: not recommended
- October 2026: not recommended
- November 2026: not recommended (month in progress)
Why it doesn’t carry the badge
- 15 people recommend itNeeds 10 or more, met.
- 3.8 recommenders for every criticNeeds 2 to 1 or better, met.
- Recommended in 1 of 13 monthsNeeds 4 or more, not met.
The same three rules apply to every product, and the badge can’t be bought. How the badge works
What people say about it
The reasons people give, with the number of comments that give each one. Open a reason to read what they said.
Why people recommend it
Each mark is one comment
Admired as a cool, well-built project
“Amazing work! I have been thinking exactly about this.”
Comment from 2 Jan 2026 in “OpenWorkers: Self-Hosted Cloudflare Workers in Rust” “Very cool project by the way, thanks for posting it”
Comment from 1 Jan 2026 in “OpenWorkers: Self-Hosted Cloudflare Workers in Rust” “Technically, and architecturally this is excellent.”
Comment from 1 Jan 2026 in “OpenWorkers: Self-Hosted Cloudflare Workers in Rust” - Comment from 1 Jan 2026 in “OpenWorkers: Self-Hosted Cloudflare Workers in Rust”
Open-source, no vendor lock-in
“This is perfect for knowing you always got a escape hatch.”
Comment from 1 Jan 2026 in “OpenWorkers: Self-Hosted Cloudflare Workers in Rust” “Same DX as Cloudflare Workers, no vendor lock-in.”
Comment from 1 Jan 2026 in “OpenWorkers: Self-Hosted Cloudflare Workers in Rust” “Offering open-source alternatives is always good”
Comment from 1 Jan 2026 in “OpenWorkers: Self-Hosted Cloudflare Workers in Rust”
What people warn about
Each mark is one comment
Not yet polished or user-friendly
“Tested it briefly, works, but not user-friendly at all yet.”
Comment from 2 Jan 2026 in “OpenWorkers: Self-Hosted Cloudflare Workers in Rust” “Tested it, works, just hasn't been polished yet.”
Comment from 1 Jan 2026 in “OpenWorkers: Self-Hosted Cloudflare Workers in Rust”
What people said
20 of the 25 comments that mention it, newest first. Each links to the original comment.
“nice, KV + Postgres covers most of our use cases. the TTL on KV is useful for caching auth tokens between invocations”
“Tested it briefly, works, but not user-friendly at all yet.”
“Workers that hit limits (CPU, memory, wall-clock) get terminated cleanly with a clear reason.”
“OpenWorkers gives you the same model when you need compliance or data residency.”
“I get the impression this can't be run without NodeJS right now?”
“Amazing work! I have been thinking exactly about this.”
“Tested it, works, just hasn't been polished yet.”
“Technically, and architecturally this is excellent.”
“Very cool project by the way, thanks for posting it”
“this sort of project completely misses the whole reason why this sort of technology is used.”
“If you remove the global edge network and cache, you do not have any compelling reason to look at this.”
“Recently, with Claude's help, I rewrote everything on top of rusty_v8 directly.”
“This is perfect for knowing you always got a escape hatch.”
“Offering open-source alternatives is always good”
“Simpler, easier to hack on.”
“it's buggy as hell when self-hosted”
“Cool project, great work!”
“Over promising on security hurts the credibility of the entire project”
“Interesting option to consider next to openfaas”
“Same DX as Cloudflare Workers, no vendor lock-in.”
Counts come from 1,795,640 Hacker News comments, November 2025 to November 2026. How we count. Report a mistake.