NewsProductMay 22, 20267 min read

XALIVE prepares private beta for the ALIVE creation tool

The first public test flow focuses on signup, source intake, Aura growth, memory review, and objective ALIVE conversation testing.

Official announcement image showing Aura creation, onboarding, memory review, graph preview, and conversation testing.
ProductPrivate beta flow

Private beta focuses on the full authoring loop: signup, Aura birth, source review, memory visibility, and objective conversation testing.

What is opening first

XALIVE is preparing a private beta for the web-based ALIVE creation tool. The first flow is intentionally focused: sign up, create an Aura, add source material, review memory, inspect the visible graph, and test conversation quality.

The goal is to let a user build a self that can carry identity, memory, emotion, desire, and relationship across future services.

The first beta is designed around the full authoring loop. Users should be able to enter, understand what they are making, add a small amount of meaningful material, see how that material becomes reviewed memory, and then test whether the ALIVE can speak from it responsibly.

This is why the early experience begins with Aura. Aura shows that a self is forming before the user has enough source material for a deep conversation. It gives the product a visible center while the rest of the system gathers, reviews, and connects signals.

What testers will help validate

Private beta feedback will focus on whether the product feels understandable, whether memory review gives enough control, and whether Aura growth makes the progress of a self visible.

We will also watch where users lose trust. If source intake feels too opaque, the review flow needs work. If the Aura grows without a clear reason, the level system needs stricter rules. If conversation testing says too much, the runtime needs better boundaries. If it says too little, the self may not be receiving enough reviewed context.

The beta is not only a product test. It is a test of the authoring model. We need to learn whether normal users can shape an ALIVE without reading technical documentation, and whether creators can understand how ALIVE CAST extends the same engine.

  • Account and onboarding clarity.
  • Source intake and review confidence.
  • Aura level progression and interaction feedback.
  • Conversation tests that reveal what the ALIVE knows and does not know.
  • Memory Graph readability for nontechnical users.
  • Privacy controls that feel like ownership, not legal copy.
  • The handoff from ALIVE ME to ALIVE CAST creation.

What will not be opened yet

The private beta will not present every future surface as finished. Mobile widgets, external assistant bridges, full ALIVE CAST publishing, voice cloning, and broad partner APIs all depend on the same core contract becoming reliable first.

The first release is about the self-building loop. If that loop is clear, the later surfaces have a foundation. If that loop is confusing, adding more endpoints and devices will only make the product harder to understand.

How access will be handled

Early access will be limited. The goal is to work with people who can give detailed feedback on creation, source review, privacy, identity, and long-term use. We are especially interested in creators, studios, researchers, and product teams exploring persistent AI identity.

Business, creator, research, and partnership conversations can be sent to business@xrx.studio.

XALIVE prepares private beta for the ALIVE creation tool | XALIVE News · XALIVE