Skip to content

Lore across documents. A reference your team can review.

Start with a bounded lore-review task using supported document exports. Inspect extracted facts and possible conflicts against the source. PlotLens does not import native quest graphs, connect to a game engine or validate player-state conditions.

Create a free accountCheck 1,000 words free, no account needed

Limits: 1,000 words and 5 runs a day. This is a short pattern check, not a full continuity check.

Read the security pageContact Sales

Review the lore in your documents.

Entity and document limits depend on your plan; see the pricing page.

Entity graph visualization.

Browse extracted story elements and relationships in an interactive graph. Characters, locations, factions, and items connected by the relationships your writers established.

Bulk import and server-side search.

Import many documents at once. PlotLens processes them in the background and indexes them for search. Document and entity limits depend on your plan.

Programmatic access on Pro and above.

PlotLens exposes a REST API (Pro and above) for integrating with your production tools.

Team access and plan options.

Review the available access controls and support terms against your studio’s requirements.

Role-based access

Team roles are owner, admin, editor and viewer. Membership applies to every project the team owns.

Audit logs

A team activity log that owners and admins can filter by action, user, and date. On Studio and above.

Dedicated support

Dedicated support is part of the Enterprise plan. Contact us for details.

SSO / SAML (Enterprise roadmap)

SSO and SAML are not available today. Not scheduled. Not a contractual commitment until a signed Enterprise agreement says so.

How game studios use PlotLens

Use PlotLens for a bounded review of lore and narrative text in supported document formats. Build a reference, inspect extracted facts and review possible conflicts with your team. It does not import native dialogue trees or quest graphs, connect to a game engine, or validate player-state conditions. Confirm source format, access and review scope before a pilot.

  1. One project per story world

    Organize titles or story worlds in separate projects, each with its own documents, Story Bible, timeline and check sessions. This separates the reference material, not access within a team: members can access every project their team owns.

  2. Upload narrative text in the formats that exist

    PlotLens parses .txt, .md, .markdown, .docx, .pdf, .rtf, .odt, .epub, .fountain and .fdx. There is no importer for engine-native dialogue or quest data, so narrative that lives in a proprietary format has to be exported to one of those first.

  3. Extract the six entity types

    Review the characters, locations, events, items, organizations and concepts extracted from your lore documents. Check source attestations where available and review duplicate candidates before relying on the reference. Extraction does not establish game-state or quest-condition semantics.

  4. Review events and arrange narrative branches

    The timeline lists events extracted from documents and lets you add your own. Set dates or narrative order yourself: document order does not establish story chronology. Branches display parallel or alternate storylines; they do not model executable quest conditions or prove that a player path is valid.

  5. Check what a character is allowed to know

    POV-scoped validation checks text against what a specific character actually knows rather than what is true in the world, and reports knowledge violations where a character acts on something they should not know. Each character holds one of four belief statuses per fact: believes-true, believes-false, unaware or suspects. Available on Plus and above.

  6. Put the narrative team on one team-owned project

    Use a team-owned project with owner, admin, editor and viewer roles. Membership grants access to all projects the team owns. Choose reviewers and canon decision-makers as a team agreement rather than assuming the access role defines approval. Studio covers 5 to 50 seats and Production 10 to 100; these seat ranges are not performance guarantees.

Frequently asked questions

Explore a focused lore-review pilot.

Talk to our team about how PlotLens fits your studio's workflow.