| Price from | — | — |
| Free plan | — | — |
| Free trial | — | Yes |
| Open source | — | — |
| Web | — | Yes |
| Windows | Yes | Yes |
| macOS | Yes | Yes |
| Linux | Yes | Yes |
| API | Yes | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 0 | 0 |
| Spec score · Serverless Platforms | 7.7 (#12) | 7.6 (#13) |
| Deployment | Fission deploys functions with one command without requiring users to build containers or manage Docker registries. | Nuclio can run as a standalone Docker container or on a Kubernetes cluster. |
| Event sources | The docs list message queue trigger integrations for Apache Kafka, AWS SQS, AWS Kinesis, GCP Pub/Sub, NATS, RabbitMQ, and Redis Lists. | The documentation lists triggers for Cron, Azure Event Hub, HTTP, Kafka, Kinesis, MQTT, NATS, NATS JetStream, RabbitMQ, and v3ioStream. |
| Portability | Fission runs on Kubernetes clusters on laptops, public clouds, or private data centers. | The maker describes Nuclio as portable across laptops, edge devices, on-premises environments, and multiple clouds. |
| Security | Function invocation authentication is optional and can be enabled on the Fission Router using tokens passed in an Authorization header. | Nuclio supports function authentication on Kubernetes deployments, but it is disabled by default unless enabled in platform configuration. |
| Support | The project directs users to its Slack community and provides troubleshooting guides and a CLI command for collecting support diagnostics. | The documentation directs users to the Nuclio Slack workspace for support and additional product information. |
| Triggers | Documented trigger types include HTTP, timers, message queues through KEDA, and Kubernetes watches. | Documented trigger types include HTTP, cron, Azure Event Hub, Kafka, Kinesis, MQTT, NATS, NATS JetStream, RabbitMQ, and v3ioStream. |
