PUBLIC ROADMAP

Build trust first. Scale second.

The roadmap is organized around what has to be true before AlexAI can safely leave the origin server as a separate Alex build for more communities.

Updated April 2026

Now: origin server hardening

AlexAI is live in eR33t Gaming and the priority is making the current system easier to understand, operate, and explain from the public website.

Public site

Clearer homepage, command reference, architecture view, public docs, and safer onboarding language.

Admin visibility

Better status, memory health, activity, relationship, episode, and system dashboard pages for admins.

Memory quality

Improving storage, retrieval, importance scoring, correction paths, and cleanup for long-term context.

Safety docs

Making memory, voice, data, and moderation expectations readable before anyone asks for a pilot.

Next: selected pilots

Separate server builds Separate server rules, memory scope, dashboard access, usage limits, and public output controls for each pilot.
Owner controls Practical controls for channels, voice rooms, generated media, public logs, deletion requests, admin roles, and budget boundaries.
Pilot agreements Clear written expectations for setup, support, costs, safety duties, data handling, and what happens at the end of a pilot.
Launch checklist Reusable onboarding notices that server owners can share with their communities before AlexAI is active.

Later: repeatable rollout

After a few selected pilots prove the model, the project can move toward more repeatable provisioning. The likely shape includes:

  • Assisted onboarding paths for approved adult communities.
  • Pricing that combines managed setup, monthly operation, model usage, media generation, storage, and admin support.
  • Preset personas and configuration profiles for common server types.
  • Better admin tools for memory export, deletion, auditing, and retention windows.
  • More polished public pages for generated media, release notes, and server-specific notices.

Not promised yet

These ideas may happen, but they should not be treated as guaranteed product commitments.

Instant public install

Not ready until tenancy, privacy, permissions, and support flows are reliable, documented, and repeatable.

Enterprise support

Formal SLAs, procurement paperwork, and dedicated support channels require a separate commercial posture.

Child-directed communities

AlexAI is not aimed at children and should not be deployed into child-directed communities.

Perfect moderation

AlexAI can support server culture, but it does not replace human moderators or server owner responsibility.

Feedback shapes the order

Use the pilot intake or Contact page to share what would make AlexAI safer, clearer, or more useful in your server. Specific constraints are more valuable than generic enthusiasm.