Juryza
Roadmap

Where Juryza is going

Juryza is production-first today. This is the direction of travel — integrations that add trustworthy identity signals, and platform features that harden judging and voting further. Statuses are honest: shipped, planned, or still being explored.

Integrations

The theme is verified identity, not more places to click a button. Every integration is optional and additive.

GitHub integrationPlanned

Link a repo to a project and verify ownership via the connected GitHub account, so a submission's code can be trusted to belong to its team. Pull commit activity within the hackathon window to flag work done before the start, surface language/stack automatically, and let judges open the diff since kickoff. A future step: gate community voting behind a verified GitHub account to raise the cost of Sybil identities.

LinkedIn integrationExploring

Optional identity signal, not a voting channel. Let participants attach a verified LinkedIn profile to their public Juryza profile for credibility, and let winners share certificates directly. Community voting will never run on LinkedIn reactions — that is precisely the failure mode the voting-integrity guide documents.

Single sign-on & OAuth providersPlanned

Google, GitHub and Discord sign-in through Better Auth, so an event can require a real, provider-verified identity to participate or vote without running its own email flow.

Platform & integrity

Write-up quest & judge runoffPlanned

A structured public write-up challenge on shortlisted teams, with the judging panel holding final authority over the pick — replacing brigadeable open polls. See the voting-integrity guide for the design.

Curated electorate lockPlanned

Freeze the eligible voter roster at a snapshot taken before the event starts, so accounts created during the hackathon cannot vote — closing the “member before kickoff” loophole automatically instead of by manual check.

Duplicate & AI-slop detectionShipped

TF-IDF cosine similarity plus same-repo/title matching already surface look-alike and duplicate submissions on the compare view.

Shared rate-limit storagePlanned

Move rate limits and the anon-per-IP cap from process memory to shared storage (Redis) so they hold across multiple app instances, not just one container.

Smarter notificationsExploring

Digest emails and webhooks for deadline reminders, assignment nudges and results — building on the existing per-subscription signed webhooks.

Assisted judging insightsExploring

Optional, transparent aids for organizers: outlier-score flags, judge-agreement summaries and rubric-coverage gaps — never an automated verdict.