// the take
faasd is OpenFaaS stripped down to a single Go binary that runs functions on containerd + CNI instead of Kubernetes — one systemd service on a VM or Pi instead of a cluster. It's for people who want FaaS-style deployment (HTTP-triggered containers, scale-to-zero, a function store) without paying the Kubernetes complexity tax.
It reuses the actual OpenFaaS gateway, queue-worker and templates, so functions you write for faasd deploy unchanged to full OpenFaaS on k8s later — real migration path, not a toy subset. Stateful containers with persistent volumes (Postgres, Grafana, Prometheus) are supported, so it's not limited to pure stateless functions. Resource footprint is genuinely small (2 vCPU/2GB RAM claimed), and there's a solid set of deployment recipes (Terraform for DigitalOcean, cloud-init, multipass, Raspberry Pi) that go beyond a thin README.
The license split matters a lot and isn't obvious from the repo blurb: faasd CE is personal/non-commercial only under its own EULA, and any commercial use requires a paid OpenFaaS Edge license — this is not a free-to-run-your-business FaaS platform. It's single-host by design, so there's no built-in HA or horizontal scaling story; outgrowing one box means moving to full OpenFaaS on k8s, not scaling faasd itself. CNI networking setup on the host (namespaces, bridge config) is still manual plumbing you're responsible for, closer to 'light infra work' than 'install and forget'. Running production workloads also means keeping containerd itself patched and compatible, since faasd doesn't abstract that dependency away.
We read the README, the directory tree and a key source file in November 2026. Nobody pays to be listed. How we judge →