StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. Application & Data
  3. Serverless
  4. Serverless Task Processing
  5. Fission vs Knative vs Kubeless

Fission vs Knative vs Kubeless

OverviewComparisonAlternatives

Overview

Fission
Fission
Stacks27
Followers81
Votes3
GitHub Stars8.8K
Forks788
Kubeless
Kubeless
Stacks39
Followers195
Votes0
Knative
Knative
Stacks86
Followers342
Votes21
GitHub Stars5.9K
Forks1.2K

Fission vs Knative vs Kubeless: What are the differences?

Introduction

Fission, Knative, and Kubeless are serverless frameworks that allow developers to build and deploy applications without having to manage infrastructure. While they share the same goal of simplifying the development process, there are key differences between them. In this article, we will discuss the differences between Fission, Knative, and Kubeless in detail.

  1. Programming Language Support: Fission supports a wide range of programming languages including Python, Node.js, Go, and Ruby. Knative, on the other hand, supports multiple languages including Java, Node.js, Python, Ruby, and .NET. Kubeless also supports various languages like Python, Node.js, Ruby, and PHP.

  2. Integration with Kubernetes: Fission is specifically designed to work with Kubernetes and utilizes Kubernetes primitives extensively. Knative is built on top of Kubernetes and provides higher-level abstractions for serverless deployments. Kubeless is also built on top of Kubernetes, integrating seamlessly with Kubernetes resources like Services and Ingress.

  3. Event Triggering: Fission uses Kubernetes events to trigger function execution, making it easy to integrate with other Kubernetes components. Knative provides a more flexible eventing model, supporting different event sources and allowing for complex event-driven workflows. Kubeless supports event triggers through PubSub mechanisms, enabling easy integration with messaging systems like Kafka and NATS.

  4. Scaling: Fission and Kubeless both support automatic scaling of function instances based on workload. Knative, in addition to automatic scaling, also provides scale-to-zero capabilities, meaning functions are scaled down to zero instances when not in use, resulting in cost savings.

  5. Community Support: Fission is an open-source project with a smaller community compared to Knative and Kubeless, which have larger user bases and active developer communities. Knative, being a Cloud Native Computing Foundation (CNCF) project, benefits from the resources and support of the CNCF community.

  6. Vendor Lock-in: Fission and Kubeless are cloud platform-agnostic, allowing deployment on any Kubernetes cluster. Knative, being part of the larger Kubernetes ecosystem, offers more flexibility in terms of deployment options and reduces vendor lock-in.

In summary, Fission, Knative, and Kubeless are serverless frameworks with varying capabilities. Fission is tightly integrated with Kubernetes, Knative offers advanced eventing and scaling capabilities, and Kubeless provides flexible language support and easy integration with messaging systems. The choice between them depends on specific requirements and preferences of developers and organizations.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs
CLI (Node.js)
or
Manual

Detailed Comparison

Fission
Fission
Kubeless
Kubeless
Knative
Knative

Write short-lived functions in any language, and map them to HTTP requests (or other event triggers). Deploy functions instantly with one command. There are no containers to build, and no Docker registries to manage.

Kubeless is a Kubernetes native serverless Framework. Kubeless supports both HTTP and event based functions triggers. It has a serverless plugin, a graphical user interface and multiple runtimes, including Python and Node.js.

Knative provides a set of middleware components that are essential to build modern, source-centric, and container-based applications that can run anywhere: on premises, in the cloud, or even in a third-party data center

--
Serving - Scale to zero, request-driven compute model; Build - Cloud-native source to container orchestration; Events - Universal subscription, delivery and management of events; Serverless add-on on GKE - Enable GCP managed serverless stack on Kubernetes
Statistics
GitHub Stars
8.8K
GitHub Stars
-
GitHub Stars
5.9K
GitHub Forks
788
GitHub Forks
-
GitHub Forks
1.2K
Stacks
27
Stacks
39
Stacks
86
Followers
81
Followers
195
Followers
342
Votes
3
Votes
0
Votes
21
Pros & Cons
Pros
  • 1
    Open source
  • 1
    Portability
  • 1
    Any language
No community feedback yet
Pros
  • 5
    Portability
  • 4
    Autoscaling
  • 3
    Eventing
  • 3
    Secure Eventing
  • 3
    On top of Kubernetes
Integrations
Kubernetes
Kubernetes
Docker
Docker
Docker
Docker
Kafka
Kafka
Zookeeper
Zookeeper
Serverless
Serverless
Kubernetes
Kubernetes
Google Kubernetes Engine
Google Kubernetes Engine

What are some alternatives to Fission, Kubeless, Knative?

AWS Lambda

AWS Lambda

AWS Lambda is a compute service that runs your code in response to events and automatically manages the underlying compute resources for you. You can use AWS Lambda to extend other AWS services with custom logic, or create your own back-end services that operate at AWS scale, performance, and security.

Azure Functions

Azure Functions

Azure Functions is an event driven, compute-on-demand experience that extends the existing Azure application platform with capabilities to implement code triggered by events occurring in virtually any Azure or 3rd party service as well as on-premises systems.

Google Cloud Run

Google Cloud Run

A managed compute platform that enables you to run stateless containers that are invocable via HTTP requests. It's serverless by abstracting away all infrastructure management.

Serverless

Serverless

Build applications comprised of microservices that run in response to events, auto-scale for you, and only charge you when they run. This lowers the total cost of maintaining your apps, enabling you to build more logic, faster. The Framework uses new event-driven compute services, like AWS Lambda, Google CloudFunctions, and more.

Google Cloud Functions

Google Cloud Functions

Construct applications from bite-sized business logic billed to the nearest 100 milliseconds, only while your code is running

OpenFaaS

OpenFaaS

Serverless Functions Made Simple for Docker and Kubernetes

Nuclio

Nuclio

nuclio is portable across IoT devices, laptops, on-premises datacenters and cloud deployments, eliminating cloud lock-ins and enabling hybrid solutions.

Apache OpenWhisk

Apache OpenWhisk

OpenWhisk is an open source serverless platform. It is enterprise grade and accessible to all developers thanks to its superior programming model and tooling. It powers IBM Cloud Functions, Adobe I/O Runtime, Naver, Nimbella among others.

Cloud Functions for Firebase

Cloud Functions for Firebase

Cloud Functions for Firebase lets you create functions that are triggered by Firebase products, such as changes to data in the Realtime Database, uploads to Cloud Storage, new user sign ups via Authentication, and conversion events in Analytics.

AWS Batch

AWS Batch

It enables developers, scientists, and engineers to easily and efficiently run hundreds of thousands of batch computing jobs on AWS. It dynamically provisions the optimal quantity and type of compute resources (e.g., CPU or memory optimized instances) based on the volume and specific resource requirements of the batch jobs submitted.

Related Comparisons

Bootstrap
Materialize

Bootstrap vs Materialize

Laravel
Django

Django vs Laravel vs Node.js

Bootstrap
Foundation

Bootstrap vs Foundation vs Material UI

Node.js
Spring Boot

Node.js vs Spring-Boot

Liquibase
Flyway

Flyway vs Liquibase