Appsmith vs 
ToolJet
Compared on data, not vibes. Metrics refresh nightly; verdict links carry the math.
| Appsmith | ToolJet | |
|---|---|---|
| GitHub stars | 40,616 | 38,314 |
| Last commit | 0d ago | 0d ago |
| Latest release | v2.2 | v3.20.209-lts |
| Docker pulls | — | — |
| License | Apache-2.0 | AGPL-3.0 |
| Min RAM | 8,192 MB | 4,096 MB |
| Containers | 1 | 3 |
| ARM (Pi-friendly) | yes | no |
Appsmith
Drag-and-drop internal tools over your own databases and APIs, with no per-builder seat and no second meter for the people who only use them.
Backs these verdicts
ToolJet
The internal-tools builder ToolJet sells, installed from ToolJet's own repository, with no per-builder meter and no end-user cap.
Backs these verdicts
Neither page tells you which is "better" — they solve the same jobs differently. Pick by the constraint that binds you: RAM, ARM, license, or how alive the project looks.