01
Dialogue logic sprawls fast
Studios end up stitching together prompt routing, entitlement checks, and player-state rules by hand.
The Simpler Way to Connect AICharactersAssistantsto Games
Journale securely connects AI to games with rate limiting, threat detection, entitlement check verification, and complete playerbase behavior observability. Built for retention.
Free forever. No credit card required.
Loading preview
Integrates with
Why teams get stuck
Building AI NPC dialogue is usually a backend project disguised as a gameplay feature.
Tropical Teal is carrying placeholder copy, but the structure is meant to sell the operational pain clearly before moving into the solution.
02
Backend work delays prototypes
Conversation features stall when SDK setup, auth, and observability all need separate infrastructure.
03
Live tuning stays opaque
Teams cannot see which scenes, NPCs, or player cohorts are driving cost and retention outcomes.
04
Security becomes an afterthought
Shipping keys inside the client or skipping signed requests introduces abuse risk before launch.
One stack instead of five
Ship conversation systems with SDK entry points, signed requests, credits, and analytics already connected.
The placeholder story here is simple: Journale gives a game team an opinionated runtime instead of another toolkit they still have to operationalize alone.
Unity / Unreal SDKs
Fast client integration with backend control.
Session security
JWT and signed request workflows for live games.
Credit intelligence
Usage visibility tied directly to account spend.
Player-aware context
Route dialogue using entitlement and player-state signals.
JournaleNpc.csPlaceholder snippet
using JournaleSDK;using UnityEngine;public class TavernKeeper : MonoBehaviour{ [SerializeField] private string npcId = "tavern_keeper"; [SerializeField] private string projectKey = "proj_live_01"; async void Start() { await Journale.InitializeAsync(projectKey); var reply = await Journale.ChatToNpcAsync( npcId, "What rumor is everyone repeating tonight?"); Debug.Log(reply); }}What the product covers
A modular surface area for game teams that need infrastructure, not just prompt helpers.
01
Feature area 1
Unity and Unreal entry points with consistent server orchestration.
02
Feature area 2
API key and player-session flows built for client/server separation.
03
Feature area 3
Usage analytics that expose spend, sessions, and conversation volume.
04
Feature area 4
Credit-based billing model that stays legible for product and finance.
05
Feature area 5
Project-level controls for entitlements, context sizing, and live routing.
06
Feature area 6
Documentation and onboarding paths that support prototype-to-production teams.
Product motion
A dedicated demo surface for cinematic proof, feature explanation, or trailer edits.
Loading Journale showcase
Social proof placeholder
Use the carousel to imply market confidence without turning the page into a wall of quotes.
Indie RPG Studio
“The SDK path got us to a believable NPC prototype quickly, but the real value was everything around auth, keys, and usage visibility.”
Technical Director
Engine compatibility
Keep the integration story grounded in familiar engines, storefronts, and runtime surfaces.
SDK narrative
Tabbed examples keep the integration story concise while still serving both engines.
DialogueController.cs
await Journale.InitializeAsync("project_live_key");var response = await Journale.ChatToNpcAsync( "harbor_master", "What changed after the storm?");uiPanel.SetReply(response);FAQ placeholder
Answer practical objections without forcing visitors to leave the flow.
Placeholder answer: the product is positioned as a backend control plane, with SDKs and server-side flows depending on how much authority your team wants to keep.
Start with the structure now. Refine the messaging when the visual system is locked.
The current implementation makes room for copy iteration later without losing the new hierarchy, motion, and section architecture.