Platform Comparison

evrtng functions vs. the Cloud Giants

How does evrtng functions — powered by Fission — compare to AWS Lambda, Google Cloud Functions, and Azure Functions? Here's the honest breakdown.

Feature Matrix

Side-by-Side Comparison

Feature evrtng functions
Fission + Firecracker 		AWS Lambda
Amazon Web Services 		Cloud Functions
Google Cloud 		Azure Functions
Microsoft
// PRICING
Requests CHF 0.20 / 1M CHF 0.20 / 1M CHF 0.40 / 1M CHF 0.20 / 1M
Compute (GB·s) CHF 0.0000167 CHF 0.0000166667 CHF 0.0000100 CHF 0.000016
Free Tier (requests) 30K / month 1M / month 2M / month 1M / month
Idle cost CHF 0.00 CHF 0.00 CHF 0.00 CHF 0.00
Pricing model Subscription Pay-per-use Pay-per-use Pay-per-use / Premium
evrtng prices in CHF, incl. 8.1% VAT. Cloud provider prices in USD.
// LANGUAGES & RUNTIMES
JavaScript / Node.js ✓ ✓ ✓ ✓
Python ✓ ✓ ✓ ✓
Java ✓ ✓ ✓ ✓
Go ✓ ✓ ✓ ✓
PHP ✓ ✗ ✓ ✓
Ruby ✓ ✓ ✗ ✗
.NET / C# / F# ✗ ✓ ✗ ✓
Rust ✓ (Docker) ✓ (custom) ✗ ✗
ANSI C ✓ (Docker) ✓ (custom) ✗ ✗
Custom Docker Runtime ✓ Native ✓ Container Image ✗ ✓ (Premium)
Total official runtimes 7 + Docker 9 6 7
// ARCHITECTURE & FEATURES
Event-driven triggers ✓ HTTP, Cron (Kafka on request) ✓ HTTP, S3, SQS, DynamoDB… ✓ HTTP, Pub/Sub, Firestore ✓ HTTP, Queue, Event Hub
HTTP Triggers / endpoints ✓ Built-in ✓ via API Gateway ✓ Built-in ✓ Built-in
Max execution time 5 min (max) 15 min 60 min (2nd gen) 10 min (Consumption)
Max memory 1,024 MB 10,240 MB 16,384 MB 1,536 MB
Cold start performance ~0.15s warm ~100–500ms ~100–400ms ~200ms–2s
Concurrent executions 200 1,000 (default, scalable) 3,000 (regional) Unlimited (Consumption)
Open Source platform ✓ Fission (Apache-2.0) ✗ Proprietary ✗ Proprietary ✓ Partially (host)
Self-hostable ✓ Full control ✗ ✗ ✓ via Docker
Vendor lock-in Low (open standard) High High Medium
CLI tooling REST API aws CLI / SAM gcloud CLI Azure CLI / Core Tools
Local development ✓ curl / any HTTP client ✓ SAM Local ✓ Functions Framework ✓ Core Tools

// Data reflects platform capabilities as of 2025/2026. Pricing may vary by region and tier.

Why evrtng functions

Where evrtng functions Stands Out

Most Languages

7 verified runtimes plus any custom Docker image. PHP, Ruby, Go, ANSI C — languages other platforms dropped or never supported.

No Vendor Lock-in

Built on Fission — open source under Apache-2.0 and Kubernetes-native. Your functions are plain code and Docker images. Take your code and go.

Firecracker Isolation

Every function runs in its own Firecracker micro-VM — hardened isolation no hyperscaler offers at this price. Your neighbours never share your kernel.

Flexible Triggers

HTTP and cron triggers — connect events without proprietary glue services. Kafka integration on request.

Tenant URLs Built-in

Every function gets its own URL under {namespace}.fnc4.evrtng.cloud with TLS, rate limiting, and billing built in. No API Gateway required.

Battle-tested Core

Built on Fission, a Kubernetes-native open-source project under the Apache Software Foundation — hardened with Kata Containers and Firecracker micro-VMs.

Decision Guide

When to Choose evrtng functions

✓ Great fit if you…

Need PHP, Ruby, Go, or ANSI C runtime support
Want to avoid vendor lock-in with an open-source platform
Require custom Docker-based runtimes for niche languages
Want to self-host or run on Kubernetes later
Prefer transparent subscription billing with no surprises

→ Consider alternatives if you…

Need deep integration with AWS services (S3, DynamoDB, SQS…)
Are building stateful long-running workflows (→ Azure Durable Functions)
Need native Google Cloud integration (BigQuery, Pub/Sub, Spanner) (→ Google Cloud Functions)
Require enterprise compliance certifications on day one
// ready to try?

Deploy your first function today

No credit card for the first deployment. Transparent billing from request one.

$ quick start → see pricing