Discofork
Repository brief

Dokploy/dokploy

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis
cached 2026-03-30T19:50:40.210Z
1mo ago

Dokploy/dokploy

Dokploy/dokploy is an actively maintained, popular open source self-hosted PaaS positioned as an alternative to Vercel, Netlify, and Heroku. It has strong adoption signals for fork research: 32,470 stars, 2,280 forks, a non-archived repo, and very recent activity on 2026-03-30. The repository is a pnpm-based Node.js monorepo with apps/ and packages/ workspaces, multiple Dockerfiles, and an API/openapi.json, suggesting a broad, production-oriented platform rather than a small utility.

GitHub
Loading tags...
Stars32,470
Forks2,280
Default branchcanary
Last pushed2026-03-30T15:11:15Z
Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs
Selected

Prefer upstream unless you specifically need an old frozen baseline. This fork adds no visible capabilities, is far behind upstream, and appears stale.

Prefer upstream unless you specifically need an old, unmodified snapshot. This fork offers no clear added capability and is far behind on fixes and operational improvements.

Choose this fork only if blank issues are the specific change you want and you are comfortable inheriting a very stale upstream snapshot. For product adoption, the upstream branch is the safer default.

Adopt this only if you explicitly want a frozen upstream snapshot. If you want a maintained or value-added fork, this is not it.

Choose this fork only if you explicitly need the older state; otherwise upstream is the better option because this fork adds nothing visible and is far behind.

Prefer upstream Dokploy unless you explicitly need this old snapshot; this fork shows no added functionality and is far behind current development.

Prefer upstream unless you specifically need this old snapshot; this fork adds no visible capabilities and is too far behind for normal adoption.

This is not a differentiated fork; it is an old, inactive snapshot that has fallen far behind an actively maintained upstream. Most adopters should prefer upstream unless they specifically need a frozen baseline.

Choose this fork only if you want an essentially unmodified Dokploy snapshot. If you want the newest upstream fixes or any differentiated workflow, upstream itself is the better default.

Choose this fork only if you need a pinned copy of Dokploy; otherwise upstream is the better default because this fork adds nothing and is already behind on fixes.