head to head · open source

grocy vs packj

grocy has 9,646 GitHub stars, 828 forks, 135 open issues and last shipped 2 months ago. packj has 694 stars, 38 forks, 14 open issues and last shipped 2 months ago. grocy leads on adoption by 1,290% (9,646 vs 694 stars). grocy is written in Blade under MIT; packj is written in Python under AGPL-3.0. grocy has attracted 9% as many forks as stars, packj 5%. packj was the more recently maintained of the two, and both are self-hostable with no licence fee.

Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.

grocy ★ 9.6K packj ★ 694 category Business Software

← all 20902 open source comparisons

Side by side

grocy packj
GitHub stars ★ 9.6K ★ 694
License MIT AGPL-3.0
Written in Blade Python
Last push 2026-09-16 2026-09-17
Forks ⑂ 828 ⑂ 38
Self-hosting Yes Yes
Data ownership Your server Your server

pick grocy if

  • You weight community size — 9.6K stars and counting
  • You want the MIT license terms
  • Your stack matches Blade
  • You value the larger contributor base for long-term maintenance

full grocy profile →

pick packj if

  • You want the packj feature set and don't need the biggest community
  • You prefer the AGPL-3.0 license terms
  • Your stack matches Python
  • You evaluated both and packj fits your workflow better

full packj profile →

About grocy

ERP beyond your fridge Grocy is a web based self hosted groceries & household management solution for your home This is a hobby project by Bernd Bestel Give it a try Public demo of the latest stable version ( release branch) → Public demo of the current development version ( master branch) → Features See the website. → Questions / Help / Bug Reports / Feature Requests General help and usage questions → r/grocy on Reddit Bug Reports and Feature Requests → Issue Tracker Please don't send me private messages or call me regarding anything Grocy. I check the issue tracker and the subreddit…

read the full grocy overview →

About packj

Packj flags malicious/risky open source packages Packj (pronounced package) is a tool to help to mitigate software supply chain attacks. It can detect malicious, vulnerable, abandoned, typo squatting, and other "risky" packages from popular open source package registries, such as NPM, RubyGems, and PyPI. It can be easily customized to minimize noise. Packj started as a PhD research project and is currently being developed under various govt grants. Note Self hosted Packj webserver and several integrations coming later this month :punch: Watch this repo to stay up to date. Contents Get started available as Docker…

read the full packj overview →

More in Business Software

Related comparisons

More ERP & Operations projects

Compare either of these against the rest of the ERP & Operations field.

Frequently asked questions

Is grocy or packj more popular?

grocy has 9,646 GitHub stars and packj has 694. grocy has the larger community by that measure.

Are grocy and packj free?

Both are open source. grocy is licensed under MIT and packj under AGPL-3.0. Neither carries a licence fee.

What is the difference between grocy and packj?

grocy is written in Blade and packj in Python. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.

Which should I choose, grocy or packj?

Choose grocy if you want the larger community (9,646 stars) or its MIT licence terms. Choose packj if its feature set, stack or AGPL-3.0 licence fits better. Both are self-hostable.