Series · Part 6 of 6
Building Djengo
I ran a small script across every Djengo repository in September 2026. It counts commits, active months, and lines of hand-written source, meaning TypeScript, JavaScript, C#, and Vue, with generated code, migrations, protobuf output, and build folders excluded.
22
Repositories
2,030
Commits
~772k
Lines of source
18
Months
Where the commits went#
| Repository | Commits | Lines | Since |
|---|---|---|---|
| djengo-proto-contracts | 614 | 2,157 | Jun 2025 |
| client (Staff Workspace) | 270 | 276,102 | Mar 2025 |
| gateway-service | 125 | 63,776 | Jun 2025 |
| profile-service | 106 | 26,030 | Jun 2025 |
| financials | 85 | 70,314 | Oct 2025 |
| organization-service | 84 | 15,674 | Jun 2025 |
| operations | 77 | 56,464 | Oct 2025 |
| events | 74 | 37,231 | Apr 2026 |
What the numbers say#
- The contracts repo has the most commits and one of the smallest codebases. Small, frequent changes to the boundaries are where the design actually happens.
- The Staff Workspace is over a third of all source. Operators live in that UI all day, so that is where the weight belongs.
- The .NET services are young and dense. Events and facility are under six months old and already hold almost 60k lines between them.
- Mobile has been in the repo since May 2025. Staff on the floor were never an afterthought.
What they do not say#
Commits are effort, not value. Lines of code are closer to cost than to progress. None of these numbers says whether a hotel manager closed the day faster or a clinic got payroll right on the first try.
Eighteen months and 22 repositories. It is a lot of software. The job now is to turn it into a lot of operators who would not go back.
← Part 5
State machines are product decisions
Key takeaways
What to remember
- 22 repos, 2,030 commits, ~772k lines in 18 months.
- Boundaries change most often; the UI carries the most weight.
- Pilots and operators are the next numbers that count.




