NextJudge

Spec sheet

Purpose

NextJudge is an open-source, self-hosted platform for competitive programming, practice problems, and online contests.Read 7 Oct 2026 · docs.nextjudge.net

Integrations

The configuration documentation describes optional GitHub OAuth and optional Elasticsearch for problem search.Read 7 Oct 2026 · docs.nextjudge.net

Support

The product landing page lists [email protected] for questions and bug reports.Read 7 Oct 2026 · nextjudge.net

License

The documentation identifies NextJudge as MIT-licensed and says the license has no seat limits or feature tiers.Read 7 Oct 2026 · docs.nextjudge.net

API and CLI

The project documents a REST API and a CLI for automation, downloading problems, local testing, and submitting solutions.Read 7 Oct 2026 · docs.nextjudge.net

Authentication

The getting-started guide supports email/password registration and GitHub sign-in when OAuth is configured.Read 7 Oct 2026 · docs.nextjudge.net

Availability

The landing page invites visitors to join a waitlist for early access and says new users will be onboarded when the team is ready.Read 7 Oct 2026 · nextjudge.net

Browser workspace

The solving workspace combines a problem statement, sample tests, a language selector, and a Monaco editor, with separate run and submit actions.Read 7 Oct 2026 · docs.nextjudge.net

Code editor

Its code editor uses Monaco and provides syntax highlighting and multiple themes.Read 4 Oct 2026 · nextjudge.net

Contest tools

The platform includes live leaderboards, contest Q&A, live submissions, real-time submission feedback and activity overviews.Read 4 Oct 2026 · nextjudge.net

Contests

Timed contests include scheduled problems, registration, clarifications, and standings.Read 7 Oct 2026 · docs.nextjudge.net

Data control

The maker says participant data, problems and submissions are stored in PostgreSQL on infrastructure the operator controls.Read 4 Oct 2026 · docs.nextjudge.net

Deployment requirements

The getting-started guide requires Docker and Docker Compose, at least 4 GB RAM (8 GB with web and judge together), and available ports 5000, 5432, 5672, and 8080.Read 7 Oct 2026 · docs.nextjudge.net

Execution

Judge workers compile and run submitted code in nsjail sandboxes.Read 4 Oct 2026 · docs.nextjudge.net

Isolation

The documentation says compile and run use nsjail with no network, capped CPU and memory, and a restricted filesystem.Read 7 Oct 2026 · docs.nextjudge.net

Judge limit caveat

Problem timeout and memory settings are stored and exposed, but the judge currently uses fixed nsjail defaults instead of applying those settings.Read 7 Oct 2026 · docs.nextjudge.net

Judging

Submissions are queued through RabbitMQ, then compiled and evaluated by a Python judge worker in nsjail.Read 7 Oct 2026 · docs.nextjudge.net

Language support

The maker’s homepage lists Python, JavaScript, C++, Go, Haskell, Kotlin, C#, Java, TypeScript, PHP, Swift, Rust, C, Lua and Ruby.Read 4 Oct 2026 · nextjudge.net

Languages

The landing page lists Python, JavaScript, C++, Go, Haskell, Kotlin, C#, Java, TypeScript, PHP, Swift, Rust, C, Lua, and Ruby.Read 7 Oct 2026 · nextjudge.net

Operational responsibility

Self-hosters operate the database, message queue, judge images, backups, monitoring, and network isolation.Read 7 Oct 2026 · docs.nextjudge.net

Operational tradeoff

Self-hosters are responsible for operating the database, message queue, judge images, backups, monitoring and network isolation.Read 4 Oct 2026 · docs.nextjudge.net

Requirements

A local deployment requires Docker and Docker Compose, at least 4 GB RAM (8 GB with web and judge together), and ports 5000, 5432, 5672 and 8080 free.Read 4 Oct 2026 · docs.nextjudge.net

Security operations

The deployment guide recommends keeping judge workers network-separated from internal admin tools and rate-limiting authentication and password-reset routes at the proxy.Read 4 Oct 2026 · docs.nextjudge.net

Where Specifiction places it

• Coding Challenge Platforms#22 of 307.3