Clan or guild website — dedicated hosting vs builders

Two guilds both ask for "a website" and want different things. One wants pages, a forum, and recruitment tonight, without opening an editor. The other wants the address, the files, and the database in its own hands, even if version one is a single page. A clan or guild website is not one choice: you either use a builder, or you use hosting and publish what you wrote.

In this piece, Battlehorns is hosting for gaming communities — guilds, clans, and esports teams — not the metal band of the same name. The free plan is web space (PHP, MariaDB, FTP, SSL), not a page builder. What that plan includes, and what it leaves out, is in the free guild hosting guide.

What a clan site actually needs

Before you compare products, list what the site must do next season. Serious communities share the same core:

• Who you are — game, faction or mode, schedule, language, and what you will not tolerate.
• How to join — requirements, what you offer, and a place to apply. A Discord invite expires; a URL does not.
• Proof you exist — officers, a recent result, one light image. Outsiders cannot guess your reputation.
• A stable address for bios, league sheets, and the Discord footer. How chat and the site fit together is in Discord and your website.

What many guilds treat as mandatory and then fail to maintain: a forum with dozens of boards, a shop, a wiki, and a full-resolution gallery. A forum nobody answers hurts more than it helps. The short site converts. The bloated site nobody updates looks abandoned.

Separate the public poster from internal operations. Members, events, loot, and resources belong in GuildOps. The website does not have to be the officer panel. That split is covered in GuildOps — guild management in one app.

Classic hosting vs a website builder

A guild website builder — Guildtag is the one communities run into most often — ships pages, a forum, and a community look already assembled. You create an account, pick a theme, and publish. You do not need FTP or to know what a database is.

As of this article, Guildtag describes its free plan as ad-free sites for guilds, clans, and esports, inside their platform. On the pricing page, your own domain, custom CSS and JavaScript, and an HTML widget sit on the paid plan. Sites on the platform use their domain certificate; a custom domain on the paid plan gets a Let's Encrypt certificate. It is not a space where you install whatever you want over FTP: you customize their widgets and pages.

Classic hosting, such as Battlehorns shared hosting, is the opposite. You get a subdomain, a public_html folder, PHP, one MariaDB database, and one FTP user. The HTML you upload is the HTML the visitor sees, with no platform ad bar on top. You also do not get a forum, a roster, or a theme builder. If nobody writes or installs those pieces, the site is a blank page with potential.

Neither column wins everything. If nobody in the guild wants to touch HTML and a forum is non-negotiable this week, the builder is the honest choice. If you want your own forms, a domain on your timeline, and the freedom to change the design without asking a widget, hosting fits better. The name-by-name comparison with Shivtr and Guildwork, as well as Guildtag, is in Battlehorns vs Guildtag vs Shivtr vs Guildwork. The wider hosting map is in web hosting for gaming communities.

Your own domain

A subdomain is enough to start: your-guild.battlehorns.net, or an address on the builder's platform. It reads well, it shares well, and it already beats a lost invite. Your own domain (guildname.pt or .com) changes the impression when the guild recruits outside its circle or files sheets with a league.

On a builder, that step is often paid. On Guildtag, "use your own domain" appears on the premium list, not as a free-plan detail. On hosting the path is different: you start on the free-plan subdomain and, when the name is worth the cost, you point the domain at shared hosting. What actually changes — credibility, SSL on the new name, what to put on the page — is in a custom domain for your guild.

Do not buy the domain on day one just because it looks good in a signature if there is no page to put there yet. Do not spend years on someone else's subdomain either, once the guild name is a brand people search for. The test is simple: while the site is an experiment, the subdomain is enough; when the address shows up on applications and partnerships, the domain should be yours.

Forum and recruitment

The forum is the most common reason to pick a builder. It already has boards, member accounts, and a place to apply that does not depend on a form you wrote. That is gold in a guild where nobody is comfortable with PHP.

It also has a hidden cost: moderation. An empty forum, or one full of spam, says the guild stopped. If the real conversation is already on Discord, copying it into a forum only creates two stale places. In that case the site needs a recruitment page, not another message board.

On hosting, recruitment is a page and, if you want it, a candidatura.php that writes into a MariaDB table. The free plan has one database: enough for applications, not for a heavy forum plus a gallery plus a wiki. The reference plan's 700 MB SSD and 5 GB monthly traffic disappear quickly under forum attachments. The page that filters applicants is in the recruitment page guide, and the next step — a member panel that converts — is in recruitment and the member panel.

A useful question before you decide: in the last thirty days, did anyone who is not an officer need a forum, or did they need to read the rules and apply? If it is the second, do not pay for builder complexity the guild will not inhabit.

When Battlehorns fits

Battlehorns fits when you accept this contract: hosting supplies the server tools, the guild supplies the content.

• You want PHP and MariaDB without waiting for a plan that unlocks HTML.
• You want to take the site with you (files and a dump) if you ever move machines.
• The public sees rules, schedule, and applications; the inside stays in GuildOps.
• Someone on the team can maintain a page, or is willing to follow the guild site setup tutorial and the HTML, PHP, and FTP guide.

It does not fit — and it is worth saying so — when the priority is a forum, an imported roster, and a finished theme today, and nobody will open FileZilla. Forcing hosting in that case produces an empty subdomain. A builder does the job better. You can still use GuildOps for operations and leave the public site on the tool the guild will actually update.

The reference free-plan figures — subdomain, PHP 8.3 by default, one database, one FTP user, Let's Encrypt, 700 MB, 5 GB of traffic, ticket support — are in the free-hosting article and on the hosting page. If that page shows different numbers on the day you order, those are the ones that count. The terms make clear that the free plan has quotas and is not a permanent guarantee.

Register the hosting

If the hosting column is the one you chose, the path is short. Do not ask for FTP before you have an account.

1. Create the account with Discord at register.
2. Open shared hosting, go to the client area, and order the free plan if you want to start at no cost.
3. Pick a subdomain with the guild name, easy to say out loud. Avoid admin, www, and test123.
4. Publish a minimal index.html: who you are, when you play, how to join. Confirm the HTTPS padlock before you announce it.

If the certificate or FTP fails, support needs the subdomain and a screenshot, not only "it does not work". The guild site can be small. It does need to be yours enough to explain without depending on a builder — or, if a builder really is the better tool, use it on purpose, not because nobody compared the options.