Top Board

Top Board

Nobody scrolls past a board that moves
Topboard puts a live activity board at the top of your community: the newest posts, discussions heating up right now, your most active members, and sponsored slots you can sell to help fund it all.
It refreshes itself while people read, and turns some of the most valuable screen space on your site into something members watch and sponsors can pay for.
Demo: https://demo.invisionite.com/

The problem
A forum index is a list of containers. The actual life of your community, the reply posted forty seconds ago, the topic that suddenly took off, the member on a posting streak, is buried one click deeper.
Visitors land on your busiest page and see furniture.
Monetizing that page is its own headache. Banner ads look like ads, so people learn to ignore them or block them outright. Selling placements manually means invoices, start dates in spreadsheets, expiry dates to remember, and renewal reminders someone eventually forgets to send.
Topboard fixes both halves: it surfaces the activity and runs the sponsorship pipeline for you.

Three looks, one widget
Every widget instance gets its own style:
Native Feed: clean stacked rows that feel like part of the rest of your community.
Classic Table: the column-based statistics board forum veterans remember, with topic, forum, replies, views, activity, and last poster. On phones it restacks into tidy rows instead of forcing a sideways scroll.
Spotlight: card-based headline slots with full-image sponsor cards and text overlaid on the artwork.

Eight tabs, plus two of your own
New posts, New topics, Featured, Latest files, Trending, Most replies, Most viewed, and Most reacted.
Choose the tabs you want for each widget, set the number of items, and limit them to selected forums if needed.
You can also add up to two custom tabs with your own label and forum selection. An Introductions tab for greeters, a Marketplace tab for traders, or whatever fits your community.
Trending and Most reacted rank content within a time window you control, so they reward what is happening now instead of what happened in 2019.

Alive without a reload
A countdown sits in the tab bar and Topboard refreshes itself on schedule while keeping the reader on the tab they were viewing. Impatient members get a manual refresh button too.
Members who do not care about the board can collapse it into a slim strip. The Top Members panel folds away separately, letting the activity area use the full width.
Both choices are remembered per device.
A collapsed board also stops refreshing and stops counting impressions. No wasted requests and no phantom ad views.

Headline slots
Above the tabs sit your promoted rows: pinned topics you want seen and sponsored placements you have sold, each with its own label chip.
A slot can point to an internal topic or work as a completely standalone external ad with its own title, description, link, and image.
Images appear as neat thumbnails in Native Feed and Classic Table, and become full-image cards in Spotlight.
Sponsored slots can also be hidden from selected member groups, which gives you an easy premium perk: upgrade and the ads disappear.

Monetize the app without any effort
With Commerce installed, Topboard becomes self-service advertising.
You create the packages: price, duration, slot type, label, and an optional Most popular highlight.
Members buy through the campaign storefront, pay using your normal Commerce checkout, and then submit the topic or advertisement they want to promote through a guided form.
Nothing goes live automatically. Every submission goes through staff approval first.
Once approved, Topboard handles the schedule. Campaigns start, run, expire, and become available for renewal without you tracking dates manually.

Numbers a sponsor can trust
Impressions are counted from the reader's browser, deduplicated per visitor with a cooldown, and only counted while the board is actually visible on screen.
Clicks pass through a tracked redirect.
Every slot gets daily impression and click data alongside its lifetime totals.
Sponsors see their own report card at /campaigns, with stat tiles, click-through rate, a 14-day chart, and a renewal button that extends an active campaign or relaunches an expired one through normal checkout.
You get the same picture across the entire site in the ACP Performance dashboard: totals, a 30-day chart, and every campaign with its own sparkline.

Top members included
A ranked member panel, based on posts or reputation, sits beside the activity tabs like the classic statistics boxes many communities used for years.
A standalone Top Members widget is included for sidebars too.

In short
Topboard is a live, tabbed activity board with three display styles, eight activity sources, custom forum tabs, a Top Members panel, and promoted headline slots.
Behind it sits impression and click tracking, self-service Commerce campaigns with staff approval, sponsor-facing performance charts and renewals, and an ACP dashboard that shows you the whole picture.
The front of your community, finally earning its keep.

IPS5.0.0+

15 hours ago15 hr

Nobody scrolls past a board that moves
Topboard puts a live activity board at the top of your community: the newest posts, discussions heating up right now, your most active members, and sponsored slots you can sell to help fund it all.
It refreshes itself while people read, and turns some of the most valuable screen space on your site into something members watch and sponsors can pay for.
Demo: https://demo.invisionite.com/

The problem
A forum index is a list of containers. The actual life of your community, the reply posted forty seconds ago, the topic that suddenly took off, the member on a posting streak, is buried one click deeper.
Visitors land on your busiest page and see furniture.
Monetizing that page is its own headache. Banner ads look like ads, so people learn to ignore them or block them outright. Selling placements manually means invoices, start dates in spreadsheets, expiry dates to remember, and renewal reminders someone eventually forgets to send.
Topboard fixes both halves: it surfaces the activity and runs the sponsorship pipeline for you.

Three looks, one widget
Every widget instance gets its own style:
Native Feed: clean stacked rows that feel like part of the rest of your community.
Classic Table: the column-based statistics board forum veterans remember, with topic, forum, replies, views, activity, and last poster. On phones it restacks into tidy rows instead of forcing a sideways scroll.
Spotlight: card-based headline slots with full-image sponsor cards and text overlaid on the artwork.

Eight tabs, plus two of your own
New posts, New topics, Featured, Latest files, Trending, Most replies, Most viewed, and Most reacted.
Choose the tabs you want for each widget, set the number of items, and limit them to selected forums if needed.
You can also add up to two custom tabs with your own label and forum selection. An Introductions tab for greeters, a Marketplace tab for traders, or whatever fits your community.
Trending and Most reacted rank content within a time window you control, so they reward what is happening now instead of what happened in 2019.

Alive without a reload
A countdown sits in the tab bar and Topboard refreshes itself on schedule while keeping the reader on the tab they were viewing. Impatient members get a manual refresh button too.
Members who do not care about the board can collapse it into a slim strip. The Top Members panel folds away separately, letting the activity area use the full width.
Both choices are remembered per device.
A collapsed board also stops refreshing and stops counting impressions. No wasted requests and no phantom ad views.

Headline slots
Above the tabs sit your promoted rows: pinned topics you want seen and sponsored placements you have sold, each with its own label chip.
A slot can point to an internal topic or work as a completely standalone external ad with its own title, description, link, and image.
Images appear as neat thumbnails in Native Feed and Classic Table, and become full-image cards in Spotlight.
Sponsored slots can also be hidden from selected member groups, which gives you an easy premium perk: upgrade and the ads disappear.

Monetize the app without any effort
With Commerce installed, Topboard becomes self-service advertising.
You create the packages: price, duration, slot type, label, and an optional Most popular highlight.
Members buy through the campaign storefront, pay using your normal Commerce checkout, and then submit the topic or advertisement they want to promote through a guided form.
Nothing goes live automatically. Every submission goes through staff approval first.
Once approved, Topboard handles the schedule. Campaigns start, run, expire, and become available for renewal without you tracking dates manually.

Numbers a sponsor can trust
Impressions are counted from the reader's browser, deduplicated per visitor with a cooldown, and only counted while the board is actually visible on screen.
Clicks pass through a tracked redirect.
Every slot gets daily impression and click data alongside its lifetime totals.
Sponsors see their own report card at /campaigns, with stat tiles, click-through rate, a 14-day chart, and a renewal button that extends an active campaign or relaunches an expired one through normal checkout.
You get the same picture across the entire site in the ACP Performance dashboard: totals, a 30-day chart, and every campaign with its own sparkline.

Top members included
A ranked member panel, based on posts or reputation, sits beside the activity tabs like the classic statistics boxes many communities used for years.
A standalone Top Members widget is included for sidebars too.

