U-CTF is the entrypoint for running polished CTF events without building the platform yourself.
Get hosted infrastructure, deploy shared or instanced challenges, upload your own themes and plugins, and ship an event with storage already included. U-CTF handles the platform layer so you can focus on challenge design and competition flow.
Managed CTFd infrastructure
Provision the event stack without hand-assembling clusters, ingress, or storage.
Themes and plugins ready to upload
Push your branding and extensions into the platform without extra plumbing.
Two deployment models for challenges
Run one shared service for everyone or isolated instanced services per team.
Managed CTFd infrastructure
Provision the event stack without hand-assembling clusters, ingress, or storage.
Themes and plugins ready to upload
Push your branding and extensions into the platform without extra plumbing.
Two deployment models for challenges
Run one shared service for everyone or isolated instanced services per team.
10 GB
Autoscaling + Git sync
Everything needed to run the event, without rebuilding the platform around it.
U-CTF is built for organizers who want a managed CTF helper instead of another pile of infrastructure tasks. This is done through various features: customization, deployment, storage, and operations all belong in one workflow.
Deploy challenges the way the event actually needs them.
Some challenges belong in one shared service. Others need isolated infrastructure per team. U-CTF is designed to support both patterns so organizers are not forced into a single deployment model.
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.
- One running service for the whole event
- Simpler resource footprint
- Useful when all teams can interact with the same environment
Use instanced deployments when each team needs a clean environment. That model is better when the challenge can be altered, exhausted, or solved in a way that should not leak state across teams.
- Fresh environment for each team
- Safer isolation for mutable challenges
- Better fit for stateful or destructive challenge flows
Ship challenge assets quickly, then decide how much of the storage story you want to own.
U-CTF includes storage from the start, which means you can publish challenges, bundle event assets, and keep customization files moving without blocking on separate infra work.
- 10 GB storage included for challenge and event assets.
- Bring your own credentials when your organization needs a custom storage path.
- Keep themes, plugins, and challenge artifacts closer to the event workspace.
Included by default
10 GB
Enough room to get a competition moving, with a clean path to use your own credentials when the event setup calls for it.
The roadmap is aimed at removing even more operational drag.
Future platform work will push 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.
Git sync
Keep challenge content closer to versioned repositories and simplify iterative delivery.
Read the public overview now, then sign in when you are ready to run the event.
The public entrypoint explains what U-CTF gives you before it asks for a sign-in. The actual workspace remains behind authentication for provisioning, administration, and event operations.
What organizers get
Managed infrastructure instead of do-it-yourself event plumbing.
Customization with themes, plugins, and challenge assets already in the workflow.
Clear room for future autoscaling and Git-based content delivery.