Fission vs Fn Project
Fission
fission.ioFn Project
fnproject.ioSide by side
| Figure | Fission | Fn Project |
|---|---|---|
| Price from | — | Free |
| Free plan | — | Yes |
| Free trial | — | — |
| Open source | — | — |
| Windows | Yes | Yes |
| macOS | Yes | Yes |
| Linux | Yes | Yes |
| API | Yes | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 0 | 1 |
| Spec score · Serverless Platforms | 7.7 (#12) | 7.9 (#9) |
| Deployment options | Fission runs on Kubernetes clusters on a laptop, in a public cloud, or in a private data center. | Fn can run on public, private, and hybrid cloud, as well as on-premise. |
| Integrations | The homepage says Fission integrates with Fluentd for CLI logs, Prometheus for metrics, and Istio for service mesh monitoring and tracing. | Fn can run with Docker, Podman, or Rancher Desktop; its docs also list a Kubernetes Helm chart. |
| License | Fission is open source under the Apache License. | The Fn documentation repository identifies its license as Apache-2.0. |
| Support | The project directs users to its Slack community and provides troubleshooting guides and a CLI command for collecting support diagnostics. | The project directs users to Stack Overflow and its Slack community for help. |
| What it does | Fission is an open-source framework for running serverless functions on Kubernetes and mapping them to HTTP requests or other event triggers. | Fn is an open-source, event-driven Functions-as-a-Service compute platform. |
Plans
In their own words
Fn Project
Fn Project has no write-up on Specifiction yet; its figures are above.