In short
Topboard is a live, tabbed activity board with three display styles, eight activity sources, custom forum tabs, a Top Members panel, and promoted headline slots.
Behind it sits impression and click tracking, self-service Commerce campaigns with staff approval, sponsor-facing performance charts and renewals, and an ACP dashboard that shows you the whole picture.
The front of your community, finally earning its keep.

25 USD
12.50 USD/year

25 USD
12.50 USD/year

[ChatPro] Voice Rooms

[ChatPro] Voice Rooms

Voice Rooms for ChatPro brings real-time, Clubhouse-style interactive audio spaces directly into your chat rooms. It enables members to connect, request speaker seats on a virtual stage, and engage in crystal-clear live voice discussions seamlessly.
Key Features:
Built on top of the modern LiveKit WebRTC framework, ensuring industry-grade, ultra-low latency, and high-performance audio communication.
Supports up to 8 dedicated speaker seats for active presenters, with intuitive empty seat claiming indicators.
Real-time Speaker Highlighting: Dynamic visual glow effects that highlight who is speaking for natural, fluid conversations.
Empower room owners and moderators to manage the stage by muting individuals, kicking users from seats, or toggling the stage on and off.
Perfect for hosting live podcasts, interactive Q&A sessions, community meetups, or gaming voice chats right inside your platform.

IPS5.0.0+

Monday at 02:58 AM4 days

Voice Rooms for ChatPro brings real-time, Clubhouse-style interactive audio spaces directly into your chat rooms. It enables members to connect, request speaker seats on a virtual stage, and engage in crystal-clear live voice discussions seamlessly.
Key Features:
Built on top of the modern LiveKit WebRTC framework, ensuring industry-grade, ultra-low latency, and high-performance audio communication.
Supports up to 8 dedicated speaker seats for active presenters, with intuitive empty seat claiming indicators.
Real-time Speaker Highlighting: Dynamic visual glow effects that highlight who is speaking for natural, fluid conversations.
Empower room owners and moderators to manage the stage by muting individuals, kicking users from seats, or toggling the stage on and off.
Perfect for hosting live podcasts, interactive Q&A sessions, community meetups, or gaming voice chats right inside your platform.

Free

Free

Music

Music

A music library your members can add to, and a live station page that shows what is on air right now. One application, because a community that has a radio station usually has an archive as well, and running two add-ons that do not know about each other is how you end up with neither.
The library
Releases live in categories you set up, each with artwork, an artist, a year, a genre and a track list. Members open a release and play a track straight from the page — no download, no separate player, no leaving the community.
Tracks are playable by click or keyboard, and the list rolls on to the next one the way a record does.
Releases are proper Invision Community content: search, tags, comments, reactions, follows, moderation, reports and the activity stream all work because it is built on the same foundation as your forums.
Optionally start a discussion topic for every release.
Members can add music, on your terms
Four separate gates decide who may upload: the master switch, a per-group permission, the category, and your own moderation queue. Turn uploads off entirely and only staff add music — everything already added stays exactly where it is.
Tags are read from the files themselves
Upload an MP3, FLAC, M4A or OGG and the title, artist, track number, length and embedded cover art are filled in from the file. Whatever the member typed always wins; the file only fills the blanks.
No external tools, no shell access, no extra PHP extensions. The tag reader is part of the application. It does not shell out to ffprobe, it does not need getID3, and it works on shared hosting where you cannot install anything.
The station
Point Music at your stream and the station page shows what is playing right now — artwork, artist, title, the live listener count, and recently played.
Works with AzuraCast, Icecast and SHOUTcast. AzuraCast needs no API key unless you have closed off its public endpoint.
It knows the difference between a real DJ and the AutoDJ, and says so — a live badge with the presenter's name when somebody is actually on the decks.
Recently played survives quiet spells. Icecast and SHOUTcast publish no history at all and AzuraCast often returns none, so Music keeps its own airplay log and shows that instead of an empty box.
A Test button in the AdminCP asks your station and reports exactly what came back.
A player that follows people around your community
A small dock sits at the foot of every page with the station playing in it. Members can hide it, and it stays hidden.
Being straight with you about one thing. Invision Community loads a whole new page on every click, which stops any audio element on it. So the dock reconnects on the next page rather than pretending to play through the click — and there is a pop-out window for anyone who wants the music to genuinely keep going while they read. Both ship. Neither is oversold.
Built to leave running
One check per interval, shared by everybody. Fifty members on the station page is one request to your radio server, not fifty.
Every call to your station is capped at four seconds and every failure becomes a plain “not answering”.
Uploads go through Invision Community's own file storage, so Amazon S3 and other storage methods work.
The airplay log trims itself.
What you need
For the library, nothing at all — install it and it works. For the station, the address of an AzuraCast, Icecast or SHOUTcast server. The setup guide walks through all three, and the library is entirely usable without a station if you never intend to broadcast.

IPS5.0.0+

Monday at 01:52 AM5 days

A music library your members can add to, and a live station page that shows what is on air right now. One application, because a community that has a radio station usually has an archive as well, and running two add-ons that do not know about each other is how you end up with neither.
The library
Releases live in categories you set up, each with artwork, an artist, a year, a genre and a track list. Members open a release and play a track straight from the page — no download, no separate player, no leaving the community.
Tracks are playable by click or keyboard, and the list rolls on to the next one the way a record does.
Releases are proper Invision Community content: search, tags, comments, reactions, follows, moderation, reports and the activity stream all work because it is built on the same foundation as your forums.
Optionally start a discussion topic for every release.
Members can add music, on your terms
Four separate gates decide who may upload: the master switch, a per-group permission, the category, and your own moderation queue. Turn uploads off entirely and only staff add music — everything already added stays exactly where it is.
Tags are read from the files themselves
Upload an MP3, FLAC, M4A or OGG and the title, artist, track number, length and embedded cover art are filled in from the file. Whatever the member typed always wins; the file only fills the blanks.
No external tools, no shell access, no extra PHP extensions. The tag reader is part of the application. It does not shell out to ffprobe, it does not need getID3, and it works on shared hosting where you cannot install anything.
The station
Point Music at your stream and the station page shows what is playing right now — artwork, artist, title, the live listener count, and recently played.
Works with AzuraCast, Icecast and SHOUTcast. AzuraCast needs no API key unless you have closed off its public endpoint.
It knows the difference between a real DJ and the AutoDJ, and says so — a live badge with the presenter's name when somebody is actually on the decks.
Recently played survives quiet spells. Icecast and SHOUTcast publish no history at all and AzuraCast often returns none, so Music keeps its own airplay log and shows that instead of an empty box.
A Test button in the AdminCP asks your station and reports exactly what came back.
A player that follows people around your community
A small dock sits at the foot of every page with the station playing in it. Members can hide it, and it stays hidden.
Being straight with you about one thing. Invision Community loads a whole new page on every click, which stops any audio element on it. So the dock reconnects on the next page rather than pretending to play through the click — and there is a pop-out window for anyone who wants the music to genuinely keep going while they read. Both ship. Neither is oversold.
Built to leave running
One check per interval, shared by everybody. Fifty members on the station page is one request to your radio server, not fifty.
Every call to your station is capped at four seconds and every failure becomes a plain “not answering”.
Uploads go through Invision Community's own file storage, so Amazon S3 and other storage methods work.
The airplay log trims itself.
What you need
For the library, nothing at all — install it and it works. For the station, the address of an AzuraCast, Icecast or SHOUTcast server. The setup guide walks through all three, and the library is entirely usable without a station if you never intend to broadcast.

60.00 USD
22.00 USD / 6 months

60.00 USD
22.00 USD / 6 months

GitHub Login Handler

GitHub Login Handler

This application connects a GitHub account to an IPS5 account. It allows users to sign up and sign in using their GitHub account, as well as synchronize their display name and/or profile photo.
You must register your application at https://github.com/settings/developers to obtain:
Client ID
Secret

IPS5.0.0+

Sunday at 11:33 PM5 days

This application connects a GitHub account to an IPS5 account. It allows users to sign up and sign in using their GitHub account, as well as synchronize their display name and/or profile photo.
You must register your application at https://github.com/settings/developers to obtain:
Client ID
Secret

