Infrastructure already handled
Start from a managed stack instead of stitching together networking, storage, certificates, and runtime services by hand.
Loading…
Deploy shared or instanced challenges, upload your themes and plugins, and ship with storage included. No infrastructure to assemble by hand.
Built for organizers who want to focus on great challenges, not on maintaining the stack running them. Customization, deployment, storage, and operations in one workflow.
Start from a managed stack instead of stitching together networking, storage, certificates, and runtime services by hand.
Upload the visual identity and platform extensions your event needs without building a bespoke deployment workflow.
Some challenges belong in one shared service. Others need isolated infrastructure per team. Both patterns are supported, you're not locked into one model.
One container for everyone
Use a shared challenge deployment when a single service is enough for every team. It keeps operations lean and is a good fit for classic web and service-style challenges.
Isolated environment per team
Use instanced deployments when each team needs a clean environment. Better when the challenge can be altered, exhausted, or solved in a way that should not leak state across teams.
U-CTF's basic plan is built for organizers who need per-team instanced challenges and full container control. Capabilities hosted CTFd reserves for higher tiers.
U-CTF
€44.99
/month
CTFd.io
$60
/month
U-CTF includes storage from the start, so you can publish challenges, bundle event assets, and keep customization files moving without blocking on separate infra work.
Included by default
10 GB
Enough room to get a competition moving, with a clean path to your own credentials when the event setup calls for it.
Choose between one challenge service for every team or isolated instances when the challenge model demands it.
Ship with 10 GB included for challenge assets and switch to your own credentials when your workflow requires it.
Keep teams, environments, and event delivery in one control plane instead of spreading the work across ad hoc tooling.
Connect a GitHub repository and keep challenge content in sync with versioned commits, so iterative delivery stays close to your workflow.
Use your own images and registries, without proprietary build constraints.
07Comparison based on publicly available CTFd.io Basic plan details as of April 2026. You bring your own container images and challenge content. U-CTF provides the infrastructure to deploy and manage them.
Future platform work pushes U-CTF further toward hands-off event operations, without pretending those features are here already.
Autoscaling
Scale event workloads more gracefully as traffic spikes and challenge demand changes.
Sign in with GitHub, create an organization, and you're ready to run your first CTF event. The whole setup takes a few minutes.
How it works