InvokeAI

invoke-ai/InvokeAI

Invoke is a leading creative engine for Stable Diffusion models, empowering professionals, artists, and enthusiasts to generate and create visual media using the latest AI-driven technologies. The solution offers an industry leading WebUI, and serves as the foundation for multiple commercial products.

Ship status

Still shipping

Pushed in the last 30 days.

Last push
Oct 3, 2026
today
Ship score
88/100
How it is calculated →
Stars, last 7 weeks
Stars, weekly: 27,912 → 28,309 (Aug 18 – Sep 29, 2026)
+219 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
28.3K
Forks
3K
Open issues
388
Watchers
211
Primary language
TypeScript
Created
Aug 17, 2022
Owner
invoke-ai · 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

#ai-art#artificial-intelligence#generative-art#image-generation#img2img#inpainting#latent-diffusion#linux#macos#outpainting#stable-diffusion#txt2img#windows

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 97%, self-hostable 80%, hosted offering 45%. 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-03This is the badge for invoke-ai/InvokeAI, as served from the URL below.
[![OSSEAN: shipping](https://ossean.com/badge/invoke-ai/InvokeAI.svg)](https://ossean.com/invoke-ai/InvokeAI)

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.