FREE

FREE

Developer Sign-In

Developer Sign-In

Developer Sign-In
Let your members sign in with GitHub, GitLab or Bitbucket — the accounts they already have, on the platforms they already use every day.
Invision Community ships sign-in handlers for Facebook, Google, Microsoft, LinkedIn, Apple and X. Excellent for a general community. Not much use if your members are developers.
Who this is for
Software and open-source communities — support forums, plugin and mod communities, anywhere the conversation is about code. Homelab, self-hosting and sysadmin communities, where a GitHub account is more universal than a Facebook one. Companies running their own GitLab. A community that self-hosts its forum very often self-hosts its GitLab too, and this connects the two. Your instance address is a field on the settings screen. Game and modding communities whose members publish their work on one of these platforms already. What it does
Three providers, one application. Enable one, two or all three. Each is a separate sign-in button with its own credentials, and each can be turned on and off independently. Verified email addresses, carried across. This is the part that is fiddly to do by hand — see below. Avatars and names come across too, and you decide whether the provider's name is used or the member picks their own. Works alongside everything else. Passwords, existing social logins and any other handler carry on exactly as they are. A member can link a provider to an account they already have, from their account settings, and unlink it there just as easily. Self-hosted GitLab is supported properly, not as an afterthought — every address the handler uses is built from the instance you name. The email problem, and why it is worth paying to skip
Invision Community includes a generic OAuth handler that can, in principle, be pointed at anything. The reason people give up on it for these three platforms is the email address.
PlatformWhat actually happens GitHubThe profile carries only the public address, and most developers keep theirs private — so it arrives empty. The real address needs a second request, a specific permission, and filtering down to the one that is both primary and confirmed. BitbucketThe profile carries no address at all. Same story: a second request, and permissions that have to be set on the application itself rather than asked for at sign-in. GitLabStraightforward — provided you ask for the right scope. Get this wrong and sign-in still appears to work. Members simply arrive with no email address and are asked to type one, which is exactly the friction you installed a one-click sign-in to remove.
An unverified address is never accepted. Only an address the provider itself confirms as belonging to the account holder is used. Anything less would let somebody register an account elsewhere against one of your members' addresses and land on their community account.
What it does not do
It does not import repositories, issues or commits, and it does not post anything to your community. It does not sync organisations, teams or repository access to member groups. It does not replace your existing sign-in methods. It adds to them. Requirements
Invision Community 5. A free OAuth application on each platform you want to offer — a few minutes each, and the setup guide walks through all three with the exact values to paste. No cron job, no theme edit, and no third-party service beyond the platforms themselves.

IPS5.0.0+

Sunday at 09:47 PM5 days

Developer Sign-In
Let your members sign in with GitHub, GitLab or Bitbucket — the accounts they already have, on the platforms they already use every day.
Invision Community ships sign-in handlers for Facebook, Google, Microsoft, LinkedIn, Apple and X. Excellent for a general community. Not much use if your members are developers.
Who this is for
Software and open-source communities — support forums, plugin and mod communities, anywhere the conversation is about code. Homelab, self-hosting and sysadmin communities, where a GitHub account is more universal than a Facebook one. Companies running their own GitLab. A community that self-hosts its forum very often self-hosts its GitLab too, and this connects the two. Your instance address is a field on the settings screen. Game and modding communities whose members publish their work on one of these platforms already. What it does
Three providers, one application. Enable one, two or all three. Each is a separate sign-in button with its own credentials, and each can be turned on and off independently. Verified email addresses, carried across. This is the part that is fiddly to do by hand — see below. Avatars and names come across too, and you decide whether the provider's name is used or the member picks their own. Works alongside everything else. Passwords, existing social logins and any other handler carry on exactly as they are. A member can link a provider to an account they already have, from their account settings, and unlink it there just as easily. Self-hosted GitLab is supported properly, not as an afterthought — every address the handler uses is built from the instance you name. The email problem, and why it is worth paying to skip
Invision Community includes a generic OAuth handler that can, in principle, be pointed at anything. The reason people give up on it for these three platforms is the email address.
PlatformWhat actually happens GitHubThe profile carries only the public address, and most developers keep theirs private — so it arrives empty. The real address needs a second request, a specific permission, and filtering down to the one that is both primary and confirmed. BitbucketThe profile carries no address at all. Same story: a second request, and permissions that have to be set on the application itself rather than asked for at sign-in. GitLabStraightforward — provided you ask for the right scope. Get this wrong and sign-in still appears to work. Members simply arrive with no email address and are asked to type one, which is exactly the friction you installed a one-click sign-in to remove.
An unverified address is never accepted. Only an address the provider itself confirms as belonging to the account holder is used. Anything less would let somebody register an account elsewhere against one of your members' addresses and land on their community account.
What it does not do
It does not import repositories, issues or commits, and it does not post anything to your community. It does not sync organisations, teams or repository access to member groups. It does not replace your existing sign-in methods. It adds to them. Requirements
Invision Community 5. A free OAuth application on each platform you want to offer — a few minutes each, and the setup guide walks through all three with the exact values to paste. No cron job, no theme edit, and no third-party service beyond the platforms themselves.

45.00 USD
20.00 USD / 6 months

45.00 USD
20.00 USD / 6 months

Realtime Gateway

Realtime Gateway

Works with: Realtime, Live Notifications, Chat, Chat Calls and the Chat Bundle — all of which need this to deliver anything live. Live Topics can use it but does not require it. Nothing else needs it, and on its own it adds no feature to your community.
Realtime Gateway
Free. The small WebSocket server that Realtime, Live Notifications, Chat and Chat Calls 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
Several 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 Chat Calls — voice and video, through the same connection Chat uses Chat Bundle — both of the above Live Topics can use it and does not require it: without a gateway it falls back to a timed refresh, so it works either way and simply feels less immediate.
Nothing else I publish needs it, and it does nothing on its own. If you do not own one of the applications above, there is nothing here to install.
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.

IPS5.0.0+

Sunday at 09:37 PM5 days

Works with: Realtime, Live Notifications, Chat, Chat Calls and the Chat Bundle — all of which need this to deliver anything live. Live Topics can use it but does not require it. Nothing else needs it, and on its own it adds no feature to your community.
Realtime Gateway
Free. The small WebSocket server that Realtime, Live Notifications, Chat and Chat Calls 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
Several 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 Chat Calls — voice and video, through the same connection Chat uses Chat Bundle — both of the above Live Topics can use it and does not require it: without a gateway it falls back to a timed refresh, so it works either way and simply feels less immediate.
Nothing else I publish needs it, and it does nothing on its own. If you do not own one of the applications above, there is nothing here to install.
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.

Free
Free

Free
Free

Chat Bundle

Chat Bundle

Chat Bundle
Chat and Chat Calls together — messages, rooms, and voice and video calling, all on your own server.
$135 instead of $160 bought separately, and $50 every six months instead of $60. The same two applications, the same files, one purchase.
What you get
ApplicationWhat it doesOn its own ChatA launcher on every page. Private messages, public rooms, invite-only private rooms, typing indicators, images and files, moderation.$95 + $35/6mo Chat CallsVoice and video calling from any one-to-one conversation. Peer to peer, never recorded, never through your server.$65 + $25/6mo Also included: a ready-made coturn setup for calls, which is the part most people would otherwise spend an afternoon on.
Why they are sold together
Calls are an add-on to Chat and do nothing without it. If you want calling at all, you need both — so this is simply the cheaper way to buy them.
If you only want text chat, buy Chat on its own. Nothing here is held back from it.
Requirements
Invision Community 5 Realtime, with a current gateway. The gateway is free and has its own listing. HTTPS, for calls — browsers refuse microphone and camera access on an insecure page. A TURN server for calls. The setup is included and takes about ten minutes. Worth knowing before you buy
Calling is one to one in this version. Group calling needs a different piece of server software with real processing cost, and is planned rather than promised. Chat needs a live connection. There is no polling fallback, deliberately — a chat that refreshes every thirty seconds is a slow forum, not a chat. Without Realtime connected the launcher does not appear at all. Nothing leaves your server. No third-party chat service, no per-message pricing, no monthly bill that grows with your community.

