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 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.
x86_64and ARM out the box
Demo of faasd running in KVM
faasd is OpenFaaS, so many things you read in the docs or in blog posts will work the same way.
Use-cases and tutorials:
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 out fasad on MacOS or Windows, we recommend using multipass.
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 cd faasd ./hack/install.sh
This approach also works for Raspberry Pi
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.
The terraform can be adapted for any IaaS provider:
You can run this tutorial on your Raspberry Pi, or adapt the steps for a regular Linux VM/VPS host.
Automate everything within < 60 seconds and get a public URL and IP address back. Customise as required, or adapt to your preferred cloud such as AWS EC2.
faasd is a portable, and open source serverless engine. It runs a number of core services for its REST API, for background processing, and for metrics. The project schedules functions with containerd directly, and supports scale to and from zero, but without the need for clustering or Kubernetes.
It makes for a quick and easy way to start hosting APIs and websites, benefiting from containers and cloud native technology without having to manage Kubernetes, or pay significant hosting costs.
This handbook is written for those deploying faasd to self-hosted or cloud infrastructure. Whilst OpenFaaS has reference documentation, here we focus on everything you need to know about faasd itself.
faasd users can upgrade to Kubernetes when the need presents itself and can bring their functions with them.
You can view the logs of functions using
journalctl -t openfaas-fn:FUNCTION_NAME faas-cli store deploy figlet journalctl -t openfaas-fn:figlet -f & echo logs | faas-cli invoke figlet
You'll also need:
You can use the standard faas-cli along with pre-packaged functions from the Function Store, or build your own using any OpenFaaS template.
"Serverless For Everyone Else" is the complete guide and documentation for faasd. If you're looking for how to do something, it's likely that the book covers it.
The OpenFaaS docs provide a wealth of information for OpenFaaS on Kubernetes, and are likely to be useful for you, even using faasd.
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.
The founder of faasd and OpenFaaS has written a training course for the LinuxFoundation which also covers how to use OpenFaaS on Kubernetes. Much of the same concepts can be applied to faasd, and the course is free:
The OpenFaaS workshop is a set of 12 self-paced labs and provides a great starting point for learning the features of openfaas. Not all features will be available or usable with faasd.
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 completed features, WIP and upcoming roadmap see: