fission/fission

Fast and Simple Serverless Functions for Kubernetes

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 17 minutes ago
Added to GitGenius on September 7th, 2026
Created on August 19th, 2016
Open Issues & Pull Requests: 47 (+0)
GitHub issues: Enabled
Number of forks: 793
Total Stargazers: 8,914 (+0)
Total Subscribers: 149 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Issue API getrepoissuespagesummary failed: 429 Rate limit exceeded. Please try again later.

Detailed Description

Fission is a serverless functions platform for Kubernetes that enables developers to deploy and run functions without managing container infrastructure directly.

Fission addresses the complexity of running functions on Kubernetes by abstracting away container and pod management. It allows developers to write functions in supported languages and deploy them as simple code, with the platform handling compilation, containerization, and scaling. The tool uses Kubernetes as its underlying runtime, leveraging its orchestration capabilities while presenting a simplified interface for function deployment and invocation.

Fission suits teams already operating Kubernetes clusters who want to add serverless capabilities without adopting an external managed service. It works well for organizations seeking to keep their infrastructure on-premises or within their own cloud accounts while gaining the developer experience benefits of functions-as-a-service. The project is particularly valuable for teams that want to avoid vendor lock-in and prefer managing their own Kubernetes environment. Those new to serverless or preferring managed solutions should evaluate whether running and maintaining a Fission cluster aligns with their operational capacity.

The project maintains active development with regular commits across its codebase. Pull requests receive timely review and integration. The maintainers engage consistently with issues, providing responses and guidance to users. Documentation is kept current alongside code changes. The project demonstrates sustained investment in both feature development and community support.