IPS5.0.0+

Sunday at 09:32 PM5 days

Chat Bundle
Chat and Chat Calls together — messages, rooms, and voice and video calling, all on your own server.
$135 instead of $160 bought separately, and $50 every six months instead of $60. The same two applications, the same files, one purchase.
What you get
ApplicationWhat it doesOn its own ChatA launcher on every page. Private messages, public rooms, invite-only private rooms, typing indicators, images and files, moderation.$95 + $35/6mo Chat CallsVoice and video calling from any one-to-one conversation. Peer to peer, never recorded, never through your server.$65 + $25/6mo Also included: a ready-made coturn setup for calls, which is the part most people would otherwise spend an afternoon on.
Why they are sold together
Calls are an add-on to Chat and do nothing without it. If you want calling at all, you need both — so this is simply the cheaper way to buy them.
If you only want text chat, buy Chat on its own. Nothing here is held back from it.
Requirements
Invision Community 5 Realtime, with a current gateway. The gateway is free and has its own listing. HTTPS, for calls — browsers refuse microphone and camera access on an insecure page. A TURN server for calls. The setup is included and takes about ten minutes. Worth knowing before you buy
Calling is one to one in this version. Group calling needs a different piece of server software with real processing cost, and is planned rather than promised. Chat needs a live connection. There is no polling fallback, deliberately — a chat that refreshes every thirty seconds is a slow forum, not a chat. Without Realtime connected the launcher does not appear at all. Nothing leaves your server. No third-party chat service, no per-message pricing, no monthly bill that grows with your community.

135.00 USD
50.00 USD / 6 months

135.00 USD
50.00 USD / 6 months

Podcast Bundle

Podcast Bundle

Everything you need to run a podcast from your community and get it onto Apple Podcasts and Spotify — the Podcast app and Podcast Studio, together, for less than buying them apart.
Buy the bundle and save against the two on their own. One purchase, both apps, one renewal. Podcast — host the show
A feed Apple Podcasts, Spotify, Overcast and the rest will accept — the iTunes namespace, owner verification, categories and artwork done to spec. Permanent, opaque episode IDs, so renaming an episode never makes every subscriber re-download your back catalogue. Schedule episodes, keep drafts invisible, and give each episode its own forum topic so the conversation happens with your members. A page and the browser's own audio player per show and per episode. No third-party host, no monthly fee — the feed address is yours. Podcast Studio — publish and distribute it
A guided walk-through to get each show onto Apple Podcasts and Spotify, tracking where every show stands on each. Instant publishing over WebSub: the moment you publish, directories that honour it — Apple among them — fetch the new episode in minutes instead of hours. A pre-flight check that tells you exactly what would get a show rejected before you submit it. It can read the ownership verification code out of your mailbox for you — optional, read-only, encrypted. What you need
Invision Community 5. Install Podcast first, then Podcast Studio. Everything else is built in — no external service to sign up for.

IPS5.0.0+

Sunday at 09:25 PM5 days

Everything you need to run a podcast from your community and get it onto Apple Podcasts and Spotify — the Podcast app and Podcast Studio, together, for less than buying them apart.
Buy the bundle and save against the two on their own. One purchase, both apps, one renewal. Podcast — host the show
A feed Apple Podcasts, Spotify, Overcast and the rest will accept — the iTunes namespace, owner verification, categories and artwork done to spec. Permanent, opaque episode IDs, so renaming an episode never makes every subscriber re-download your back catalogue. Schedule episodes, keep drafts invisible, and give each episode its own forum topic so the conversation happens with your members. A page and the browser's own audio player per show and per episode. No third-party host, no monthly fee — the feed address is yours. Podcast Studio — publish and distribute it
A guided walk-through to get each show onto Apple Podcasts and Spotify, tracking where every show stands on each. Instant publishing over WebSub: the moment you publish, directories that honour it — Apple among them — fetch the new episode in minutes instead of hours. A pre-flight check that tells you exactly what would get a show rejected before you submit it. It can read the ownership verification code out of your mailbox for you — optional, read-only, encrypted. What you need
Invision Community 5. Install Podcast first, then Podcast Studio. Everything else is built in — no external service to sign up for.

69.00 USD
27.00 USD / 6 months

69.00 USD
27.00 USD / 6 months

Community Experts

Community Experts

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 badgeThe graduation-cap badge, its styling, and the follow-this-expert button are all core templates that already ship with your community. The emailThe "questions waiting for you" email — both the HTML and plain-text versions — is a core template. The unsubscribe linkCore already knows how to handle it and which preference to change. The dataCore 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.

IPS5.0.0+

Sunday at 09:14 PM5 days

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 badgeThe graduation-cap badge, its styling, and the follow-this-expert button are all core templates that already ship with your community. The emailThe "questions waiting for you" email — both the HTML and plain-text versions — is a core template. The unsubscribe linkCore already knows how to handle it and which preference to change. The dataCore 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.

Free
Free

Free
Free

Profile Photo Gallery

Profile Photo Gallery

Profile Photo Gallery
Give your members a set of profile photos to choose from, instead of leaving every avatar to whatever they happen to upload.
You supply the photos. Members pick one from their account settings, and it becomes their profile photo everywhere on the community — topics, profiles, the member list, hovercards, notifications.
Why communities want this
Younger or moderated communities where letting members upload arbitrary images is a moderation problem you would rather not have. Themed communities — a game, a show, a team — where a set of house avatars is part of the character of the place. Anyone tired of the letter avatar. Most members never set a photo at all. A row of ready-made ones they can pick with a single click converts far better than an upload form. What it does
Photo sets. Group your photos however you like — "Mascots", "Seasonal", "Staff" — each with its own heading that members see. Restrict a set to member groups. Staff-only avatars, supporter-only avatars, a set that only appears for a promoted group. Secondary groups count, so a member given a staff group as a secondary sees the staff photos. Members choose from their account settings, in a tab alongside Email Address and Password, where they already go to change things about their account. One click to change, one click to remove. The photo they are wearing is marked, so it is obvious what they have. See what is actually being used. Every photo in the AdminCP shows how many members are wearing it, and deleting one that is in use warns you first. Upload in bulk. Select a folder's worth of images at once; they are resized on the way in. How it stores them
One copy of each photo, shared by everyone who chose it — not a duplicate per member. A community of five thousand members wearing twenty avatars stores twenty images.
It uses the same mechanism Invision Community's own Gallery application uses for this, so photos work everywhere a profile photo appears, with no theme edits and no template hooks. They can also be moved to S3 or any other storage you have configured, from the AdminCP screen you already use for that.
What it does not do
It does not remove or replace your members' ability to upload their own photo. That stays exactly as your group settings have it — the gallery is an additional way to get one, not a restriction. If you want uploads switched off, that is a group setting in Invision Community itself. It does not import photos from anywhere. You upload the images you want offered. Requirements
Invision Community 5. Nothing else. No third-party service, no cron job, no theme changes. Invision Community offers a profile photo gallery on its Cloud Team, Business and Enterprise plans. This brings the same idea to a self-hosted community.

IPS5.0.0+

Sunday at 09:07 PM5 days

