Behind the scenes
How Jurika is built and looked after, for funders, partners and anyone technical. Every number is counted from the real code — never rounded up — and refreshed every month. Last counted 17 October 2026.
Jurika today
- Lines of application code
- 63,422
- Lines of automated tests
- 5,077
- Automated checks before every release
- 552
- Screens
- 90
- Server actions (API routes)
- 110
- Database tables
- 46
- Database upgrades (migrations)
- 162
- Kinds of email
- 61
- Automatic background jobs
- 16
- Saved changes since 24 June 2026
- 1,326
In English and Bahasa Melayu · online and face-to-face judging · run by PaKSI Kelantan, a non-profit, and developed by SyncMind Consulting & Services.
How it has grown
Lines of code at each month end since the first saved version on 24 June 2026 — application code in blue, automated tests in green.
| Month end | App code | Tests | Screens | API routes | Migrations |
|---|---|---|---|---|---|
| 24 Jun 2026 | 18,842 | 0 | 52 | 43 | 44 |
| Jun 2026 | 26,203 | 455 | 58 | 59 | 70 |
| Jul 2026 | 43,658 | 1,562 | 70 | 81 | 125 |
| Aug 2026 | 49,793 | 2,230 | 81 | 92 | 133 |
| Sep 2026 | 53,842 | 3,075 | 83 | 98 | 143 |
| 17 Oct 2026 | 63,422 | 5,077 | 90 | 110 | 162 |
How it’s looked after
- Every update passes 552 automated checks, then a full build, before it can go live.
- Every update goes to a separate test copy of Jurika first, and only then to the real one — never during a live competition.
- The database is backed up every night to a separate place, and each backup is checked.
- Three outside monitors watch the app, its background jobs and its backups + email, and alert us if anything stops.
- A full review of the code for bugs, security and privacy runs after every batch of changes.