RadioForge
Menu
Products
WebForgeAirForgeControlForgeVTForgeLocalForgeSyndiForgeProductionForge
Solutions
Local StationsInternet StationsRadio GroupsNew Launches
More
AboutSupportForge Book a Demo
Independent Radio
Goes Further.
SupportForge

Real support. Real people.
A real system.

Free radio tools hand you software and walk away. With RadioForge you also get SupportForge: a real bug and feature desk, real people who write back, fixes that are tested before they reach you, and servers that are watched around the clock.

Radioforge.netReal Radio. Brighter Tomorrow.
Report an issue

Why it matters

Software is only half of it.

Plenty of radio tools are free. Almost none of them have anyone on the other end when something breaks on a Tuesday afternoon.

01

Someone reads it

Every report lands on a real ticket desk with your product, your station and your screenshots attached.

02

You hear back

You get an email the moment we receive it, and again at every step until it is solved.

03

Fixes are tested

A fix is built and checked first. Nothing goes live on your station until it has been approved.

24x7

Weekday support

Our team works the desk around the clock on weekdays, and the servers are watched every five minutes, every day.

Step one

Reporting a problem takes one minute.

Here is a real ControlForge bug report. Pick the product, say what happened, add a screenshot if you have one, and press Send. That is all.

  • Works for WebForge, AirForge, ControlForge and LocalForge
  • Attach up to 5 screenshots or documents
  • Works just as well from your phone
The real RadioForge report form with a ControlForge bug filled in
A real ControlForge bug report (test ticket #52)

A ticket's journey

What happens after you press Send.

We filed a real test ticket, #52, and walked it through our actual desk. Every picture below is the real screen.

1 · It reaches a real person

Your report lands on our ticket desk.

The moment you press Send, a qualified support rep is emailed and your report appears at the top of the desk, tagged with the product and your station. You get an instant email with your reference number.

The RadioForge ticket desk with test ticket 52 at the top
The real desk. Other customers' tickets are blurred.
2 · We dig in

It goes to Development, and you are told.

Your rep reads it and sends it to Development to investigate. You get an email right away saying we are looking into it.

Ticket 52 marked With Development
Ticket #52, now with Development
3 · A plain answer

The findings come back in plain English.

Development posts what it found as a short, plain summary, with the technical detail tucked behind a button. Then your rep decides the next step. Building a fix changes nothing live. Shipping it is a separate, deliberate OK.

Development findings on ticket 52 with the Build the fix button
Real findings on #52. It was a test, and Development said so.
4 · Real conversation

We talk to you, and your replies come right back.

If we need more detail, your rep emails you from the ticket. You simply reply to that email, and your answer lands on the same ticket automatically. Nothing gets lost.

The conversation on ticket 52 showing our question and the reporter's emailed reply
The reporter's email reply, landed on the ticket by itself
5 · Careful rollout

Fixes ship one station at a time if needed.

Once a fix is approved, we can send it to every station, just yours, or a chosen few first. When it is live, you get a "your fix is live" email with a plain summary of what changed.

The history log on ticket 52
Every step is logged on the ticket

The emails

You are kept informed at every step.

These are the real emails from ticket #52, in the order they arrived. The reporter's address is hidden.

RadioForge · 11:20 am
Email: We got your bug report (#52)

Seconds after Send: we have it, here is your reference number.

RadioForge · 11:30 am
Email: We're looking into your bug report (#52)

The moment it goes to Development, you are told.

Your support rep · 11:30 am
Email: Update on your bug report (#52) with a question

A real question from a real person, sent from the ticket.

The station replies · 11:43 am

"Hi, it was Chrome on my laptop. The Save button just stayed grey." Just a normal email reply, and it landed on the ticket by itself (shown in step 4 above).

Feature requests

Got an idea? It rides the same rails.

Feature requests use the same form and the same desk. A support rep reads every one, you get the same emails, and you are told when your idea is added.

  • Same form: just tap "Request a feature"
  • Same desk, same reference number, same updates
  • Ideas we schedule go to "Later", and you are told
The report form with Request a feature selected for ControlForge
A ControlForge feature request on the real form

Always up to date

Every installation is updated remotely.

You never have to reinstall the software over and over again. Install once, and new fixes and features reach your station automatically.

WebForge uptime

When a server failed, the sites stayed up.

This is not a drill we describe. It happened.

  1. July 30, 2026: our main US server went down completely.
  2. Our watchdog caught it and alerted us by email and text.
  3. We switched our WebForge sites over to our standby server in London, so listeners kept reaching them.
  4. Once the main server was repaired, we switched everything back and checked every site.

A standby copy of every site,
refreshed every day, an ocean away.

Our infrastructure

A professional setup, not a hobby server.

Three servers in two countries, watched every five minutes, backed up every night.

Your station & listenerswebsites, apps, admin Security layer (Cloudflare)HTTPS everywhere, attack filtering Main server 1Kansas City, USA Main server 2Kansas City, USA nightly backupsdaily refresh Standby serverLondon, UK Watchdogchecks every 5 minutes if anythinglooks wrong Alertsby email and text Failover switchone switch, all sites moves sitesto London

Three servers, two countries

Two main servers in the US and a standby server in London, UK.

Watched every 5 minutes

Memory, disk, load, services and every site are checked around the clock. Problems alert us by email and text.

Backed up every night

Station sites are backed up nightly, and the London standby is refreshed every day.

Not WordPress

Our sites are built in-house, with no plugin pile to patch and no plugin holes to exploit.

Our offices

Real offices, on two continents.

Our team works from offices in the US and in Europe.

US offices

Fort Lauderdale, Florida

United States

European offices

Madrid, Spain

Spain

European offices

Lisbon, Portugal

Portugal

Talk to a real person.

Found a bug, have an idea, or want to see how SupportForge works for your station? We answer.

Fort Lauderdale · Madrid · Lisbon · 24x7 weekday support · Talk to broadcasters, not salespeople.