INDEPENDENT PRODUCT STUDIO

AI tools.
Real worlds.

We build the systems that turn ideas into working software. AI agent workflows, Unreal Engine tooling, and multiplayer experiences—developed together, tested in practice.

ENGINEERING × INTERACTIVE EXPERIENCES

VR11 / CONNECTED SYSTEMSINTENT → TOOLS → EXPERIENCE BRIEF ENGINE TOOLS VERIFY
VR11 / STUDIOTOOLS FOR THE NEXT THING YOU BUILD↓
BUILT WITHUnreal EngineMCPRustPythonWeb technologies

01 / SELECTED WORK

One studio.
A connected toolkit.

Our work starts with a practical question: how can a small team turn ambitious ideas into software it can actually run, inspect, and improve?

01
ENGINE TOOLINGActive development

Monolith workflows

Give AI a way
to work in Unreal.

We develop and extend MCP-based workflows that connect AI agents to Unreal Engine. Blueprint, material, and scene operations become discoverable tools with explicit inputs and inspectable results.

  • Unreal Engine
  • MCP
  • Editor workflows
Discuss an engine workflow
02
AGENT OPERATIONSActive development

AgentDesk & AnchorMind

Keep the work
moving forward.

Our agent operations work brings task coordination, execution records, and reusable project context together. We extend agent tooling so developers can manage work across providers and review what changed.

  • Orchestration
  • Project context
  • Developer control
Discuss agent tooling
03
INTERACTIVE EXPERIENCESPrototype / web demo

Speed & Giant

Build it. Play it.
Learn from it.

Speed explores multiplayer flows in Unreal Engine. Our Giant web demo explores dedicated-server multiplayer, shared rooms, and reconnect behavior. Playable projects give our engineering work a real testing ground.

  • Multiplayer
  • Unreal Engine
  • Dedicated servers
Open the Giant web demo (opens in a new tab)

ALSO IN THE LAB

Dataset StudioResearch / prototype

Workflows for curating domain knowledge and evaluating training candidates.

Scenario LabResearch / prototype

Explainable property valuation and scenario analysis, developed with synthetic demo data.

02 / HOW WE BUILD

AI is part of the
work, from day one.

We use AI coding tools in our development process and are developing workflows for model-driven tool use. The goal is useful execution: changes a developer can inspect and results a team can reproduce.

  1. 01

    Understand

    Start with the task, the project context, and the constraints that matter.

  2. 02

    Execute

    Connect the work to real tools, clear interfaces, and a defined scope.

  3. 03

    Verify

    Check the resulting behavior and preserve the evidence needed to review it.

A connected development workflow

A creative brief becomes editor actions: inspect the project, change an asset, and check the result.

WORKFLOW CONCEPT · NOT A LIVE PRODUCT SESSION

03 / THE STUDIO

Small-team ambition.
Hands-on engineering.

VR11 is an independent product studio working at the intersection of developer tools and interactive software. We develop integrations, extend open software, and build prototypes that put our ideas to work.

For game developers, technical creators, and teams exploring practical AI workflows.

  • Real tools, real feedback
  • Clear product stages
  • Respect for data and ownership
What is available today?

The Giant web demo is publicly accessible. Our engine tooling, agent workflows, and research projects are under active development. Contact us to discuss a specific workflow or preview.

How do you use Claude?

Claude Code is part of the developer tooling supported by our agent operations work. We are developing and evaluating Claude-compatible MCP workflows for tool use, project context, and verification. Our next step is to evaluate production API integrations against concrete development tasks.

Who should get in touch?

Game developers and small product teams with an engine workflow, agent integration, or interactive prototype to explore. We are open to conversations about scoped pilot projects and collaboration.

LET’S BUILD SOMETHING USEFUL

Your next idea
deserves real tools.

Tell us what you are trying to build, where the workflow gets stuck, and what a useful first result would look like.

Email the studio
fasfin@vr11.net