oblien/openship

Self-hosted deployment platform

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 10 minutes ago
Added to GitGenius on September 1st, 2026
Created on March 5th, 2026
Open Issues & Pull Requests: 212 (+0)
GitHub issues: Enabled
Number of forks: 1,095
Total Stargazers: 12,175 (+0)
Total Subscribers: 37 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 5.1 hours
Mean response time: 36.7 hours
90th percentile: 5.6 days
Tracked items: 324

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 85% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Almost all tracked open issues have seen activity in the last three months. Only 19% of issues opened in the past year have been closed. Three people close 96% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 106
New in 7 days: 26
Closed in 7 days: 50
Avg open age: 22 days
Stale 30+ days: 45
Stale 90+ days: 0

Recent activity

Opened in 7 days: 26
Closed in 7 days: 48
Comments in 7 days: 15
Events in 7 days: 62

Top labels

  • bug (4)
  • enhancement (1)

Detailed Description

Openship is a self-hosted deployment platform that enables teams to manage application deployments within their own infrastructure.

The platform addresses the need for deployment automation without relying on external cloud services. It provides a self-contained solution where organizations can control their entire deployment pipeline, from configuration through execution, while maintaining data and operations within their own environment. The approach centers on giving users direct access to deployment management tools rather than delegating control to third-party platforms.

Teams evaluating Openship should consider it if they require deployment infrastructure that remains under their direct control and operates independently of external service providers. It suits organizations with existing infrastructure who want to integrate deployment capabilities without adopting additional cloud dependencies. The project is particularly relevant for teams prioritizing data sovereignty or operating in environments where external platform dependencies are not feasible.

The project shows consistent development activity with regular commits and ongoing refinement of its codebase. The maintainers actively respond to issues and incorporate feedback into the platform. The tool receives periodic updates that address both bug fixes and feature enhancements. Development appears focused on stability and usability improvements rather than rapid feature expansion.