HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
openfaas
faasd
Go2020–2021
openfaas / faasd

faasd

Lightweight and portable version of OpenFaaS

4Distinct people
25Mentions
0Explicit recommenders
3.3KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Lightweight and portable version of OpenFaaS

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by month25 dated mentions

Observed mentions: 2020-02-06 13:53:38 UTC to 2021-11-20 08:58:15 UTC.

012342020-02-01 00:00:00 UTC to 2020-03-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsFeb 20202020-03-01 00:00:00 UTC to 2020-04-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2020-04-01 00:00:00 UTC to 2020-05-01 00:00:00 UTC (exclusive): 2 mentions; 2 submissions, 0 comments2020-05-01 00:00:00 UTC to 2020-06-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2020-06-01 00:00:00 UTC to 2020-07-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2020-07-01 00:00:00 UTC to 2020-08-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2020-08-01 00:00:00 UTC to 2020-09-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-09-01 00:00:00 UTC to 2020-10-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2020-10-01 00:00:00 UTC to 2020-11-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2020-11-01 00:00:00 UTC to 2020-12-01 00:00:00 UTC (exclusive): 4 mentions; 2 submissions, 2 comments2020-12-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsDec 20202021-01-01 00:00:00 UTC to 2021-02-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2021-02-01 00:00:00 UTC to 2021-03-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2021-03-01 00:00:00 UTC to 2021-04-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-04-01 00:00:00 UTC to 2021-05-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2021-05-01 00:00:00 UTC to 2021-06-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-06-01 00:00:00 UTC to 2021-07-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2021-07-01 00:00:00 UTC to 2021-08-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2021-08-01 00:00:00 UTC to 2021-09-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-09-01 00:00:00 UTC to 2021-10-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-10-01 00:00:00 UTC to 2021-11-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-11-01 00:00:00 UTC to 2021-12-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsNov 2021

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Feb 20202020-02-01 00:00:00 UTC2020-03-01 00:00:00 UTC110
Mar 20202020-03-01 00:00:00 UTC2020-04-01 00:00:00 UTC101
Apr 20202020-04-01 00:00:00 UTC2020-05-01 00:00:00 UTC220
May 20202020-05-01 00:00:00 UTC2020-06-01 00:00:00 UTC110
Jun 20202020-06-01 00:00:00 UTC2020-07-01 00:00:00 UTC101
Jul 20202020-07-01 00:00:00 UTC2020-08-01 00:00:00 UTC110
Aug 20202020-08-01 00:00:00 UTC2020-09-01 00:00:00 UTC000
Sep 20202020-09-01 00:00:00 UTC2020-10-01 00:00:00 UTC101
Oct 20202020-10-01 00:00:00 UTC2020-11-01 00:00:00 UTC211
Nov 20202020-11-01 00:00:00 UTC2020-12-01 00:00:00 UTC422
Dec 20202020-12-01 00:00:00 UTC2021-01-01 00:00:00 UTC101
Jan 20212021-01-01 00:00:00 UTC2021-02-01 00:00:00 UTC202
Feb 20212021-02-01 00:00:00 UTC2021-03-01 00:00:00 UTC303
Mar 20212021-03-01 00:00:00 UTC2021-04-01 00:00:00 UTC000
Apr 20212021-04-01 00:00:00 UTC2021-05-01 00:00:00 UTC202
May 20212021-05-01 00:00:00 UTC2021-06-01 00:00:00 UTC000
Jun 20212021-06-01 00:00:00 UTC2021-07-01 00:00:00 UTC101
Jul 20212021-07-01 00:00:00 UTC2021-08-01 00:00:00 UTC110
Aug 20212021-08-01 00:00:00 UTC2021-09-01 00:00:00 UTC000
Sep 20212021-09-01 00:00:00 UTC2021-10-01 00:00:00 UTC000
Oct 20212021-10-01 00:00:00 UTC2021-11-01 00:00:00 UTC000
Nov 20212021-11-01 00:00:00 UTC2021-12-01 00:00:00 UTC101

What Hacker News says

