faasd is OpenFaaS reimagined, but without the cost and complexity of Kubernetes. It runs on a single host with very modest requirements, making it fast and easy to manage. Under the hood it uses containerd and Container Networking Interface (CNI) along with the same core OpenFaaS components from the main project.
faasd is just another way to run OpenFaaS, so many things you read in the docs or in blog posts will work the same way.
Videos and overviews:
Use-cases and tutorials:
Additional resources:
x86_64
and Arm out the boxdocker-compose.yaml
file like Grafana, MongoDB, InfluxDB, or Postgres, etcMost importantly, it's easy to manage so you can set it up and leave it alone to run your functions.
Demo of faasd running asynchronous functions
Watch the video: faasd walk-through with cloud-init and Multipass
By default faasd comes with the Community Edition (CE) components, but if you like, you can purchase a license to upgrade to OpenFaaS Standard with scale to zero and rich support for async use-cases through the JetStream queue worker.
faasd relies on industry-standard tools for running containers:
You can use the standard faas-cli along with pre-packaged functions from the Function Store, or build your own using any OpenFaaS template.
faasd does not create the same maintenance burden you'll find with maintaining, upgrading, and securing a Kubernetes cluster. You can deploy it and walk away, in the worst case, just deploy a new VM and deploy your functions again.
You can learn more about supported OpenFaaS features in the ROADMAP.md
The faasd project is MIT licensed and open source, and you will find some documentation, blog posts and videos for free.
"Serverless For Everyone Else" is the official handbook and was written to contribute funds towards the upkeep and maintenance of the project.
You'll learn how to deploy code in any language, lift and shift Dockerfiles, run requests in queues, write background jobs and to integrate with databases. faasd packages the same code as OpenFaaS, so you get built-in metrics for your HTTP endpoints, a user-friendly CLI, pre-packaged functions and templates from the store and a UI.
Topics include:
View sample pages, reviews and testimonials on Gumroad:
"Serverless For Everyone Else"
The easiest way to deploy faasd is with cloud-init, we give several examples below, and post IaaS platforms will accept "user-data" pasted into their UI, or via their API.
For trying it out on MacOS or Windows, we recommend using multipass to run faasd in a VM.
If you don't use cloud-init, or have already created your Linux server you can use the installation script as per below:
git clone https://github.com/openfaas/faasd --depth=1
cd faasd
./hack/install.sh
This approach also works for Raspberry Pi when using the 64-bit OS or Ubuntu 22.04 or higher.
It's recommended that you do not install Docker on the same host as faasd, since 1) they may both use different versions of containerd and 2) docker's networking rules can disrupt faasd's networking. When using faasd - make your faasd server a faasd server, and build container image on your laptop or in a CI pipeline.
Terraform scripts:
For community functions see faas-cli store --help
For templates built by the community see: faas-cli template store list
, you can also use the dockerfile
template if you just want to migrate an existing service without the benefits of using a template.
Commercial users and solo business owners should become OpenFaaS GitHub Sponsors to receive regular email updates on changes, tutorials and new features.
If you are learning faasd, or want to share your use-case, you can join the OpenFaaS Slack community.
For open backlog items, shipped features, design limitations and any known issues, see ROADMAP.md
Want to build a patch without setting up a complete development environment? See docs/PATCHES.md
Are you looking to hack on faasd? Follow the developer instructions for a manual installation, or use the hack/install.sh
script and pick up from there.