Profile Photo Gallery
Give your members a set of profile photos to choose from, instead of leaving every avatar to whatever they happen to upload.
You supply the photos. Members pick one from their account settings, and it becomes their profile photo everywhere on the community — topics, profiles, the member list, hovercards, notifications.
Why communities want this
Younger or moderated communities where letting members upload arbitrary images is a moderation problem you would rather not have. Themed communities — a game, a show, a team — where a set of house avatars is part of the character of the place. Anyone tired of the letter avatar. Most members never set a photo at all. A row of ready-made ones they can pick with a single click converts far better than an upload form. What it does
Photo sets. Group your photos however you like — "Mascots", "Seasonal", "Staff" — each with its own heading that members see. Restrict a set to member groups. Staff-only avatars, supporter-only avatars, a set that only appears for a promoted group. Secondary groups count, so a member given a staff group as a secondary sees the staff photos. Members choose from their account settings, in a tab alongside Email Address and Password, where they already go to change things about their account. One click to change, one click to remove. The photo they are wearing is marked, so it is obvious what they have. See what is actually being used. Every photo in the AdminCP shows how many members are wearing it, and deleting one that is in use warns you first. Upload in bulk. Select a folder's worth of images at once; they are resized on the way in. How it stores them
One copy of each photo, shared by everyone who chose it — not a duplicate per member. A community of five thousand members wearing twenty avatars stores twenty images.
It uses the same mechanism Invision Community's own Gallery application uses for this, so photos work everywhere a profile photo appears, with no theme edits and no template hooks. They can also be moved to S3 or any other storage you have configured, from the AdminCP screen you already use for that.
What it does not do
It does not remove or replace your members' ability to upload their own photo. That stays exactly as your group settings have it — the gallery is an additional way to get one, not a restriction. If you want uploads switched off, that is a group setting in Invision Community itself. It does not import photos from anywhere. You upload the images you want offered. Requirements
Invision Community 5. Nothing else. No third-party service, no cron job, no theme changes. Invision Community offers a profile photo gallery on its Cloud Team, Business and Enterprise plans. This brings the same idea to a self-hosted community.

25.00 USD
10.00 USD / 6 months

25.00 USD
10.00 USD / 6 months

Chat Calls

Chat Calls

Chat Calls
Voice and video calling for Chat. A call button appears in every one-to-one chat window; press it and the other person's browser rings.
The audio and video go directly between the two browsers. They do not pass through your server, they are not recorded, and there is no per-minute charge from anybody.
What it does
Voice calls from any private conversation. Video calls, if you allow them — your own camera in the corner, theirs filling the panel. Ring, answer, decline, with the caller told which of those happened rather than left listening. Busy handling — someone already on a call is not interrupted, and the caller is told why. No answer times out instead of ringing forever. Per-group permission. Off for every group until you turn it on. Works on a phone. It bolts on — it does not modify Chat
This installs as its own application and attaches through the extension points Chat publishes. Install it and the call buttons appear. Remove it and they disappear, with no trace of a missing feature and nothing edited in Chat itself.
It also needs no change to your Realtime gateway. Two people in a conversation are already connected to it, so the call sets itself up over the connection they have.
Requirements
Invision Community 5 Chat — this is an add-on to it and does nothing on its own Realtime, which Chat already requires HTTPS. Browsers refuse microphone and camera access on an insecure page. This is not negotiable and not something an application can work around. A TURN server — see below You will want a TURN server, and here is the honest reason why.
Roughly a third of real connections cannot go directly between two browsers, because of how home and office networks are configured. Those calls need a relay, and that relay is TURN.
Without one, calling will look like it works. You will test it, it will connect, and you will ship it — because the two people testing are almost always on the same network, which is the case that always works. It will then fail for a meaningful share of your members, and the reports you get will say "it just doesn't connect" with nothing to go on.
The download includes a ready-made coturn setup — a compose file and a configuration file with the three values you need to change marked. It takes about ten minutes. The AdminCP tells you plainly whether one is configured.
One to one, for now
This version does two people. Group calling needs an entirely different piece of server software routing everybody's video to everybody else, with real processing and bandwidth cost on your machine. That is planned as a later version rather than promised here — a call quality problem you cannot fix is worse than a feature you do not have yet.
Privacy
Media is peer to peer and encrypted by the browser. Your server sees only the handful of small messages that set the call up, and stores none of them. Nothing is recorded anywhere, by design — there is no recording feature to switch off.
TURN credentials are generated for one member and expire on their own, so a browser never holds a lasting key to your relay.

IPS5.0.0+

Sunday at 08:57 PM5 days

Chat Calls
Voice and video calling for Chat. A call button appears in every one-to-one chat window; press it and the other person's browser rings.
The audio and video go directly between the two browsers. They do not pass through your server, they are not recorded, and there is no per-minute charge from anybody.
What it does
Voice calls from any private conversation. Video calls, if you allow them — your own camera in the corner, theirs filling the panel. Ring, answer, decline, with the caller told which of those happened rather than left listening. Busy handling — someone already on a call is not interrupted, and the caller is told why. No answer times out instead of ringing forever. Per-group permission. Off for every group until you turn it on. Works on a phone. It bolts on — it does not modify Chat
This installs as its own application and attaches through the extension points Chat publishes. Install it and the call buttons appear. Remove it and they disappear, with no trace of a missing feature and nothing edited in Chat itself.
It also needs no change to your Realtime gateway. Two people in a conversation are already connected to it, so the call sets itself up over the connection they have.
Requirements
Invision Community 5 Chat — this is an add-on to it and does nothing on its own Realtime, which Chat already requires HTTPS. Browsers refuse microphone and camera access on an insecure page. This is not negotiable and not something an application can work around. A TURN server — see below You will want a TURN server, and here is the honest reason why.
Roughly a third of real connections cannot go directly between two browsers, because of how home and office networks are configured. Those calls need a relay, and that relay is TURN.
Without one, calling will look like it works. You will test it, it will connect, and you will ship it — because the two people testing are almost always on the same network, which is the case that always works. It will then fail for a meaningful share of your members, and the reports you get will say "it just doesn't connect" with nothing to go on.
The download includes a ready-made coturn setup — a compose file and a configuration file with the three values you need to change marked. It takes about ten minutes. The AdminCP tells you plainly whether one is configured.
One to one, for now
This version does two people. Group calling needs an entirely different piece of server software routing everybody's video to everybody else, with real processing and bandwidth cost on your machine. That is planned as a later version rather than promised here — a call quality problem you cannot fix is worse than a feature you do not have yet.
Privacy
Media is peer to peer and encrypted by the browser. Your server sees only the handful of small messages that set the call up, and stores none of them. Nothing is recorded anywhere, by design — there is no recording feature to switch off.
TURN credentials are generated for one member and expire on their own, so a browser never holds a lasting key to your relay.

65.00 USD
25.00 USD / 6 months

65.00 USD
25.00 USD / 6 months

Chat

Chat

Chat
A chat launcher on every page of your community. Members message each other privately, join public rooms, or start invite-only rooms of their own — without leaving the page they were reading.
It runs on your own server, over your own WebSocket. There is no third-party chat service in the loop, no per-message pricing, and no monthly bill that grows with your community.
What members get
A launcher that is always there. Bottom corner of every page, with an unread count. Open it and their conversations and rooms are right there. Private messages. One to one, with history. Start one from the list of who is online. Public rooms. You create these in the AdminCP and choose which groups may enter. Private rooms. Invite-only, owned by whoever made them. Give a group permission to create their own, or keep it to staff. Typing indicators, so a conversation has a rhythm rather than a series of surprises. Images and files. Pictures appear inline; documents arrive as a labelled link. It works on a phone. The floating window becomes a full-screen panel rather than a postage stamp. What you get
Per-group permissions. Who can use chat at all, and who can create rooms. Off for every group until you say otherwise. Moderation. A "Can moderate chat" permission that reaches every room, including private ones. Delete anything, mute anyone. Room owners manage their own. Invite, remove and mute inside a room they created — and nothing outside it. Attachments live where your files live. S3, R2, Backblaze, FTP, or local disk. Whatever you have already configured. Core's ignore list is honoured, in both directions. Members browsing anonymously are never listed. They asked not to be seen. Private by construction
Every channel a browser is allowed to listen on is decided by your server and cryptographically signed. The WebSocket gateway verifies that signature and knows nothing about rooms or permissions — so there is only ever one copy of the rules.
That applies to public rooms as much as private ones. It would be simpler to let the gateway wave through anything that looks like a room, but the same shortcut would wave through a private room to anybody who guessed a number. It does not.
Requirements
Invision Community 5 Realtime, installed and connected, with its gateway deployed Audio and video
Voice and video calling is a separate add-on, sold on its own or bundled with this. Chat ships the extension points it needs, so installing the add-on makes a call button appear — and not installing it leaves no trace of a missing feature.

