- Client tools
- Forms
- Billing Portal
- Help Center
- Remote Support
Churches
Most organisations can absorb a bad Tuesday. A church has one immovable moment a week, in front of everyone, usually being streamed, run largely by volunteers who joined last month. Iconium keeps the systems behind that morning working, and the rest of the week quietly running underneath it.
For most churches this is the largest technical burden they carry, and it is the one thing an ordinary IT provider is least prepared for. It has a hard weekly deadline, it depends on the part of the connection nobody sizes for, and it fails in public.
Streaming depends on upload bandwidth, which is the number most internet packages quietly under-provide. A connection that feels fast all week can still fail at 10am on Sunday. It is worth measuring before it embarrasses you rather than after.
A second connection that takes over, or a device that can fail over on its own, turns a dropped stream into a few seconds of stutter. This is not expensive. It is mostly a matter of having decided in advance.
Guest wifi, the children’s wing and a full building of phones should not be able to starve the encoder. Separating that traffic is a configuration decision, not a purchase.
We are not an AV integrator. Cameras, sound desks, lighting and the mix are your AV people’s work and we will not pretend otherwise. We handle the network, the connection, the machines and the failover the stream depends on, and we coordinate with whoever runs the booth.
Any organisation that stores, processes or transmits card data is in scope for PCI DSS, enforced through your processor agreement rather than by statute. The cheapest way to meet it is to arrange things so your systems never touch card data at all — a hosted giving page keeps that with the processor, where it belongs.
Names, addresses, family relationships, giving history, pastoral notes. It is one of the most sensitive files a small organisation holds and it is usually the least protected, because nobody thinks of a church directory as a data asset. Attackers do.
The most common gap we find. People serve for a season and move on, and their accounts stay. Named accounts instead of shared logins, and an offboarding step that actually happens, fixes most of it for very little money.
Background checks and children’s ministry records carry no formal regulatory classification, which sometimes means they are treated as less sensitive than they are. They are among the most serious records you hold, and they should be access-controlled accordingly.
Saint Rita Parish on Baldwin Road in Solon is an Iconium client, and not the only congregation we support across Northeast Ohio. The parish live-streams its 5:00pm and 10:45am Masses, so the situation described above is not a hypothetical one: two fixed broadcasts a week, in front of the people who cannot be there in person.
We also support Saint Rita School next door. Where a parish runs both a church and a school, the two are usually one engagement rather than two, which matters more than it sounds: the weekend broadcast and the school calendar stop competing for attention and get planned against each other instead.
Solon is also where our own office is. When this page says someone comes out, for Saint Rita that is a few minutes rather than a promise. See the school IT page for the other half of that arrangement.
The same published rates apply, and we do not run a separate church price list — the published one is already the price. $163 per user, $19 per computer, $100 per server, $17 per mailbox and $179 per additional location, per month, or $199 for a fully equipped seat. No minimum and no setup fee, so a church with six on staff pays for six. Additional campuses are charged per site rather than per device in them. The pricing page has a calculator.
We support congregations across Northeast Ohio. Where a church runs a school, the two are usually one engagement — see our school IT page. Iconium’s founder serves on local nonprofit boards.
Usually, and usually it is not the camera. The most common cause is upload bandwidth — streaming depends on the upload figure, which most internet packages under-provide and almost nobody measures. After that it is contention, where a full building of phones and the children’s wing are competing with the encoder, which is a network configuration problem rather than a purchase. We measure first and tell you which it is, rather than selling you a bigger connection on principle.
No, and you should be wary of a provider who says yes without an AV person on staff. Cameras, sound, lighting and the mix belong to your AV people or your volunteers. We handle everything that sits underneath them: the network, the connection, the failover, the machines running the encoder and presentation software. Where the two meet we coordinate with whoever runs the booth rather than arguing about the boundary during a service.
This is the most common attack on churches and it works because it exploits trust and deference rather than technology. Email security and quarantine stops most of it before anyone reads it. Multi-factor authentication means a stolen password is not enough. Simulated phishing means your volunteer has seen the pattern in a safe setting. Then a callback rule on a known number for any payment or gift-card request — and the pastor has to publicly back whoever uses it on them, or it will not hold.
You are in scope if your systems store, process or transmit card data. The useful move is to arrange things so they do not: a hosted giving page or a redirect keeps the card data with your processor and keeps your scope as small as possible. The obligation reaches you through your processor agreement rather than a statute, so check what yours says. We help with the arrangement; we do not assess or certify compliance.
Yes, and it is the normal arrangement here rather than an exception. Volunteers keep the relationships, the room knowledge and the Sunday routine. We take the parts that need 24/7 coverage, specialist tooling or continuity when someone moves away — which is the real risk, since a church often has one person who knows everything and no record of it anywhere else.
Your first location is included in the monthly rate and each additional campus is $179 per month, charged per site rather than per device in it. That covers firewall management, network segmentation, wireless and documentation. For a multi-campus church the more useful question is usually whether the sites should share identity and systems or stay separate, which is worth deciding deliberately rather than inheriting.
Two ways that are real rather than rhetorical. First, the major software vendors run non-profit pricing and grant programmes whose terms change regularly, so churches are often either missing them or still assuming an old one applies; we track that and pass through what you qualify for. Second, quarterly planning puts capital purchases in the right budget year instead of as an emergency. What we will not do is quote you a lower rate than the published one — that is already the price, and it is on the website.
We plan for a clean handover and never withhold data or organisational intellectual property. We work with whoever comes next, including a volunteer, and hand over documentation. Onboarding in the other direction takes about a week, with terms of twelve, twenty-four or thirty-six months and no setup fee.
Call (440) 991-9980 or book a thirty minute call. It is the number that decides whether Sunday works, and most churches have never been told it.
See also: every industry we serve and our written answers.
