fnproject/fn

The container native, cloud agnostic serverless platform.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 29 minutes ago
Added to GitGenius on September 11th, 2026
Created on July 18th, 2017
Open Issues & Pull Requests: 159 (+0)
GitHub issues: Enabled
Number of forks: 403
Total Stargazers: 5,946 (+0)
Total Subscribers: 183 (+0)

Repository Insights (GitGenius)

Most active contributors

Sign in to see contributor activity.

Related repositories by overlapping contributors

No overlapping-contributor repos identified yet.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 6
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 1,216 days
Stale 30+ days: 6
Stale 90+ days: 6

Recent activity

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

Top labels

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Fn is a Functions-as-a-Service platform that runs serverless workloads in containers and can be deployed anywhere.

Fn addresses the need to run serverless functions across different environments without vendor lock-in. It treats Docker containers as first-class functions, allowing developers to package code in any language and runtime. The platform handles function invocation, scaling, and orchestration while remaining agnostic to the underlying infrastructure, whether public cloud, private data center, or hybrid deployments.

Teams should adopt Fn if they want serverless capabilities without committing to a specific cloud provider's Lambda-like service. It suits organizations running Kubernetes or Docker Swarm who need to add event-driven compute to existing infrastructure, or those migrating from AWS Lambda who want to preserve function code while changing deployment targets. The platform explicitly supports importing Lambda functions and running them anywhere, making it valuable for multi-cloud strategies or on-premises deployments where managed serverless is unavailable.

The project maintains active development with regular updates to core functionality and tooling. The codebase shows ongoing refinement of container integration, including recent work on Podman and Rancher Desktop compatibility alongside Docker support. Documentation and operational guidance receive consistent attention, with separate repositories for documentation, a command-line interface, a web UI, and a workflow orchestration layer called Flow. The project sustains community engagement through Slack and GitHub discussions, indicating sustained investment in developer experience alongside platform stability.