IPS5.0.0+

Sunday at 08:47 PM5 days

Chat
A chat launcher on every page of your community. Members message each other privately, join public rooms, or start invite-only rooms of their own — without leaving the page they were reading.
It runs on your own server, over your own WebSocket. There is no third-party chat service in the loop, no per-message pricing, and no monthly bill that grows with your community.
What members get
A launcher that is always there. Bottom corner of every page, with an unread count. Open it and their conversations and rooms are right there. Private messages. One to one, with history. Start one from the list of who is online. Public rooms. You create these in the AdminCP and choose which groups may enter. Private rooms. Invite-only, owned by whoever made them. Give a group permission to create their own, or keep it to staff. Typing indicators, so a conversation has a rhythm rather than a series of surprises. Images and files. Pictures appear inline; documents arrive as a labelled link. It works on a phone. The floating window becomes a full-screen panel rather than a postage stamp. What you get
Per-group permissions. Who can use chat at all, and who can create rooms. Off for every group until you say otherwise. Moderation. A "Can moderate chat" permission that reaches every room, including private ones. Delete anything, mute anyone. Room owners manage their own. Invite, remove and mute inside a room they created — and nothing outside it. Attachments live where your files live. S3, R2, Backblaze, FTP, or local disk. Whatever you have already configured. Core's ignore list is honoured, in both directions. Members browsing anonymously are never listed. They asked not to be seen. Private by construction
Every channel a browser is allowed to listen on is decided by your server and cryptographically signed. The WebSocket gateway verifies that signature and knows nothing about rooms or permissions — so there is only ever one copy of the rules.
That applies to public rooms as much as private ones. It would be simpler to let the gateway wave through anything that looks like a room, but the same shortcut would wave through a private room to anybody who guessed a number. It does not.
Requirements
Invision Community 5 Realtime, installed and connected, with its gateway deployed Audio and video
Voice and video calling is a separate add-on, sold on its own or bundled with this. Chat ships the extension points it needs, so installing the add-on makes a call button appear — and not installing it leaves no trace of a missing feature.

95.00 USD
35.00 USD / 6 months

95.00 USD
35.00 USD / 6 months

Live Notifications

Live Notifications

Live Notifications
Invision Community only checks for notifications when a member opens the notification menu. Anything that happens while they are reading a page — a reply to their topic, a mention, a quote — sits there unseen until they navigate or reload.
Live Notifications shows it at the time. A small toast slides in at the corner of the page, the bell count updates to match, and the member carries on reading.
What it does
Notifications appear as they happen. No reload, no navigation, no waiting for the member to go looking. The bell stays honest. The counter in the header is updated from the same figure, so the badge and the menu can never disagree. It reads like a notification, not an advert. A photo, one line of text, and a dismiss button. It fades after a few seconds, and hovering it stops the clock so nobody loses a message they were mid-way through reading. Click to go straight there. The toast is a link to whatever caused it. Optional chime. Off by default. When switched on it is a short two-note tone generated in the browser — nothing to download, and nothing to host. Instant with Realtime, still useful without it
Installed alongside Realtime, notifications arrive over the existing WebSocket the moment they are sent — typically inside a few seconds, with no polling at all.
Without Realtime the application still works. It falls back to a light periodic check on an interval you set, so members see notifications while they read rather than only when they go looking. The AdminCP tells you plainly which of the two is happening, rather than leaving you to guess.
Built to stay out of the way
Nothing is loaded for guests. A signed-out visitor gets no extra script at all. A background tab is never polled. Members with twelve tabs open do not generate twelve times the traffic. Members on a live connection are never polled at all. Reduced-motion preferences are honoured, and the toast is announced politely to screen readers rather than interrupting mid-sentence. Light and dark are both handled. Private by construction
The live message that reaches a browser contains nothing — no title, no author, no link. It says only "look again". The notification itself is then fetched through Invision's own permission-checked endpoint, so a member can never be pushed something they are not allowed to read, even if a channel were somehow joined by the wrong person.
Each member listens on their own channel, and the permission to join it is cryptographically signed by your server for that one member. There is no shared feed to eavesdrop on.
Requirements
Invision Community 5 Optional: Realtime (with its gateway deployed) for instant delivery. Without it, the fallback check is used instead.

IPS5.0.0+

Sunday at 08:38 PM5 days

Live Notifications
Invision Community only checks for notifications when a member opens the notification menu. Anything that happens while they are reading a page — a reply to their topic, a mention, a quote — sits there unseen until they navigate or reload.
Live Notifications shows it at the time. A small toast slides in at the corner of the page, the bell count updates to match, and the member carries on reading.
What it does
Notifications appear as they happen. No reload, no navigation, no waiting for the member to go looking. The bell stays honest. The counter in the header is updated from the same figure, so the badge and the menu can never disagree. It reads like a notification, not an advert. A photo, one line of text, and a dismiss button. It fades after a few seconds, and hovering it stops the clock so nobody loses a message they were mid-way through reading. Click to go straight there. The toast is a link to whatever caused it. Optional chime. Off by default. When switched on it is a short two-note tone generated in the browser — nothing to download, and nothing to host. Instant with Realtime, still useful without it
Installed alongside Realtime, notifications arrive over the existing WebSocket the moment they are sent — typically inside a few seconds, with no polling at all.
Without Realtime the application still works. It falls back to a light periodic check on an interval you set, so members see notifications while they read rather than only when they go looking. The AdminCP tells you plainly which of the two is happening, rather than leaving you to guess.
Built to stay out of the way
Nothing is loaded for guests. A signed-out visitor gets no extra script at all. A background tab is never polled. Members with twelve tabs open do not generate twelve times the traffic. Members on a live connection are never polled at all. Reduced-motion preferences are honoured, and the toast is announced politely to screen readers rather than interrupting mid-sentence. Light and dark are both handled. Private by construction
The live message that reaches a browser contains nothing — no title, no author, no link. It says only "look again". The notification itself is then fetched through Invision's own permission-checked endpoint, so a member can never be pushed something they are not allowed to read, even if a channel were somehow joined by the wrong person.
Each member listens on their own channel, and the permission to join it is cryptographically signed by your server for that one member. There is no shared feed to eavesdrop on.
Requirements
Invision Community 5 Optional: Realtime (with its gateway deployed) for instant delivery. Without it, the fallback check is used instead.

25.00 USD
10.00 USD / 6 months

25.00 USD
10.00 USD / 6 months

Signal

Signal

