Beta testing

Endozia beta testing is live.

We are opening a limited round of beta testing for writers who want to put the real product through its paces and tell us where it holds, where it drifts, and where the experience still needs work.

Limited seats

We are keeping this round small on purpose.

This is an active beta, not a broad open signup. We want a group large enough to pressure the product, but still small enough that feedback is readable and useful.

If you want in, apply here and tell us what machine you are using. Hardware matters for this product, and part of the beta is learning where the experience stays strong and where it starts to strain.

What we need from testers

Useful feedback, not polished praise.

We are looking for people who will actually use Endozia, notice where it slows down or gets confusing, and tell us plainly what happened. That includes install issues, AI behavior, image generation quality, project organization, and machine-specific problems.

Scope of this beta

What this round is meant to test.

The goal here is not just "does it open." We want to know how the actual writing workflow holds up on real machines, with real projects, under real use.

Install and first-run experience

We want to know whether the install is clear, whether setup makes sense, and whether the software feels ready to use once it lands on the machine.

Muse and Ask AI

We are looking closely at answer quality, groundedness, follow-up behavior, and whether the AI feels genuinely useful inside the manuscript workflow.

Image generation

This includes prompt quality, generation time, hardware behavior, and whether portrait and concept work actually feel worth using.

Performance and stability

We want to hear where the app feels smooth, where it feels heavy, and where it feels like it is close to freezing or falling over.

Hardware compatibility

Part of the beta is understanding how Endozia behaves on different CPUs, GPUs, RAM sizes, and storage setups, especially outside the recommended target.

Writer workflow fit

We want direct feedback on whether Endozia helps the manuscript stay legible and usable as the project grows more complicated.

Recommended target

The system we are tuned around.

  • Windows 11
  • 32 GB RAM
  • NVIDIA GPU with 16 GB VRAM
  • Modern desktop CPU
  • 80 GB free disk space (100 GB preferred)

If you are outside that target and still want to test, apply anyway. We just want to know what hardware you are bringing into the beta.

Discord sessions

Beta demo and Q&A are coming.

We will be doing beta tester demo sessions and Q&A on our Discord server. The schedule and announcement are still to come, so this page is the place to raise your hand first.

Once those sessions are ready, we will post the details through the normal Endozia channels and make sure testers know where to show up.

Apply for beta

Tell us what machine you are using.

We do not need a perfect spec sheet. We need a practical picture of the system you would be testing on and what kind of writing use you want to put through the product.

Limited beta space means we may not be able to bring everyone in at once, but this is the place to raise your hand.

Thanks. Your beta application is in, and we will reach out if this round is a fit.
What happens next

This is an application, not an instant download.

We are using this form to understand who is testing, what machines they are using, and where the beta will be most useful right now. If your setup fits the current round, we will follow up with the next step.

We are especially interested in a mix of recommended-spec systems and real-world edge cases, because both tell us something important about the product.