CodyChat is a PHP + MySQL application, which is good news: it runs on the kind of hosting almost everyone already has, and it scales up cleanly when your community grows. This guide covers the baseline requirements, when to move beyond shared hosting, and the tweaks that keep a busy chat feeling instant. For the installation itself, see the setup guide.
A current PHP release on your host's standard configuration. Set the PHP version from your hosting panel — if a build ever misbehaves, switching versions is the usual first fix.
One database and one user with full access to it. Any normal shared-hosting MySQL plan is fine to start; bigger communities benefit from more memory on the database side.
Chat data is small — messages are text. The real usage is uploads: avatars, images, voice notes. Budget a few GB and let it grow; allow more if you enable media-heavy addons.
Non-negotiable in 2026. Browsers mark plain-HTTP logins as “not secure”, and members notice. Free certificates come with virtually every host — turn one on before launch.
| Stage | What works | Watch for |
|---|---|---|
| Starting out (up to a few hundred active members) | Standard shared hosting with PHP + MySQL | Hosts that throttle CPU hard; test chat during peak hours |
| Growing (thousands of members, heavy addons) | Managed hosting or a small VPS | Database memory and concurrent connections |
| Busy community (always-on traffic) | VPS/dedicated with room to tune PHP-FPM and MySQL | Backups, monitoring and patching become your job — budget the time |
The jump point is rarely “number of messages” — it is usually concurrent users in the room at once plus whatever addons run on every page load.
Settings, categories and userlist metadata can be cached. Most chat “slowness” traces back to repeating heavy queries on every message poll.
Avatars and covers are the heaviest bytes. A CDN (or Cloudflare's free tier) offloads them and shaves a lot off peak load.
Every addon adds queries. Keep the ones your members actually use, and update to current versions — maintainers fix performance, not just bugs.
Daily databases, regular files. A chat's database is its community history — losing it is the one outage you cannot apologize your way out of.
If all of the above sounds like a second job, be honest about it. A hosted room like ChatSocket gives you the same “chat on your website” outcome with none of the server work — free for 7 days, then $9/month. The full comparison lays out the trade-offs honestly, and plenty of owners run both: CodyChat for the main community, a hosted room where maintenance would not pay off.
A PHP + MySQL hosting account with SSL and a few GB of disk. That is genuinely enough to launch — the requirements page for any specific build lists exact versions.
Yes, to start. If the host throttles CPU or the room grows busy, that is your signal to move up to a VPS or managed plan.
No. Almost no CodyChat site needs dedicated hardware; a well-tuned VPS handles large communities comfortably.
Only for the heavy ones. Games, gifts and media addons increase queries and storage — check their listings before choosing a tier of hosting.
Preparing order and redirecting you to the payment processor please wait...