
Fantasy RPG
01Tavern NPCs with moods, trust levels, and dialogue that shifts based on player actions. Insult the bartender and she remembers.
The runtime layer · Beta
Director reads game state, makes narrative decisions, and returns validated parameter updates. Within your rules. Every time. Built to run on-device through its native SDK, which is not yet available; today, developers use the hosted Director beta.

What is Director?
Eposyne Director is a runtime AI Game Master that reads your game state and makes constraint-validated narrative decisions in real time. It drives NPC behavior and dialogue within the limits your game declares; plot progression through story arcs is in development. Director is built to run on-device through its native SDK, which is not yet available. Today, developers use the hosted Director beta for building and testing, and its model calls are paid from usage credits. Eposyne plugins exist for Unity and Unreal, and any other engine can call the HTTP API. It is in beta: the core runtime is what you can build against today, with no licence fee until launch. After launch, it takes 1% of gross revenue above the first 100,000 EUR.
Hosted beta
On-device SDK not yet available
Validated
Checked against your rules
No licence fee
Until launch; beta calls from usage credits
Any engine
Unity, Unreal plugins; HTTP API
01The problem
Players expect worlds that feel alive. Most games still rely on systems that look complex but feel predictable.
Pre-authored branches players exhaust quickly. Same lines, every playthrough.
Quests that play out the same way regardless of what the player actually does.
Characters with no memory. Save their life, they still greet you like a stranger.
02How it works
Six things Director is built to do at runtime
Learn more →01Constraints
Define your game state as parameters with allowed values, ranges, and mutability. Director operates within those boundaries. If the model proposes a change that breaks a rule, Director drops it.
02Decisions
Your engine sends a snapshot of the current scene. Director returns validated updates. JSON or XML in, same format back. One API call.
03Memory
In the beta, your game passes what the player did as part of the state it sends, so Director can read it in later scenes. Help someone, betray someone, ignore someone, and the next conversation starts from there. A dedicated NPC memory module is in development.
04Emergence · In development
The direction Director is built toward: narrative arcs from gameplay, not scripts. Player actions shape what happens next and consequences propagate through the world. The beta covers the reactive part today; a story-arc module for proactive arcs is in development.
05Dialogue
Director can write a line of dialogue for any value your game marks as text, from the context your game sends: what has happened, who is speaking, and what is at stake. Within the limits you declare. No hardcoded branches.
06Generation · In development
In development: Director creating new characters, factions, quests, and rivals at runtime, each one shaped by the current state of your world. Not random. Contextual. This is not available in the beta.
03Control
Director is designed for real production environments. You stay in control. Director handles execution.
Mutable and immutable parameters. Allowed values. Range enforcement. If the model proposes a change that breaks your rules, Director drops it.
You define what Director can change and what it cannot. Personality stays locked. Mood can shift. You set every boundary.
Director proposes; your engine decides. The engine applies only values you declared, marked as changeable, and within range.
Works with your engine
Eposyne for Unreal plugin
Eposyne for Unity plugin04In the field
Director is being built and tested against wildly different game types. Same engine. Different worlds.

Tavern NPCs with moods, trust levels, and dialogue that shifts based on player actions. Insult the bartender and she remembers.

Character relationships, affection systems, and social dynamics that evolve every interaction. Friendships form and break naturally.

Dynamic quests, district-level world state, and NPCs who react to your reputation. Every choice shapes what opportunities appear next.
05The pipeline
Architect and Director are built to work together. One authors the narrative, one runs it.
Builds your narrative systems: quests, dialogue, structure. The authoring layer.
Learn about Architect →Runs them in real time: behavior, adaptation, emergence. The runtime layer.
You are hereDirector is not AI NPCs. It is a narrative runtime. It interprets player behavior and drives the story forward. Every session. Every choice. Every consequence.
Pricing
The hosted beta's model calls are paid from usage credits. Every new account starts with a welcome credit to try it.
After launch, 1% of gross revenue above the first €100,000 per title
Enterprise licensing, a one-time buyout of the revenue share, SLA, and integration work by contact
See how Director transforms static game worlds into living narrative systems.
06Questions
Director is a runtime AI Game Master, currently in beta, that reads your game state and makes constraint-validated narrative decisions in real time. It drives NPC behavior and dialogue within the limits your game declares. Plot progression through story arcs is in development.
Traditional scripting is hand-authored. Every branch must be written and tested in advance. Director takes your world's rules, state, and goals, and generates narrative decisions at runtime that still respect every constraint you define. It handles the branches you didn't write.
Today, yes. Developers use the hosted Director beta, which is reached over the network for every decision; it is for building and testing, and a shipped game cannot use it yet. Director is built to run on-device through its native SDK, which is not yet available. The native SDK is what brings no cloud dependency, no network calls, and no player data leaving the game. Today each hosted call is paid from usage credits; on-device inference through the native SDK runs on the player's hardware.
Director has no licence fee while you build. The hosted beta's model calls are paid from usage credits, and every new account starts with a welcome credit to try it. After your game launches commercially, Director takes 1% of gross revenue above the first 100,000 EUR per title, so small releases pay no licence fee. Enterprise licensing, a one-time buyout of the revenue share, SLA, and integration work are available on request. See pricing for the details.
Director has plugins for Unity and Unreal Engine: Eposyne for Unity and Eposyne for Unreal. Any other engine can call Director's HTTP API directly. It works as middleware that reads game state and returns validated narrative parameter updates.
Not outside the limits you set. In your engine, you declare which values Director may change and within which allowed values or ranges. Any proposed change outside those limits is dropped before it reaches your game, and your engine applies only declared, changeable, in-range values. You define the boundaries; Director operates inside them.
No. Director does not read Architect worlds today; it works with the state your game sends and the limits your game declares. Architect content reaches your game through the Eposyne plugin's import.