daytona

daytonaio/daytona

Daytona is a Secure and Elastic Infrastructure for Running AI-Generated Code

Ship status

Gone silent
Last push
Jul 24, 2026
90 days ago
Stars, last 7 weeks
Stars, weekly: 71,765 → 71,519 (Sep 8 – Oct 20, 2026)
−219 stars in the 28 days to 2026-10-20

GitHub reports this repository as archived. That forces the status to silent whatever the last push says.

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
71.5K
Forks
5.6K
Open issues
457
Watchers
130
Primary language
Unspecified
License
Unknown
Created
Feb 6, 2024
Owner
daytonaio · 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. This repo does not expose a primary language.

Topics

#agentic-workflow#ai#ai-agents#ai-runtime#ai-sandboxes#code-execution#code-interpreter#developer-tools

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 99%, self-hostable 48%, hosted offering 77%. 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: silent — last push 2026-07-24This is the badge for daytonaio/daytona, as served from the URL below.
[![OSSEAN: silent](https://ossean.com/badge/daytonaio/daytona.svg)](https://ossean.com/daytonaio/daytona)

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.