gitpod

gitpod-io/gitpod

The developer platform for on-demand cloud development environments to create software faster and more securely.

Ship status

Still shipping

Pushed in the last 30 days.

Last push
Oct 2, 2026
today
Ship score
77/100
How it is calculated →
Stars, last 7 weeks
Stars, weekly: 13,750 → 13,778 (Aug 18 – Sep 29, 2026)
+18 stars in the 28 days to 2026-09-29

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

Repo facts

What GitHub reports.

Stars
13.8K
Forks
1.4K
Open issues
449
Watchers
136
Primary language
TypeScript
Created
Apr 24, 2018
Owner
gitpod-io · Organization

Open issues are the issues and pull requests GitHub reports as open; watchers are the accounts subscribed to the repository. OSI-approved license — GitHub’s own license field, not legal advice. 208 startups in the directory ship primarily in TypeScript.

Topics

#cde#cloud#cloud-development#cloud-development-environments#cloud-ide#code-review#dev-environment#developer-environment#developer-experience#disposable#editor#ephemeral#gitpod#ide#jetbrains#prebuilds#remote-development#remote-devtools#vscode

How it got here

What the classifier decided, and when.

Classified as an open-source startup by Jev, TypeSafe’s classifier, on Sep 22, 2026 — os_startup 100%, self-hostable 45%, hosted offering 91%. 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.

Listed since the 2025-09 crawl. Answered by jev-1.13.0. How the classification works →

Embed your status

Put this badge on your README.

OSSEAN ship status: shipping — last push 2026-10-02This is the badge for gitpod-io/gitpod, as served from the URL below.
[![OSSEAN: shipping](https://ossean.com/badge/gitpod-io/gitpod.svg)](https://ossean.com/gitpod-io/gitpod)

Updates daily, from the last push GitHub saw.

Honest caveat: GitHub proxies README images through Camo and rewrites the anchor with rel=“nofollow”, so a README embed sends you referral traffic and brand, not link equity. The link is dofollow wherever you control the markup — your docs, your landing page, your blog. The snippet uses your frozen OSSEAN slug, so it survives a repo rename.