Signal
Every topic in your forum is in one of a handful of states, and your members can only tell which by opening it. Signal reads the conversation and says so on the list: this one has nobody answering, this one is waiting on the person who asked, this one already has its answer, this one is finished. A reader scanning a forum can see where they can help, and where they will find what they came for.
It answers a different question to "when was the last reply?"
Labels driven by the clock — new, active, quiet, dormant — tell you the same thing the last reply column already tells you, in different words. Signal's states come from the conversation itself: whether anyone replied, who spoke last, whether an answer was accepted, and whether one reply is clearly the best in the topic even though nobody ever pressed the button.
Unanswered — nobody has replied yet. Needs a reply — the person who asked spoke last, so it is waiting on somebody else. Answered — one reply stands well clear of the others, so it probably answers the question. Nobody had to mark it. Solved — an answer was accepted. Settled — answered, and the conversation has finished. Not "dormant": the same fact, and the opposite impression of the community that produced it. Locked — the topic is closed, so it is not waiting on anybody. Busy — replies are still arriving quickly. Waiting on asker — somebody replied and the person who asked has not come back. You choose which of these appear. Fewer is better, and the default leaves out the one that tends to cover most of a forum, because a label on two thirds of the list stops being read at all.
Post scoring — the part Invision only finishes on Cloud
Your self-hosted database already has the columns: post score on every post, and an average on every topic. Nothing in the suite ever fills them in. Signal does.
Scores come from what your community has already done — accepted answers, reactions, and which replies other people quoted — plus a much smaller contribution from the writing itself. That balance is deliberate and it was corrected after testing against a real forum: length is evidence of effort, not of value. A post nobody has reacted to, quoted or marked is held near the baseline however long it is, so a quiet forum does not end up crowning its wordiest automated announcement.
Negative reactions count against a post rather than being ignored, so a reply people actively disagreed with does not score the same as one nobody read.
And it tells you why
Every score comes with its reasoning in plain words — marked as the answer, reactions worth +7, quoted by two later replies, one of the first replies. The settings screen shows the highest-scoring post on your own site and exactly what earned it. An administrator who cannot ask "why is this an 8?" will not trust the number, and a number nobody trusts changes nobody's behaviour.
Answers that nobody marked
On most forums the mark as answer button is barely used, so the knowledge in a long support thread stays invisible. Signal finds the reply that stands clear of its neighbours and puts a small Answer marker on it.
It marks the reply, not the whole discussion. A long support topic often answers several different questions, and declaring the entire thread solved hides that from the next person arriving with the second one.
Standing out is measured against the other replies in that topic, not against a fixed number. That matters: on a quiet forum a fixed threshold labels nothing, and on a busy one it labels everything.
Built to stay out of the way
Badges are rendered from a stored state, and a whole forum index costs one query — not one per row. Scoring runs in the background a batch at a time, and only looks at posts whose evidence has actually changed. It never sweeps the table. The batch size is capped whatever you set it to, because Invision runs background work inside real visitor requests. No third-party services, no outbound requests, no API keys. Everything is computed from your own database. Nothing is overwritten: Signal writes into Invision's own columns, so a community that later moves to Cloud simply has Cloud take over. Requirements
Invision Community 5.0 or later, self-hosted. The Forums application. PHP 8.1+.

IPS5.0.0+

Sunday at 08:30 PM5 days

Signal
Every topic in your forum is in one of a handful of states, and your members can only tell which by opening it. Signal reads the conversation and says so on the list: this one has nobody answering, this one is waiting on the person who asked, this one already has its answer, this one is finished. A reader scanning a forum can see where they can help, and where they will find what they came for.
It answers a different question to "when was the last reply?"
Labels driven by the clock — new, active, quiet, dormant — tell you the same thing the last reply column already tells you, in different words. Signal's states come from the conversation itself: whether anyone replied, who spoke last, whether an answer was accepted, and whether one reply is clearly the best in the topic even though nobody ever pressed the button.
Unanswered — nobody has replied yet. Needs a reply — the person who asked spoke last, so it is waiting on somebody else. Answered — one reply stands well clear of the others, so it probably answers the question. Nobody had to mark it. Solved — an answer was accepted. Settled — answered, and the conversation has finished. Not "dormant": the same fact, and the opposite impression of the community that produced it. Locked — the topic is closed, so it is not waiting on anybody. Busy — replies are still arriving quickly. Waiting on asker — somebody replied and the person who asked has not come back. You choose which of these appear. Fewer is better, and the default leaves out the one that tends to cover most of a forum, because a label on two thirds of the list stops being read at all.
Post scoring — the part Invision only finishes on Cloud
Your self-hosted database already has the columns: post score on every post, and an average on every topic. Nothing in the suite ever fills them in. Signal does.
Scores come from what your community has already done — accepted answers, reactions, and which replies other people quoted — plus a much smaller contribution from the writing itself. That balance is deliberate and it was corrected after testing against a real forum: length is evidence of effort, not of value. A post nobody has reacted to, quoted or marked is held near the baseline however long it is, so a quiet forum does not end up crowning its wordiest automated announcement.
Negative reactions count against a post rather than being ignored, so a reply people actively disagreed with does not score the same as one nobody read.
And it tells you why
Every score comes with its reasoning in plain words — marked as the answer, reactions worth +7, quoted by two later replies, one of the first replies. The settings screen shows the highest-scoring post on your own site and exactly what earned it. An administrator who cannot ask "why is this an 8?" will not trust the number, and a number nobody trusts changes nobody's behaviour.
Answers that nobody marked
On most forums the mark as answer button is barely used, so the knowledge in a long support thread stays invisible. Signal finds the reply that stands clear of its neighbours and puts a small Answer marker on it.
It marks the reply, not the whole discussion. A long support topic often answers several different questions, and declaring the entire thread solved hides that from the next person arriving with the second one.
Standing out is measured against the other replies in that topic, not against a fixed number. That matters: on a quiet forum a fixed threshold labels nothing, and on a busy one it labels everything.
Built to stay out of the way
Badges are rendered from a stored state, and a whole forum index costs one query — not one per row. Scoring runs in the background a batch at a time, and only looks at posts whose evidence has actually changed. It never sweeps the table. The batch size is capped whatever you set it to, because Invision runs background work inside real visitor requests. No third-party services, no outbound requests, no API keys. Everything is computed from your own database. Nothing is overwritten: Signal writes into Invision's own columns, so a community that later moves to Cloud simply has Cloud take over. Requirements
Invision Community 5.0 or later, self-hosted. The Forums application. PHP 8.1+.

45.00 USD
20.00 USD / 6 months

45.00 USD
20.00 USD / 6 months

Disposable Email Blocker

Disposable Email Blocker

Disposable Email Blocker — stop throwaway signups
Ten-minute mailboxes are how a banned member comes back, how one person becomes fifty accounts, and how a spam run gets its foothold. Invision Community has no idea those domains are different from anybody else's.
This knows about eight thousand of them, keeps the list current by itself, and decides what happens the moment such an account is created.
What it does
Recognises throwaway domains. A maintained public blocklist, fetched at install and refreshed daily, so a service that launched last week is caught this week. You choose the response. Hold the account for approval, ban it outright, or record it and do nothing — useful for watching what arrives before you act on it. Your list beats the public one. Add domains it misses, and mark domains it is wrong about as always allowed. A refresh never touches either. Blocking a domain blocks its subdomains. One entry for example.com covers mail.example.com without listing every variation by hand. Shows you what it caught. A panel of counts and the recent catches, so you can tell whether the rule is right rather than trusting that it is. Holding for approval is the default, on purpose
Not everybody using a forwarding address is a spammer. Plenty of careful people sign up to a new forum with a throwaway address precisely because they do not know you yet, and some of them become your best members.
So the default is to hold the account for a human, not to ban it. You get to look. Ban is there when you want it, and there is a third setting that changes nothing at all and simply keeps a record — the honest way to find out what your signups actually look like before you start turning people away.
It acts when the account is created, not at the signup form
Worth being straight about, because it is visible to you: Invision Community 5 provides no way for an application to refuse a registration while the form is being filled in. The account is created, and this acts on it immediately afterwards.
That is not a workaround — it is the better place to stand. It means the check also covers registrations that never touch the form: social and OAuth logins, and anything created through the REST API. A guard bolted onto the signup form would miss all of them, which is exactly where a determined spammer goes next.
Built not to get in the way
A fault never blocks a real signup. If the database is unhappy, the check is skipped rather than failing closed. A spam tool must never be the reason somebody cannot join your community. A bad download cannot empty your blocklist. If the source returns a suspiciously small list, it is treated as a failed fetch and the existing list is kept. Existing members are never touched. It only ever looks at an account as it is created. The log records the domain, never the address. You do not need a file of other people's email addresses to decide whether a rule is working. Requirements
Invision Community 5.0 or newer, self-hosted Outbound access to fetch the blocklist — or add domains by hand and turn the refresh off, which works perfectly well on a closed network Built to be safe
It adds two small tables, hooks no templates, and never edits a core file. Everything it does happens on the member-created event, wrapped so that no fault of its own can surface to the person registering.
Version 1.0.0 · Invision Community 5 · self-hosted

