Managed CTF Platform

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

Set up the event without assembling networking, storage, or certificates by hand.

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.

What ships with U-CTF
A managed control surface for infrastructure, content, and event operations.

Managed CTFd infrastructure

Set up the event without assembling networking, storage, or certificates by hand.

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.

Included storage

10 GB

Challenge delivery

Git sync

Soon on the roadmap

Autoscaling

Bring your own storage credentials when you need them, or start with the included managed storage path and keep event assets moving immediately.
Why U-CTF

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.

Infrastructure already handled
Start from a managed stack instead of stitching together networking, storage, certificates, and runtime services by hand.
Theme and plugin delivery
Upload the visual identity and platform extensions your event needs without building a bespoke deployment workflow.
Shared or instanced challenges
Choose between one challenge service for every team or isolated instances when the challenge model demands it.
Included challenge storage
Ship with 10 GB included for challenge assets and switch to your own credentials when your workflow requires it.
Operational clarity
Keep teams, environments, and event delivery in one control plane instead of spreading the work across ad hoc tooling.
Git-synced challenges
Connect a GitHub repository and keep challenge content in sync with versioned commits, so iterative delivery stays close to your workflow.
Ready for platform growth
The platform is set up to expand with heavier events, richer pipelines, and more demanding infra patterns over time.
Challenge deployment

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.

One container for everyone
Shared challenge

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
Isolated environment per team
Instanced challenge

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
Plan comparison

More challenge infrastructure, lower price point.

U-CTF's basic plan is built for organizers who need per-team instanced challenges and full container control, capabilities that hosted CTFd reserves for higher tiers.

U-CTF

€39.99

/month

CTFd.io

$60

/month

Shared challenges5 containers
Instanced challenges (isolated per team)
Custom subdomain or domain
TLS / SSL
Git-synced challenge delivery
Bring-your-own container images
CTFTime integration
Webhooks (Discord & generic)
Theme & plugin uploadsFree themes only
Included storage10 GB
Teams & players
Page-view capNone250k / month
Preconfigured email

Comparison 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.

Storage and delivery

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.

Themes, plugins, and challenge bundles stay close to the platform instead of relying on improvised side channels.
Coming soon

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.

Next step

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 setup, 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.

Git-synced challenge delivery and clear room for future autoscaling.