rainbond

goodrain/rainbond

Rainbond is an open-source container platform that requires no Kubernetes expertise. Its core capabilities are 100% open source. It abstracts away infrastructure complexity and provides a unified way to deploy and manage business applications, AI-generated projects, open-source AI software, and large language model services. AI helps teams deploy

Ship status

Still shipping

Pushed in the last 30 days.

Last push
20 Nov 2026
today
Ship score
73/100
How it is calculated →
Stars, last 7 weeks
no history yet
No weekly sample has been taken for this repository yet.

Shipping: pushed in the last 30 days · slowed: quiet for 31–120 days · silent: no push in over 120 days.

Repository facts

Stars
6.3K
Forks
882
Open issues
62
Watchers
161
Primary language
Go
License
Other
Created
5 Nov 2017
Owner
goodrain · Organization

Open issues are the issues and pull requests GitHub reports as open; watchers are the accounts subscribed to the repository. License unknown — GitHub’s own license field, not legal advice. 133 startups in the directory ship primarily in Go.

Topics

#ai-applications#application-delivery#application-runtime#cloud-native#devops#kubernetes#paas#platform-engineering#private-deployment#self-hosted

How Jev classified this project

Classified as an open-source startup by Jev, TypeSafe’s classifier, on 19 Nov 2026 — os_startup 98%, self-hostable 85%, hosted offering 70%. The classifier reads only the repository’s name, description and homepage; it can be wrong, and a probability under 0.5 puts a listing in the review queue rather than out of the directory.

Joined the directory 19 Nov 2026, found by the weekly discovery job at confidence 0.97. Answered by jev-1.14.0. How the classification works →

Add the status badge to your README

OSSEAN ship status: shipping — last push 20 Nov 2026This is the badge for goodrain/rainbond, as served from the URL below.
[![OSSEAN: shipping](https://ossean.com/badge/goodrain/rainbond.svg)](https://ossean.com/goodrain/rainbond)

Updates daily, from the last push GitHub saw.

The badge links to this profile, even after a GitHub rename. GitHub caches README images, so the badge can take a little longer to update there.