Who the pilot is for
AlexAI works best in adult Discord communities that already have active moderators, a clear
sense of server culture, and a reason to use a memory-rich bot beyond novelty. Gaming clans,
creative servers, roleplay groups, private leagues, and long-running friend communities are
the strongest candidates.
Strong fit
- Adult community with owner or admin buy-in.
- Members understand that AlexAI may remember context.
- There is a clear use case: events, creative media, lore, moderation support, or
voice presence.
Not a fit yet
- Servers aimed at children or teen safety-sensitive audiences.
- Communities that need direct billing, instant install, or enterprise SLAs.
- Spaces where members cannot be told when memory or voice features are active.
What a managed pilot includes
Discord integration
Configured bot access, command surfaces, and channel boundaries
matched to your server structure.
Memory setup
Shared expectations for what AlexAI can remember, how to request
correction, and what should stay out of memory.
Voice planning
Consent-aware voice-channel rules before any transcription, response,
or voice-memory feature is enabled.
Operator review
Direct review of safety, moderation, generated media, dashboard
access, and public telemetry needs.
Setup checklist
Before a pilot starts, the community owner or authorized admin should be ready to provide:
- Server purpose, approximate member count, and expected active channels.
- Which channels AlexAI may read, answer in, or ignore.
- Whether voice features are allowed, and which voice rooms are excluded.
- Any topics, names, channels, or moderation areas that should never become public
content.
- The people allowed to make memory, safety, dashboard, and configuration decisions.
Boundaries that are decided up front
AlexAI is intentionally not installed as a silent observer. The pilot should make these
choices visible to the server before launch.
Memory
What gets remembered, what gets excluded, who can ask for deletion, and how long
pilot records are retained.
Voice
When AlexAI may join voice, whether voice memory is enabled, and how members know a
bot is present.
Public surfaces
Whether logs, generated media, blog-like content, or telemetry can be made public,
and what is redacted first.
Admin access
Who can view dashboard surfaces, adjust bot behavior, inspect memory, or request
operational changes.
Expected timeline
Pilots are currently manual and selective. The goal is to learn from real communities without
rushing a tenancy model that affects memory, privacy, voice, and server identity.
1. Intake
Submit the request with the community context and boundaries that
matter.
2. Fit review
We review use case, moderation maturity, privacy posture, and technical
readiness.
3. Configuration
If selected, we configure access, channels, memory behavior, and
public-facing notices.
4. Pilot review
We evaluate usefulness, friction, safety events, and what must change
before broader rollout.
Request a pilot
The fastest path is the managed instance intake on the homepage. Include community size,
your role, likely use cases, and any safety, privacy, voice, moderation, or budget
boundaries.
A request is not approval, and pilot details may be handled under a
separate written agreement when needed.