openfaas/faasd

Lightweight and portable version of OpenFaaS

View on GitHub ↗Jump to charts ↓

Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 1 hour ago
Added to GitGenius on September 21st, 2026
Created on December 20th, 2019
Open Issues & Pull Requests: 5 (+0)
GitHub issues: Enabled
Number of forks: 236
Total Stargazers: 3,275 (+0)
Total Subscribers: 32 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 36.4 hours
Mean response time: 73.6 days
90th percentile: 188.7 days
Tracked items: 4

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 0
New in 7 days: 0
Closed in 7 days: 0
Avg open age: N/A days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • invalid/template (1)
  • support (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

faasd is a lightweight serverless platform that reimplements OpenFaaS without requiring Kubernetes. It runs as a single Go binary on a single host, using containerd and Container Networking Interface for orchestration, and reuses the same core OpenFaaS components including the Gateway, Queue-Worker, and Event Connectors.

The tool solves the operational burden of running a serverless platform by eliminating the complexity and maintenance overhead of Kubernetes. Instead of managing a cluster, operators deploy faasd to a Linux host with modest requirements—as little as 2 vCPU and 2GB RAM—where it runs as a systemd service. The platform supports stateful containers with persistent volumes, allowing deployment of databases and monitoring tools alongside functions. It uses the same container images as OpenFaaS on Kubernetes, so existing function definitions and tooling remain compatible.

faasd suits teams building internal tools, automating tasks, and integrating with existing systems where Kubernetes overhead is unjustified. It works well for edge deployments and customer-facing scenarios where you can package functions into a VM image for distribution. The tool is available in two editions: a community edition for non-commercial use and a commercial edition for production deployments. Unlike Kubernetes-based OpenFaaS, faasd requires minimal ongoing maintenance and uses stable APIs that rarely change, making it suitable for scenarios where you want to deploy and leave the infrastructure untouched.

The project maintains active engagement with its user base through documentation, tutorials covering multiple languages including Node.js, Go, Python, and Java, and deployment guides for common workflows like GitHub Actions integration. Development activity shows consistent attention to both the core platform and the ecosystem of examples and integrations surrounding it.