apache/openwhisk

Apache OpenWhisk is an open source serverless cloud platform

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 58 minutes ago
Added to GitGenius on September 9th, 2026
Created on February 18th, 2016
Open Issues & Pull Requests: 430 (+0)
GitHub issues: Enabled
Number of forks: 1,181
Total Stargazers: 6,796 (+0)
Total Subscribers: 222 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 2.6 days
Mean response time: 55.9 days
90th percentile: 234.3 days
Tracked items: 35

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 28
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 629 days
Stale 30+ days: 28
Stale 90+ days: 26

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Apache OpenWhisk is a serverless functions platform that enables developers to build cloud applications by executing code in response to events without managing infrastructure.

The platform addresses the need to run application logic without provisioning or maintaining servers. OpenWhisk works by allowing developers to define functions, compose them into workflows, and connect them to events through rules and triggers. Functions execute within Docker containers, and the platform handles scaling and resource allocation automatically. The system supports a rich programming model where multiple functions can be chained together to create serverless workflows and APIs.

Developers should choose OpenWhisk for projects requiring event-driven architectures or microservices that benefit from automatic scaling. The platform suits teams building cloud applications who want to avoid server management overhead. It works well for organizations deploying on Kubernetes in development or production environments, as well as those starting with the Standalone deployment option that runs as a single Java process for convenience. The Playground browser interface allows rapid prototyping and testing of functions directly without command-line setup, though the full feature set requires the command-line tool for production use.

The project has undergone significant architectural changes, most notably migrating from the Akka framework to Apache Pekko, which requires redeployment of clusters and updates to configuration files. This represents a breaking change that affects existing deployments. The project maintains multiple deployment paths including Docker-based options for different operating systems and Kubernetes-native deployment, indicating active support for diverse infrastructure choices. Development activity spans both the core platform and tooling, with documentation covering CLI configuration, concepts, and deployment procedures across different environments.