Usage, credits, and event sizes
How event sizes, instance-hours, and wallet credits fit together.
Three things govern what running events costs your workspace: your plan, each event’s size, and your wallet credits. The plan is a monthly subscription that sets limits and features (Plans and limits); this page explains how the other two interact, and where instance-hours fit in.
Instance-hours: the unit of usage
Container challenges run as live per-team instances, and their runtime is metered in instance-hours (IH). A Small instance running for one hour consumes 1 IH; bigger task sizes consume proportionally more, at the multiplier listed in Challenge editor. Static challenges consume none, which is why an Extra Small event (static-only) never records instance-hour usage.
Each event comes with an included budget of instance-hours, set by its size and how many hours of play it runs. Usage inside that budget costs nothing extra, and the workspace Usage page totals it across the events that ran in the current month. Usage beyond it is overage, charged to your wallet credits and visible as Usage overage charged entries in your credit activity.
The included allowance and the overage rate both scale with event size. The allowance is quoted per 24 hours and prorated across the hours of play, from your event’s start to its freeze, so a Small event with a 36-hour duration is included for 150 IH:
| Size | Included instance-hours per 24h | Overage per extra IH |
|---|---|---|
| Extra Small | None (no instances) | None |
| Small | 100 | $1.00 |
| Medium | 200 | $2.00 |
| Large | 400 | $4.00 |
| Extra Large | 800 | $8.00 |
Usage is totalled per event and metered to the exact second. A session that runs a quarter of an hour counts as a quarter of an instance-hour, never a whole one. Only the money rounds, always up, to the next cent.
What an event’s size does
Size is the per-event capacity knob, chosen at creation and fixed for the event’s life:
- it caps storage and build minutes (the quotas your Usage and Image builds pages track),
- it scales the event’s hosting cost: the credit reservation below grows with size,
- larger sizes come with more included instance-hour headroom for the heavier instance traffic they imply,
- and at the bottom of the range, Extra Small trades all container capability away for the lightest footprint.
Which sizes you can pick is a plan limit; the per-size storage and build-minute numbers are in Plans and limits, and the included instance-hours are in the table above.
What credits pay for
Wallet credits are your workspace’s prepaid balance, and they’re touched at five moments:
- When you create an event. Hosting for the event’s size and duration is reserved from your wallet up front: the event’s hold rate prorated over the hours of play, from the start to the freeze, plus the same rate over the wind-down that keeps the event up after the freeze, plus half that rate for the wait between creating the event and its start time. Your event environment comes up as soon as setup finishes, not when the countdown reaches zero, which is why that wait is charged. The create form shows the estimate before you submit. If the balance can’t cover it, creation stops with “Not enough wallet credits to create this event. Add credits and try again.” The insufficient-balance check happens before anything is provisioned, so there’s nothing to clean up; top up and re-submit. The reservation shows in your credit activity as CTF credits reserved, and it comes back in full if the event fails to provision (CTF credits released).
- When you push an event’s End time back. Extending a running event keeps its environment alive longer, so the extra time is reserved at the same daily hold rate, prorated over the hours added beyond the end you’ve already paid for and discounted like the original reservation. Shortening an event doesn’t return credits, so moving End back within a window you’ve already paid for costs nothing. Ending the event outright is what returns its unused runtime. If the balance can’t cover the extension, the save is refused and the schedule is left as it was. Top up from Usage and save again.
- When a player launches an instance. Credits are reserved before it starts, covering the worst case (the longest the instance may run, at its task-size multiplier) for whatever part of that the event’s remaining included budget doesn’t already cover. While the included budget covers the whole session, nothing is reserved and no entry appears. Otherwise the reservation shows as Instance hours reserved and returns in full when the instance stops, as Unused instance hours returned. A launch is refused when the balance can’t cover the reservation, and the player sees “This event’s organization has run out of instance hours. Ask an organizer to top up the wallet.” A launch is also refused once the event’s optional overage spend cap is reached, with “This event has reached the overage spend cap its organizers set. Ask an organizer to raise or remove the cap in the event’s settings.”
- When usage passes your included budget. Overage is drawn from the wallet as the event runs, entry by entry, rather than arriving as a surprise bill later.
- When you end an event early. The runtime the event paid for and did not use comes back to your wallet at that moment, valued at the same daily hold rate and counted in whole hours against the end date your reservation covers, with any part-hour dropped and never more than what’s left unreturned on the charge. An event that runs to its end date has nothing left to return. The entry shows as Cancelled CTF credits returned, and the confirmation dialog shows the amount before you commit.
Reservations hold credits without spending them. What a session actually costs is settled through the included budget and overage in moment 4. Because they are taken up front, a workspace can’t commit past its balance mid-session; if credits run out while instances are running, those instances are stopped shortly after and no new ones start until you top up. Extra Small events are static-only, so moment 3 never applies to them.
Topping up and reading the credit activity list are covered in Manage billing and credits.
Watching your usage
Two pages, two scopes: the workspace Usage page totals instance-hours across the events that ran in the current month (an event straddling the first of the month counts in full on both sides, because the totals are per event), while each event’s dashboard Usage page scopes consumption to that event, alongside its storage bar, its open sessions, the credits currently reserved against them, and the balance remaining. Settled usage updates as metering data arrives, so the consumed figure is a running ledger rather than a live meter; reservations move as instances start and stop.
Each event’s Running instances page lists every session; opening one shows its task size, multiplier, and metering times, and lets you terminate it while it is still running. A Terminate all action on the page stops every running instance at once. The page also flags instances that may still be running after being marked terminated. Cleanup retries on its own, and persistent entries go to support.
A practical sizing rule: pick the size for the event you expect, not the one you hope to grow into. Size can’t change after creation, and wallet-charged overage means a busier-than-expected event degrades into extra cost rather than an outage, as long as the wallet stays funded.