Support
It is your data. You decide who gets it.

CommunityGuard is a protection layer for your Khoros Aurora AI Community. It works at the edge, before traffic reaches your community, to tell real people apart from automated visitors, and it puts you in control of what happens to each kind of automated traffic.

TECHNICAL OVERVIEW
additional protection layer

CommunityGuard

CommunityGuard identifies AI crawlers, scrapers, and human-mimicking bots at the edge and lets you decide, per service, who reaches your community, so traffic stays fast, analytics reflect real people, and usage is not inflated by bots.

Automated traffic is not a future worry. It is hitting community platforms right now, and most teams cannot even see it. Left alone, it:

  • Distorts your analytics. The numbers you report stop matching the people who actually showed up.
  • Consumes capacity you pay for. Bandwidth and compute spent on traffic that will never post, read or buy.
  • Pressures the experience. Spikes and scraping slow things down for the members who matter.

A traditional firewall asks “does this match a known attack?” CommunityGuard asks “is this visitor actually human?”

additional protection layer

The problem CommunityGuard solves

A new class of automated traffic now behaves like a real person: it uses real-looking browsers, rotates through residential networks, and mimics human behavior. Traditional web firewalls were built to match known attack signatures, so this traffic slips past them. Left unchecked, it inflates your analytics, inflates your billable usage, and drives aggressive spikes in load.

The four kinds of visitors:

Named AI services are identifiable and can be managed per service. Anonymous scrapers hide and are blocked.

 

VisitorWho they areWhy it matters
Real UsersPeople in real browsers, the audience your community exists forThey should always get fast, normal access
Declared BotsAutomated visitors that identify themselves and can be verified, such as search enginesUseful and welcome: they keep their access, and search engines stay allowed so SEO is safe
Named AI servicesIdentifiable AI crawlers and assistants, such as AI search and AI training crawlers, recognized by nameBecause they are identifiable, you set a policy for each one, rate-limited by default. This is where the control comes in.
Anonymous scrapersUnnamed automation that hides behind proxies and imitates real users.They cannot be identified or trusted, so they are blocked. This is the core threat.
The four visitor types map onto these three outcomes: real users and declared bots are allowed, named AI services are handled by your policy and rate-limited by default, anonymous scrapers are blocked.
THREE OUTCOMES
OUTCOME 01

Allow

Normal access. The visitor reaches your community.
OUTCOME 02

Rate limit

Access at a controlled pace, so a visitor can still get content without overwhelming your community.

OUTCOME 03

Block

Stopped at the edge. The visitor never reaches your community.

additional protection layer

What CommunityGuard does

CommunityGuard sits in front of your community and screens automated traffic before it ever arrives.

  • Detects and manages bots at the edge. Unwanted scrapers and agents are stopped before they reach you.
  • Protects the people, preserves the channels you want. Real members get through, and so do the search engines and AI assistants you want surfacing your community. You choose who helps and who gets blocked.
  • Adapts as the traffic does. The bots do not stand still. Neither do we.

 

You decide what gets through. CommunityGuard enforces it.

Availability: CommunityGuard is enabled now for Khoros Aurora AI communities, free for the first 60 days. Talk to your Khoros team to see it working on your own data.

Keep CommunityGuard's additional layer of protection and control beyond the trial.

Contact us today.