Fission

What it is

Fission is an open-source, Kubernetes-native serverless framework. It lets you deploy functions (not containers you build and push yourself) and have Fission handle the packaging, routing, and scaling on top of your existing cluster. It uses a "pool of warm containers" model to keep cold starts low compared to spinning up a full pod per invocation, which is the core technical bet the project makes. Supports multiple language runtimes via executor environments, event triggers (HTTP, message queues, timers, Kubernetes watch events), and integrates with Prometheus for metrics.

Category: Serverless. If you're picturing "OpenFaaS but with a different pooling strategy," you're not far off.

Who builds it and why

Originally created by Platform9 Systems. Description of current governance/backing is not publicly available, but the GitHub activity tells a real story: 182 contributors and commits landing as recently as mid-2026 indicate this isn't an abandoned side project — there's an active maintainer base keeping it alive, even if it's not a headline CNCF project. CNCF maturity level is not publicly available, which suggests it may be an unaffiliated or early-stage project rather than a graduated/incubating CNCF one — verify this directly before assuming any CNCF backing in procurement conversations.

Production readiness signal

• 8,870 GitHub stars — solid, mid-tier adoption for a serverless-on-K8s tool. Not Knative-scale, but a real community.
• 182 contributors — healthy breadth; this isn't a single-maintainer bus-factor risk.
• Last commit 2026-06-30 — actively maintained, not stale.
• v1.27.0 — a mature version number suggesting years of iterative releases, not a v0.x experiment.
• Apache-2.0, written in Go — standard, unrestrictive licensing and a language fit for cloud-native tooling.
• CNCF maturity and founding date are not publicly available — do your own diligence on governance stability before betting critical infra on it.

Net signal: this is a living project with real contributors, not vaporware, but it's not a top-tier CNCF graduated project with the scrutiny that implies.

Who should use this

• Teams already running Kubernetes who want FaaS ergonomics (deploy a function, not a Dockerfile) without adopting a separate cloud provider's Lambda/Cloud Functions.
• Platform teams building internal developer platforms who want to offer "serverless" as a self-service option on existing cluster capacity.
• Event-driven workloads with bursty, unpredictable traffic where the warm-pool model meaningfully reduces cold-start latency versus scale-from-zero container platforms.
• Organizations wanting to avoid vendor lock-in to AWS/GCP/Azure serverless offerings while staying Kubernetes-native.

Who should NOT use this

• Teams with no existing Kubernetes footprint — you'd be adopting K8s complexity just to get Fission, which is a bad trade if you could just use managed cloud FaaS directly.
• Anyone needing enterprise SLAs, support contracts, or vendor accountability — there's no clear commercial backing here; you own the operational risk.
• Shops already invested in Knative or Kubeless-adjacent tooling — migrating serverless frameworks has real cost, and Fission's differentiation (warm pools) may not justify a switch.
• Teams needing broad, actively-certified compliance postures (SOC2, FedRAMP) — with CNCF maturity and organizational backing not publicly documented, this is a gap you'll need to fill yourself.
• Very large-scale, multi-region serverless deployments — Fission's community scale doesn't have the same battle-testing at hyperscale as AWS Lambda or GCP Cloud Run.

Alternatives

• Knative — CNCF-backed, broader ecosystem support, scale-to-zero via a different (request-driven) model; heavier to operate.
• OpenFaaS — similar FaaS-on-Kubernetes premise, larger community, has both OSS and commercial (OpenFaaS Pro) tiers.
• AWS Lambda / GCP Cloud Functions — fully managed, no cluster to run, but locks you into a specific cloud and loses the Kubernetes-native portability story.

Pricing

Fully open source under Apache-2.0. No license fees. You pay only for the Kubernetes infrastructure you run it on and your own operational time — there's no visible commercial tier, support contract, or hosted offering publicly documented.