Realtime Gateway
Free. The small WebSocket server that Realtime, Live Notifications and Chat all push through. If you own any of those, this is the piece that runs alongside your community and delivers to browsers.
It has always shipped inside the Realtime download. It now has a listing of its own, because a shared dependency deserves its own version number.
Why it is separate
Three applications depend on this one file, and it changes when any of them gains a new kind of channel. Buried inside another product's download, its version was whatever you happened to download last — and the only notice you got was a paragraph in somebody else's changelog.
That matters more than it sounds, because of how the gateway fails. An older gateway does not reject a channel it does not recognise. It drops it in silence: no error, no log line, nothing in the browser console. The socket stays open and looks perfectly healthy, and the feature simply never does anything.
With its own listing you can see at a glance whether yours is current, and you get told when it is not.
What it is
About 250 lines of Node.js. No database, no state on disk, nothing to back up. Subscribes to your Valkey/Redis, fans messages out to the browsers that are entitled to them. Verifies every connection against an HMAC signature your community generates. It knows nothing about your permissions — your server decides who may hear what, and the gateway only checks the signature. Ships with a Dockerfile, a package.json and an .env.example. Docker or plain Node, whichever you prefer. If it goes down your community carries on normally; realtime features simply stop updating until it is back. You need this if you run
Realtime — live topics, presence, typing indicators Live Notifications — notifications the moment they are sent Chat — private messages and rooms You do not need it for anything else, and it does nothing on its own.
Already have it?
The copy attached to the Realtime listing is the same file. Take whichever is newer — they are built together and released together. Going forward this listing is the one to watch.

Font Awesome — use the icons you already pay for
Invision Community ships Font Awesome 6 Free and gives you no way to change it. If you have a Font Awesome Pro subscription, none of it works here. If you want an icon added since 2024, it isn't there.
This is a small, free application that fixes both.
It costs nothing. There is no licence key and nothing to renew. If you use Kit mode you are using the Font Awesome subscription you already have — this simply lets Invision Community see it.
Two modes
Mode
What you get
Font Awesome 7 Free
2,606 icons instead of 2,492 — 115 more than Invision ships. No account needed.
Your Kit
The full Pro set — around 68,000 icons across six styles, plus Sharp and Duotone if your plan includes them.
Both load from Font Awesome's own CDN, not a third-party mirror.
Kit setup is one field
Paste your Kit ID and save. It accepts whatever you have to hand — the bare ID, the kit URL, or the entire <script> tag copied from your Font Awesome dashboard. There is a Test the connection button that tells you what actually loaded before you go looking at your site.
Nothing breaks
This is the part worth understanding, because it is why the application is safe to install on a live community.
Invision Community loads its own Font Awesome from a core template that offers no way to remove it. Rather than edit that file — which an upgrade would overwrite — this loads afterwards and takes precedence.
That has a real benefit beyond upgrade safety. Font Awesome 7 dropped exactly one icon that existed in 6 (fa-vector-square). Because Invision's copy is still underneath, that icon keeps working. An application that replaced Font Awesome outright would have broken it silently on every site using it.
The cost is about 70KB of stylesheet that goes unused. That is the trade, stated plainly.
What you control
Which mode — Free 7 or your Kit
Which release of Font Awesome 7
Whether the AdminCP uses it too, or stays exactly as Invision ships it
Turn it off at any time and you are back to stock, immediately
Requirements
Invision Community 5.0 or newer (self-hosted)
For Kit mode: a Font Awesome account with a published kit. Free plans have kits too.
Outbound HTTPS from visitors' browsers to Font Awesome's CDN
No core files are edited, no database tables are created, and nothing is stored except your settings.

