How much does it cost to host a CTF?
A small online CTF can cost almost nothing in cash: a free platform, one small cloud VM and volunteer challenge authors. In this calculator's default scenario, 200 players with Docker challenges comes to about ₹3.75 lakh self-hosted once people-time is counted at ₹600/hour, and a large conference event runs higher. Most of that is challenge development and staff hours, not servers.
That is the pattern the calculator makes visible, and it's why answers to "how much does a CTF cost?" vary so wildly online. Someone who counts only cloud bills says "pennies". Someone who counts the team's time says tens of thousands of rupees. Both are right. They're just counting different things.
The six cost buckets of a CTF event
1. Platform or license
Self-hosted open-source scoreboards are free software, but you pay for servers and setup. Managed platforms charge per event or per seat. On CTF7, one jeopardy CTF a year for up to 50 players is free and hosted for you, with static flags. Standard is ₹9,999 per event for up to 500 players with dynamic flags, anti-cheat and bring-your-own Docker images, and Raw Ops bug-hunting events run self-serve on it (and on the Pro and Enterprise organization plans). Attack-Defense and King of the Hill are managed Premium formats with a custom quote, and events over 500 players are quoted on Premium.
2. Cloud infrastructure
A scoreboard for a few hundred players runs comfortably on one 4 vCPU / 16 GB VM. If you self-host, the bill grows with per-team infrastructure: Docker containers for each team, a vulnbox per team in Attack-Defense, or a separate target per team in Raw Ops. Even then, compute for a 24-hour event is usually thousands of rupees, not lakhs. If you self-host, choosing the right open-source platform matters more than which cloud you pick.
3. Challenge development
This is the real cost of a CTF. A good challenge needs an idea, an implementation, a clean intended solution, a test solve by someone who didn't write it, hints and a writeup. Budget 8 hours for an easy challenge and 30+ for a hard one. Twenty-five challenges at a balanced difficulty mix is about 400 people-hours. Our guide on how to create CTF challenges covers the process, and CTF7's challenge development service can build some or all of them for you.
4. Operations staff time
Someone has to install and theme the platform, containerize challenges, load test, answer "is web-300 broken?" at 2 a.m., rotate a crashed instance and publish results. Self-hosting adds an infrastructure on-call role for the whole event. Managed hosting removes that role but not the need for admins who handle hints, disputes and announcements.
5. Prizes
Prizes are entirely your call. College CTFs range from certificates and swag to cash pools, often sponsor-funded. On CTF7, participation certificates come with Standard, Premium and every organization plan (not Free), and Premium adds branded certificates; confirm what your plan covers before dropping them from the budget.
6. Misc and contingency
Domains, bandwidth spikes, a last-minute bigger VM, a replacement challenge. Keep 10% aside. If you collect registration fees, remember that CTF7 keeps a 10% platform fee on registration fees you collect (see pricing), and payment-gateway charges and any taxes on your own fees come on top of these estimates.
Self-hosted vs managed: where the money goes
Self-hosting is cheaper in cash when your team's time is free: a student club with volunteer authors and one person comfortable with Docker and Linux. Set the in-house cost per hour to ₹0 in the calculator and self-hosting usually wins on price. Be honest about what you give up, though: nobody else is on call when the scoreboard stalls, and anti-cheat, dynamic flags and container orchestration are yours to build.
Managed hosting wins when staff time has a real cost (a company, a conference or a paid events team), when the event is high-stakes, or when you need formats that are hard to self-host. Attack-Defense and King of the Hill need game servers, checkers and per-team networks that few teams have run before. On CTF7 those formats are run as managed events by our team, scoped and quoted per event. Our guide to choosing a CTF platform for your college goes deeper on the trade-offs.
When to use this, and when a spreadsheet is better
This calculator is a starting point with every assumption shown below, so you can argue with each number. It is written by a vendor and it compares self-hosting with CTF7 only, not with other hosted platforms. Once you have quotes, move to a spreadsheet with your real figures, add the other vendors you are considering, and use this page only to sanity-check the people-hours, which is the line organizers most often leave out.
Sample CTF budgets (from this calculator)
All four use the default ₹600/hour in-house rate and in-house challenge authoring. That rate decides which column wins: the managed column comes out lower only because it counts fewer staff hours, and in cash out of pocket CTF7 costs more in the default scenario (see the last rows of the table above). Change any input above to see your own numbers.
| Scenario | Self-hosted | CTF7 managed |
|---|---|---|
| Club practice CTF: 40 players, 8 h jeopardy, 15 beginner challenges, no prizes | ≈ ₹1.47 lakh | ≈ ₹1.37 lakh (Standard; your one free event a year also fits) |
| Tech-fest CTF: 300 players, 24 h, 25 challenges (30% Docker), ₹50,000 prizes | ≈ ₹3.76 lakh | ≈ ₹3.39 lakh (Standard) |
| Conference CTF: 800 players, 36 h, 35 challenges (30% Docker), ₹50,000 prizes | ≈ ₹5.27 lakh | ≈ ₹4.59 lakh + Premium quote |
| Attack-Defense: 60 players (20 teams), 8 h, 4 services, ₹50,000 prizes | ≈ ₹2.50 lakh | ≈ ₹1.80 lakh + Premium quote |
With volunteer time valued at ₹0, the club scenario drops to ₹2,204 in cash self-hosted (at the example cloud rates), against ₹9,999 on Standard, or a ₹0 platform fee on CTF7's Free plan (one event a year, static flags, up to 50 players). The tech fest drops to ₹56,109 self-hosted against ₹60,999 on Standard, because prizes dominate.
Pricing models you will meet
CTF platforms generally charge in one of three ways. Self-hosted open-source software costs nothing to license, so your spend is servers and staff time. Managed per-event pricing, which is how CTF7 Standard works, gives you a known fee per event with hosting and support included. Per-seat subscriptions bill monthly by user count, which suits permanent training programs better than one-off events. Compare like for like: include setup, on-call time and any content or licensing in each option. See CTF7 pricing for the current plans.
Seven ways to cut the cost of your CTF
- Reuse and remix. Retire challenges from last year's event into a practice track and write fewer new ones.
- Containerize only what needs it. Crypto, forensics and reversing challenges usually ship as files. Save instances for web and pwn.
- Pick the smallest format that meets your goal. A jeopardy qualifier and a short A/D final beats a 48-hour A/D for everyone.
- Shorten the event. Staff hours scale with duration. Most student CTFs work well at 8 to 24 hours.
- Get prizes sponsored. Security vendors, training companies and alumni often fund prize pools in exchange for visibility.
- Collect a small registration fee. Even a modest per-team fee can cover infrastructure, and it reduces no-shows. CTF7 supports fee collection as part of registration.
- Plan before you build. Our hosting guide and the college CTF playbook help you avoid expensive last-minute rebuilds.
Want a real number? Share your player count, format and dates with the CTF7 events team and we'll send a quote. Quotes for Attack-Defense and King of the Hill are scoped to your event. Plan your event.
Where to go next
- Taking the budget to your department? How to pitch your HoD turns these numbers into a proposal, and cybersecurity labs for colleges without servers compares self-hosted, cloud VM and hosted options.
- Comparing platforms? CTF platforms for universities and the platform comparison put prices and trade-offs side by side.
- Planning the event itself? Follow how to host a CTF and start from a rules template.