Photon Chat has been the default in-game chat layer for Unity developers for years. It works — but the pricing model, ageing SDK and rigid channel concept can quietly slow your team down. Here's an honest look at how fiveminutes.io compares, and where each one shines.
TL;DR
- Both services give you persistent, channel-based chat for Unity games and web apps.
- Photon Chat bills per concurrent user (CCU) and ties you to the wider Photon ecosystem.
- fiveminutes.io bills on actual usage, ships a single Unity asset, and treats web parity as a first-class citizen.
- If you already run on Photon Realtime/Fusion, staying inside Photon is convenient. Otherwise, fiveminutes.io is usually faster to integrate and cheaper to scale.
At a glance
| Capability | fiveminutes.io | Photon Chat |
|---|---|---|
| Time to first message | < 5 minutes | 15–30 minutes |
| Unity SDK | Single drop-in asset | Multiple packages + AppId setup |
| Web / JavaScript SDK | First-class, same API surface | Limited, lags Unity SDK |
| Pricing model | Usage-based (messages + storage) | Per CCU tier |
| Message history | Built-in, queryable | Limited window, opt-in |
| Moderation tooling | Built-in dashboard + filters | Bring your own |
| Global edge presence | Multi-region by default | Region per app |
| Vendor lock-in | Standalone service | Tied to Photon ecosystem |
Integration experience
Photon Chat's quickstart asks you to register an application in the Photon dashboard, install the Photon Chat package alongside the Photon base libraries, generate an AppId, and wire up the IChatClientListener interface. It's well-documented but there's noticeable ceremony before your first message lands.
fiveminutes.io ships as a single Unity asset. Import it, paste your application key, and you have a working chat client with channels, presence and history. The same API exists for JavaScript and TypeScript, so a companion web client or a moderation dashboard reuses the exact same concepts.
Five-minute integration: Our Unity quickstart targets less than five minutes from import to first message. If you spend longer, that's a bug — let support know.
Pricing and scaling
Photon Chat's pricing is based on Concurrent Users (CCU). It's predictable while you're small, but the jumps between tiers can sting once you cross a threshold during a launch weekend or a streamer spike. You also pay for idle headroom — empty connections still count toward CCU.
fiveminutes.io charges for what your players actually do: messages sent, history retained, and storage consumed. Idle clients are effectively free, and the pricing curve scales linearly rather than in steps. Launch traffic stops being a billing event.
Features your players will notice
Persistent history
Photon Chat keeps a small in-memory window of recent messages. If you want true persistence — players seeing what they missed while offline, search, or compliance archives — you'll be plumbing it into your own database.
fiveminutes.io persists history by default, exposes it via the same SDK, and lets you control retention per channel. Mute notifications, unread counts and 'jump to last read' work out of the box.
Moderation and safety
Player safety is no longer optional. Photon leaves moderation up to you — you'll integrate a third-party filter, build report queues, and stand up a dashboard. fiveminutes.io ships with configurable message filters, a reports inbox, and a moderation dashboard that your community team can use directly.
Web parity
Companion sites, Discord-style web clients and creator tooling all benefit from a first-class web SDK. fiveminutes.io treats Unity and web as equal targets so you don't end up writing a custom bridge.
When Photon Chat is still the right call
- You already run Photon Realtime, Fusion or Quantum and want one vendor invoice.
- Your chat needs are limited to lobby banter with no history, moderation or web client.
- You have an existing Photon AppId, support contract and infrastructure team that knows it well.
When fiveminutes.io wins: You're starting from scratch, you want predictable usage-based pricing, you care about moderation tooling, or you need first-class web support alongside Unity.
Migrating from Photon Chat
Most teams migrate one surface at a time. Start by mirroring your existing channel list inside fiveminutes.io, run both clients in parallel behind a feature flag, and route a slice of traffic to the new service. Once message volume and latency look healthy, flip the flag and decommission the Photon AppId.
Because the Unity asset and the web SDK share an API, the migration becomes mostly mechanical: swap the listener interface for our event hooks, replace ChatClient calls with our client, and you're done.
Try it for yourself
The fastest way to compare is to integrate. Grab the Unity asset, follow the quickstart, and send your first message in under five minutes. If it isn't faster and friendlier than what you have today, we want to hear about it.