Tag Colours — your tags, finally telling them apart
Invision Community already has tags. What it does not have is any way to make them look like anything. Every tag on your site is the same shape and the same grey, so a topic tagged Solved is visually identical to one tagged Urgent, and members read every label one at a time.
Tag Colours fixes that in about a minute.
Solved Bug Report Feature Request Announcement Off Topic
It builds on the tags you already have
This is not a replacement tag system. There is nothing to migrate, no second set of labels to maintain, and no new way for your members to tag things. It reads the tags already on your community and lets you pick a colour for each one.
Because it works with the built-in system, the colours turn up everywhere tags already appear — topic view, topic lists, search results, tag pages, and the Blogs, Calendar and Pages applications too.
Setting it up
The admin screen lists every tag actually in use on your community, most-used first, with a note of how many items carry it. Click a tag, pick a colour, done.
Or click Colour them for me and every uncoloured tag is given a distinct colour from a readable palette — a sensible starting point you can then adjust. It never overwrites a colour you chose yourself, and it will not hand two tags the same colour.
Three styles
Solid — the tag is filled with your colour
Soft — a tinted background with coloured text, for a lighter touch
Outline — a coloured border and text on a transparent background
Pick one and it applies to every coloured tag, so your tags stay consistent with each other whatever your theme looks like.
Readable by default
Choose a tag colour and the text colour is worked out for you, using the same contrast maths the accessibility guidelines use — dark text on light colours, light text on dark ones. You never end up with a yellow tag nobody can read. If you want to override it on a particular tag, you can.
Built to stay out of the way
No core files are edited and no templates are overridden, so upgrading Invision Community will not break it and will not undo your work.
One small stylesheet is added to the page, cached permanently by the browser and only re-fetched when you actually change a colour. There is no JavaScript and no per-page work.
Turning it off restores your theme's own tag styling immediately — and keeps your colour choices, so turning it back on picks up where you left off.
Uninstalling leaves no trace. Your tags are Invision Community's tags; only the colours belong to this application.
Requirements
Invision Community 5.0 or newer (self-hosted)
Nothing else — no external service, no API key, no background jobs

Community Experts — free
Invision Community has a Community Experts feature. Members you name as experts get a badge on their posts in the forums they actually know about, and get an email when a question in one of those forums goes unanswered.
It is Cloud only. On a self-hosted community it is switched off, and there is no setting anywhere that turns it on.
This does not imitate that feature. It completes it.
Almost all of Community Experts is already sitting in your installation, doing nothing:
The badge
The graduation-cap badge, its styling, and the follow-this-expert button are all core templates that already ship with your community.
The email
The "questions waiting for you" email — both the HTML and plain-text versions — is a core template.
The unsubscribe link
Core already knows how to handle it and which preference to change.
The data
Core already has the table that records who is an expert in which forum, and the member settings for opting out and being blocked.
What is missing is the switch. Every one of those pieces is behind a check for the Cloud platform, so none of them can ever run. This application supplies what is missing and uses core's own badge, core's own email, core's own unsubscribe handling and core's own table.
The practical result: what your members see is the real feature, not a lookalike. And because the assignments live in core's own table, a community that later moves to Invision Community Cloud finds its experts already in place.
Named per forum, which is the whole point
Somebody who knows billing inside out is not an authority on off-topic. Experts are named per forum and the badge only appears where they actually are one — a badge that follows a member everywhere is worth considerably less than one that does not.
Naming experts automatically, if you want to
Off by default. When enabled, anyone who clears both of these tests in a forum is given the badge there:
Accepted answers in that forum. Replies of theirs that somebody marked as the answer. This is the strongest evidence available, because the person with the problem said so.
Posts in that forum. A second test, so one lucky answer is not enough on its own.
Both are counted inside the forum, deliberately. Promoting on a site-wide reputation score or post count measures how much somebody posts, not what they know — on a community whose busiest forum is off-topic, that names the most prolific chatterer an authority on billing.
The admin screen lists everyone who currently meets the tests whether or not automatic naming is switched on, so you can see exactly who the rule would pick before trusting it with the decision. Nobody is ever removed automatically: taking a badge away stays a decision a person makes.
Emails that produce answers
Once an hour, experts are emailed about questions in their forums that nobody has answered. It skips anything they started, anything they have already replied to, and anything they have already been told about — an expert is never sent the same question twice. One email lists several questions rather than sending several emails.
Members can turn it off from their own notification settings, or from the link in the email itself. Both routes work because both are core's.
Also
An audit trail of who was named or removed, when, and by whom — with automatic changes marked as such and the reason recorded.
Members can opt out of being shown as an expert without losing their assignments.
Administrators can block a member from ever showing as an expert.
Restrict by group, so the badge can only reach the people you intend.
No core files are edited. Upgrading Invision Community will not break it.
Honest about the limits
Forums only. Experts are named against forums, because that is what core's own data does.
Automatic naming needs "solved" enabled in a forum. Without accepted answers there is no evidence to promote on, so nobody is ever named automatically in a forum that does not use it. Naming people by hand works everywhere.
The emails need a working task scheduler. Without one, nothing is sent.
Three language strings belong to core's namespace. They have to, because they are the strings for core's own email, which does not ship with them. If you ever migrate to Invision Community Cloud, uninstall this application first — see the setup guide.
Requirements
Invision Community 5.0 or newer (self-hosted)
The Forums application
A running task scheduler, for the emails and for automatic naming
Free. No key, no account, no external service.