I haven't actually tried Pegasus, so I can't say exactly. In a lot of ways I'm sure they're similar. Some differences with Forge might be the removal of options: - Pegasus looks like it supports multiple CSS frameworks, Forge only comes with Tailwind - Pegasus talks about multiple deployment options, Forge focuses completely on Heroku - Pegasus talks about creating venvs or using virtualenvwrapper (+ pip-compile?), Forge uses Poetry

From what I understand, the update process for Pegasus is also a little bit more manual? Forge is intentionally set up to be a git remote, with directories and stuff named so that an update is essentially `git merge django-forge/main`.

Probably lots of little differences when you get into it — just different decisions from different people. Hoping to document more of Forge soon!