Suggestions appear as you type. Use the up and down arrows to choose one and Enter to open it.

This page's audience our own tag's counts — open to see them
–Visits
–Page views
–Clicks to vendors
–Time on page
–Reading now
Clicks to vendors, by tool
  • –
Top countries
  • –
Devices
  • –

– · visits, page views and clicks counted by our own tag, which counts more than our checked analytics; every figure rounded down · how we count

Fission review

Free#22 of 32 in Serverless HostingServerless Development FrameworksServerless Platforms

A Kubernetes-based framework for teams that want function triggers, autoscaling, and streaming.

7.3/10Editor score
Fission7.3 Visit Fission

Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026

Fission brings serverless-style functions to teams that want to run them on Kubernetes infrastructure they control. Developers can write short-lived functions, package them in language-specific runtime environments, and expose them through HTTP or event triggers. It supports Python, Node.js, Go, Rust, C#, and PHP, with deployment through its CLI and declarative application specifications. Fission fits teams comfortable operating Kubernetes; teams seeking a vendor-operated function hosting service should look elsewhere.

The execution model covers more than HTTP requests: triggers include timers, message queues, and Kubernetes events. Fission provisions function pods automatically and scales them, while streaming responses are supported over SSE, HTTP chunked transfer, and WebSocket. External routes can use Ingress or Gateway API, and Prometheus and Fluentd integrations support observability workflows. These features make it relevant when event handling or streaming belongs alongside Kubernetes workloads, rather than in a separate hosted service.

Fission is open source and self-hosted, with support for local clusters, public clouds, and private data centers. Its ecosystem includes Kubernetes, Istio, Redis, PostgreSQL, and etcd. That flexibility comes with an operational trade-off: teams remain responsible for the Kubernetes environment and its care, rather than handing infrastructure operations to a hosting vendor. Choose Fission when Kubernetes control, multiple trigger types, and streaming matter; choose a vendor-operated platform if reducing cluster administration is the priority.

Fission pros and cons

  • Where it wins
    • Supports HTTP, timer, message-queue, and Kubernetes event triggers
    • Streams responses over SSE, HTTP chunked transfer, or WebSocket
    • Integrates with Prometheus, Fluentd, Istio, Redis, PostgreSQL, and etcd
  • Where it doesn't
    • Requires teams to operate their own Kubernetes infrastructure
    • Function and package deployment is CLI-based
    • It is self-hosted rather than a vendor-operated hosting service

Fission fact sheet, pricing and score →

Advertiser disclosure: iTechGuides is reader-supported. Vendors can pay for top positions in our rankings and for a place on other products' pages, and we may earn a commission when you click some links. Bought places stand at the number bought; this page and our disclosure say so. Paying vendors may get a fuller, more detailed review from our editors, and that review can change their score. How we rank.

Last updated · How we research and update