Immersive onboarding and workforce training with interactive environments, AI-powered characters, spoken conversations, and measurable scenarios — streamed directly to the browser.
Built with you as a scoped pilot — one controlled, measurable simulation, not a self-service world generator.
A learner can pass a quiz on a procedure they have never performed. The score measures recall of the slide, not readiness for the shift.
The learner has to do the thing: find the equipment, ask the supervisor the right question, make the call, live with the consequence. Assessment reads actions and conversation, not multiple choice.
Workplaces and operational scenarios built in Unreal Engine — the bay, the ward, the shop floor, modelled to the detail the scenario needs.
Supervisors, coworkers, customers, patients or trainees who take part in the scenario. Each one works inside a defined role, approved knowledge, and explicit limits on what it may say or do.
Learners speak to characters instead of picking from a list of dialogue buttons. Speech in, spoken answer back, in the browser.
Tasks, checkpoints, permitted actions, failure conditions and branching outcomes — authored up front and enforced by the server, not improvised by a model.
Decisions, communication, task completion, safety violations, hints used and time to completion, scored against a rubric you approve.
The experience runs through Pixel Streaming: a link opens the session. No install, no download, no gaming machine on the learner's desk.
Character answers can be grounded in your approved policies, SOPs, training material and scenario notes, so a question about your process gets your answer.
The voices, emotional direction, captions, facial-animation tracks and Unreal integration already running in Renea Studio are the delivery layer behind every character.
Characters run on Renea's voice and language stack by default. If you have your own contract, tenancy or fine-tuned model, a project can be pointed at it instead — we'll tell you which measurements that changes.
Characters work inside a role, a scope of approved knowledge, the scenario's goals, safety rules and explicit limits on what they may do. They are cast members with a brief, not autonomous employees.
A new warehouse employee enters the virtual facility, meets an AI supervisor, locates safety equipment, responds to a damaged-pallet situation, asks procedural questions, and receives a competency report.
Set the role, the workplace, the learning objectives, the rules of the world and the criteria you will be judged against.
SOPs, policies, scripts, FAQs and training material. Characters answer from this, and a human signs off what is in scope.
Choose the 3D environment, the character roles, their voices and personalities, and the behaviour each one is allowed.
An isolated Pixel Streaming session starts from a secure link — one session per learner, torn down when it ends.
Completion, decisions, conversation results, violations, hints and evaluator feedback, per learner and per objective.
The first version of a simulation is built with you, not generated for you. One scenario, done properly, that you can put a real learner in front of and measure.
Discuss a pilot →Simulations are visible only to members of your organisation.
Your organisation is the boundary: scenario content, transcripts and results are isolated per customer, and Renea staff have no implicit access to them.
Run characters on Renea's stack, or point a project at your own model and voice contract.
Characters answer from material a named person has signed off.
Set how long transcripts and session recordings are kept.
Who launched what, when, and what the system recorded.
Learner, trainer, administrator and owner roles within your organisation.
Every scenario and knowledge set is reviewed before a learner sees it.
Application and database run in the EU today — Nuremberg and Frankfurt.
No. The simulation runs on our GPU servers and is streamed to the browser through Pixel Streaming. The learner opens a link and gives the browser permission to use the microphone. A normal laptop is enough.
No, and this is deliberate. Each character has a defined role, a scope of approved knowledge, allowed and prohibited actions, and escalation rules. They are not free-roaming agents, they cannot take actions the scenario has not granted, and they do not decide whether a learner passed.
No. Characters run on Renea's voice, direction and language stack by default, and that is where the assessment guarantees come from — transcripts, allowed-action enforcement and conversation scoring all happen on our side of the call. If you would rather use your own provider, contract or fine-tuned model, a project can be configured to call it directly. We will be specific about which measurements that weakens before you choose it.
Yes — SOPs, policies, scripts and training material can ground what characters say, so answers match your process rather than a generic one. What goes in scope is reviewed and approved before a learner ever sees it.
We build an environment that is faithful to the parts the scenario depends on: the equipment, the layout, the signage, the stations a learner has to find. We do not generate a whole facility automatically from a floor plan, and we will tell you up front what is worth modelling and what is not.
Objective completion, the decisions taken and their order, what the learner said and how, safety violations, hints requested, branches chosen, and time to completion — each tied back to evidence from the session so a score can be explained rather than just asserted.
No. Renea Simulations is an experiential layer that sits beside your LMS: the LMS keeps the catalogue, the records and the compliance reporting, while the simulation is where the learner actually demonstrates the skill.
Results are designed to be exportable so completion and scores can be pushed into an existing system. Standards-based integration is scoped per pilot rather than promised as a switch you flip.
One scenario, one environment, one to three character roles, voice interaction, objectives and branching, performance reporting and secure browser access — plus the review cycles to get the scenario right with your team.
The best first simulation is the one where a mistake is expensive and a slide deck has already failed to fix it.