IPS5.0.0+

Sunday at 08:21 PM5 days

Disposable Email Blocker — stop throwaway signups
Ten-minute mailboxes are how a banned member comes back, how one person becomes fifty accounts, and how a spam run gets its foothold. Invision Community has no idea those domains are different from anybody else's.
This knows about eight thousand of them, keeps the list current by itself, and decides what happens the moment such an account is created.
What it does
Recognises throwaway domains. A maintained public blocklist, fetched at install and refreshed daily, so a service that launched last week is caught this week. You choose the response. Hold the account for approval, ban it outright, or record it and do nothing — useful for watching what arrives before you act on it. Your list beats the public one. Add domains it misses, and mark domains it is wrong about as always allowed. A refresh never touches either. Blocking a domain blocks its subdomains. One entry for example.com covers mail.example.com without listing every variation by hand. Shows you what it caught. A panel of counts and the recent catches, so you can tell whether the rule is right rather than trusting that it is. Holding for approval is the default, on purpose
Not everybody using a forwarding address is a spammer. Plenty of careful people sign up to a new forum with a throwaway address precisely because they do not know you yet, and some of them become your best members.
So the default is to hold the account for a human, not to ban it. You get to look. Ban is there when you want it, and there is a third setting that changes nothing at all and simply keeps a record — the honest way to find out what your signups actually look like before you start turning people away.
It acts when the account is created, not at the signup form
Worth being straight about, because it is visible to you: Invision Community 5 provides no way for an application to refuse a registration while the form is being filled in. The account is created, and this acts on it immediately afterwards.
That is not a workaround — it is the better place to stand. It means the check also covers registrations that never touch the form: social and OAuth logins, and anything created through the REST API. A guard bolted onto the signup form would miss all of them, which is exactly where a determined spammer goes next.
Built not to get in the way
A fault never blocks a real signup. If the database is unhappy, the check is skipped rather than failing closed. A spam tool must never be the reason somebody cannot join your community. A bad download cannot empty your blocklist. If the source returns a suspiciously small list, it is treated as a failed fetch and the existing list is kept. Existing members are never touched. It only ever looks at an account as it is created. The log records the domain, never the address. You do not need a file of other people's email addresses to decide whether a rule is working. Requirements
Invision Community 5.0 or newer, self-hosted Outbound access to fetch the blocklist — or add domains by hand and turn the refresh off, which works perfectly well on a closed network Built to be safe
It adds two small tables, hooks no templates, and never edits a core file. Everything it does happens on the member-created event, wrapped so that no fault of its own can surface to the person registering.
Version 1.0.0 · Invision Community 5 · self-hosted

25.00 USD
10.00 USD / 6 months

25.00 USD
10.00 USD / 6 months

• Prev
• 1
• 2
• 3
• 4
• 5
• 6
• Next
• Page 1 of 30

Trends

Popular applications of the day

• Support Tickets

  1

  Support Tickets

  By Cedric

  App of the day
• Log Guests Visits

  2

  Log Guests Visits

  By Nuclear General
• StopForumSpam

  3

  StopForumSpam

  By Kirill Gromov
• Aqualis

  4

  Aqualis

  By Cedric
• Mobile Menu Plus

  5

  Mobile Menu Plus

  By V0RT3X
• Theme Profiles

  6

  Theme Profiles

  By onlyME
• Pages SuperSet

  7

  Pages SuperSet

  By opentype
• On This Day - Community Memories

  8 new

  On This Day - Community Memories

  By Cedric
• Delete Notifications

  9 new

  Delete Notifications

  By Adriano Faria
• (M.A.C.) Multiple Accounts Checker

  10 new

  (M.A.C.) Multiple Accounts Checker

  By Nuclear General

Top Developers

• Adriano Faria
  1

  Adriano Faria

  159 applications
• Cedric
  2

  Cedric

  65 applications
• onlyME
  3

  onlyME

  47 applications
• Nuclear General
  4

  Nuclear General

  39 applications
• Kirill Gromov
  5

  Kirill Gromov

  35 applications
• Split
  6

  Split

  28 applications
• Ernest Defoe
  7

  Ernest Defoe

  44 applications
• A Zayed
  8

  A Zayed

  9 applications
• ClawOfWinterfell
  9

  ClawOfWinterfell

  6 applications
• DawPi
  10

  DawPi

  4 applications
• opentype
  11

  opentype

  3 applications
• V0RT3X
  12

  V0RT3X

  3 applications
• PayMap
  13

  PayMap

  1 application
• Cats
  14

  Cats

  2 applications
• TheJimmo
  15

  TheJimmo

  2 applications

Last reviews

• Database Integrity Check

  

  Database Integrity Check

  I want to verify exactly what it covers. Could you clarify if it handles the following scenarios?
  Database Corruption from Updates: Will this actually repair a database table or index that became corrupted during a previous software update, plugin update or Application update?
  Leftover Plugin/App Data: Will this clean up leftover tables, rows, or orphaned settings left behind by previous system updates, uninstalled applications or plugins?
  Block Editor Sidebar Glitches: Will this resolve a corrupted sidebar layout or "side block" issue that occurred after adding or removing elements in the block editor?
  Thanks for clarifying.
  

  May 20May 20

• Number of Users per Theme

  

  Number of Users per Theme

  This is very cool, as I don't know of any other means of seeing how many people use what. So, I can't guage which themes are popular, but this is a brilliant idea that executes it well.
  

  April 12Apr 12

• Birthday Calendar

  

  Birthday Calendar

  Thank you for creating this; it never should have been removed from IC!!!
  

  April 6Apr 6

• Keyword Tooltips

  

  Keyword Tooltips

  If you are running an IPS community, this Keywords tool is an absolute must-have. We run a highly technical site, and this app has been a lifesaver for our members. We use it to define complex industry terms and acronyms site-wide, and the rich pop-up tooltips make the user experience flawless.
  What really blows me away is the rebuild. It doesn't feel like a clunky third-party add-on; it feels like a native part of the IPS framework. It has its own search integration, reactions, comments, and follow system.
  As an admin, the moderation controls are fantastic. Being able to set up approval workflows for new keywords and comments means we can keep our technical definitions accurate without babysitting the system.
  If you want to enrich your forum's content and keep your users engaged, look no further. Five stars!
  

  March 24Mar 24

• Status Updates

  

  Status Updates

  I have missed this so much, and finding out that it has been recreated and improved was a great discovery.
  Cedric is very active and works to improve this even further.
  5 out of 5 is the max I can give in this review, but it is more like 6 out of 5 or even 7 out of five!
  

  February 14Feb 14

• Ignore Preferences

  

  Ignore Preferences

  Very nice back end options, nicely restrained icon which is also well placed to hide forums or topics. Overall I would have given it five out of five stars except for one small issue ... it seems recognize categories as forums.
  Clicking on ignore does not ignore category or the sub forums associated with that category.
  Actually I would expect/prefer categories not be able to be ignored.
  The hide icon/text should not show since nothing can be actually posted in them ... the opposite would be that all sub forms would also be hidden. But if that was the intent it's not working.
  One new optional feature that could be added is a way to identify specific forums that cannot be hidden by members.
  

  January 23Jan 23

• Editor Styles

  

  Editor Styles

  I asked Cedric 5 hours ago for help with this functionality. Just a few hours later it is available as a free app. Truly amazing!
  

  December 30, 2025Dec 30

• Indent and Outdent Support

  

  Indent and Outdent Support

  Terrific, thank you!
  

  December 7, 2025Dec 7

• Frostee

  

  Frostee

  This is great, thank you!
  

  November 6, 2025Nov 6

• RTHub - Realtime Gateway

  

  RTHub - Realtime Gateway

  Great for reducing server workload and optimising services for live functions.
  Make sure to take the opportunity to claim this free, by purchasing NowReplies, as OnlyME has kindly bundled it in for a short period of time. Saving $10, but it's worth every penny! I am thankful for the kindness to receive this for free.
  

  September 29, 2025Sep 29