25 sources
I'm the original creator of faasd, and just found this post on the Internet. What I liked was how he discovered faasd and found some unique value in it. I wanted to share it all with a broader audience here. His bootstrap is a little bit convoluted, if you check out GitHub, we have a simple installer script and an eBook as a reference manual. I'm not sure what the author means when he says it's complicated, but installing faasd requires almost no knowledge of containers, and there are very detailed step-by-step instructions. Once it's up and running, it's pretty much the same experience as openfaas on Kubernetes, just without scaling and clustering. https://github.com/openfaas/faasd
In Getting Started with Faasd
I was just reading the beginning of Arvid Kahl's Zero to Sold. He recommends using a tech stack that you already know and have lots of muscle memory with. I couldn't agree with him more. [1] This tech stack looks over-engineered upon first glance, but I don't know much about the author or his product. I use Kubernetes a fair bit whilst developing OpenFaaS and teaching people about K3s, but there is a whole world of development teams who aren't prepared to consider it as an option. One of the reasons we created "faasd" [2] (single-node OpenFaaS) was to help people who just wanted to run some code, but didn't want to take "Kubernetes mastery 101" For a small app using a managed service like Cloud Run plus some cloud storage should get you very far. I saw that Heroku is still popular with the indie community, with the author of Bannerbear ge
Read the rest
tting a lot of value from the managed platform. [1] https://thebootstrappedfounder.com/ [2] https://github.com/openfaas/faasd
In The architecture behind a one-person tech startup
I was joined by Taylor Dolezal for this live stream and was surprised to learn that Taylor has not only tried OpenFaaS before, but used it in two jobs - including at Disney. After the intro, we talk a bit about Go features like testing and newer features like generics, before going into a bit of a deep dive coding session, building up functions from scratch in Golang. The functions built with OpenFaaS are actually containers with a HTTP server inside, so they can be deployed to Kubernetes, Cloud Run or Knative in a similar way. They would probably also work with fly (but I haven't tried that yet) The "workload" definition is HTTP on port 8080 and a health check (configurable) https://docs.openfaas.com/reference/workloads/ For folks starting out with FaaS and not ready to go full-on K8s, faasd might be a good option to explore - https://gi
Read the rest
thub.com/openfaas/faasd - it has containerd and CNI (just like K8s) but no clustering so it's faster and has a sub-second cold-start.
In Introduction to Serverless Golang with OpenFaaS [video]
Disclaimer, I am a CNCF Ambassador (voluntary) - so it's in my interest to promote CNCF projects like Kubernetes. It seems like a good time to mention my blog post from last year "Then he asked me “Is Kubernetes right for us?" -> https://alexellisuk.medium.com/then-he-asked-me-is-kubernete... Some of the feedback I've had so far is that it was refreshing to get "permission" to consider alternatives vs. the current hype. I use K8s and K3s quite broadly myself, but increasingly see consulting prospects and customers who are not comfortable to make the leap, but are very happy on managed services with their chosen vendor - Azure / AWS / GCP. GitLab recently released a bunch of terraform to show you how to run side projects in the free tier of a cloud - https://gitlab.com/gitlab-org/5-minute-production-app/deploy... The OpenFaaS project again
Read the rest
is very coupled to Kubernetes, making it easier to use and more reliable is important to the community and project's future. However, we created a version called faasd that works more like docker-compose. It's received much more traction than we expected and companies and individuals are putting it into production. It does't have clustering, and supports only 1 replica per function, so it's surprising. https://github.com/openfaas/faasd I'll keep doing my bit to promote solutions that make K8s easier to understand like K3s (see also https://k3sup.dev) and to look into alternatives. But as you will see in my blog post - I don't think it's right to assume Kubernetes is the right solution for every team, and every project, without first talking about the problem being solved.
In Kubernetes Failure Stories
The latest addition here is to show how to capture screenshots from locally rendered HTML/CSS - perfect for social banners. Sites like Banner bear (no affiliation) are charging a fee for this kind of function, and all the better for it. Folks should charge for their work. But if you are comfortable hosting openfaas (3 EUR / mo on Hetzner using faasd) then you can do it a lot cheaper and run additional webhooks / APIs / blogs / integrations there too. A banner generation website will cost 49 USD / mo for 1000 images, 99 USD / mo for 10,000 images. Or 3 EUR / mo for faasd. https://github.com/openfaas/faasd
In Show HN: OpenFaaS template for headless Chrome and Puppeteer
Alex, OpenFaaS founder here. The author has done a huge amount of work here, I am surprised that it's being given away for free, and not being monetized (it should be). I often hear folks complain that Kubernetes is complex, and hard to understand. We've done a lot of work to make the experience of deploying functions simple on K8s, with very little to manage. But it still costs you a K8s cluster - most of our users don't mind that, because they have one anyway. But, for everyone else we created a new of openfaas called "faasd" which can run very well somewhere like DO or Hetzner for 3 EUR / mo. It doesn't include clustering, but is likely to be suitable for a lot of folks, who don't want to get deep into IAM territory. https://github.com/openfaas/faasd The REST API for OpenFaaS has a terraform provider that works with either version - ht
Read the rest
tps://github.com/ewilde/terraform-provider-openfaas And there's a guide on setting up faasd with TLS on DigitalOcean, it took about 30 seconds to launch, and makes building functions much simpler than Lambda. "faas-cli up" https://www.openfaas.com/blog/faasd-tls-terraform/ If I were going to use Lambda, the author's examples are probably what I would turn to, but there are other ways and it needn't be this complex.
In AWS Lambda Terraform Cookbook with working examples
K3s needs 500MB of RAM on a server and 50MB on an agent. That's the lowest we've ever seen for Kubernetes and Darren is planning on getting something working on 256MB SoC devices next. If you want to go ultra-lean, and only need a single node RPi or VPS (many applications don't need massive scale-out) then take a look at what we've been building with "faasd" and containerd - https://github.com/openfaas/faasd
In K0s – Zero Friction Kubernetes

Showing the 15 most recent of 25 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.