Tiny Tool Development

// Example Projects / Free companion

IIS LLM Store Bridge

A small companion bridge that routes IIS embedding jobs through LLM Store governance.

Connects IIS embedding jobs with LLM Store routes and governance.

Keep IIS focused on indexing while LLM Store resolves embedding providers, secrets, routes, fallback, and cost.

Ask on Discord Read GitHub documentation Back to catalogue
product slidesCommitted walkthrough media; documentation carries the detailed operating context.

// PRODUCT WALKTHROUGH

Visual orientation backed by the product facts below.

Use the gallery as quick orientation, then inspect mechanics, actions, outputs, integrations, and boundaries.

Overview Embedding jobs through LLM Store governance

Small bridge, clear ownership boundaries.

// THE PAIN

Before the plugin enters the chat.

Embedding jobs should not smuggle API keys into the indexer.

PAIN

IIS needs embeddings to make hybrid search useful — but provider IDs, model strings, and API keys do not belong inside the indexer. Copying LLM Store logic into IIS creates two places to patch when a route changes.

The moment secrets live in both plugins, rotation becomes a coordination exercise instead of a single dashboard action.

What that feels like

  • Embedding configuration tempts teams to duplicate provider logic in IIS.
  • Secrets and model IDs drift between indexer and governance surfaces.
  • Cost and fallback rules split across products that should stay independent.
// WHAT YOU GET

After — in the editor, not in a slide deck.

IIS submits embedding work; LLM Store resolves route, secret, and cost.

GAIN

The bridge registers a thin llmstore executor so IIS keeps catalog and retrieval while every embedding call flows through the same governed routes as the rest of your AI stack.

  • A thin llmstore executor — no bundled provider stack inside IIS.
  • Embedding routes governed like every other LLM Store task.
  • A free companion that keeps both products independently shippable.

// HOW IT WORKS

The product architecture, inspected from the plugin surface.

These are the moving parts I would place on the page so buyers can understand what they are actually getting beyond the slide narrative.

01 / Register

The bridge adds an llmstore executor to IIS.

IIS can discover a thin embedding executor without bundling LLM provider code or duplicating governance logic.

02 / Resolve

LLM Store owns route and provider choice.

Embedding requests are adapted into LLM Store route execution so model IDs, credentials, runtime mode, and fallback stay centralized.

03 / Return

IIS receives embeddings and keeps indexing.

The bridge adapts responses back into IIS embedding job flow while preserving product ownership boundaries.

// FIT

Who actually reaches for this.

Teams using both Internal Index Service and LLM Store in the same Unreal Engine project.

The bridge connects systems without blurring the ownership boundaries of the core plugins.

// SURFACE

Where it lives in Unreal.

Embedding executor registration, request and response adaptation, Blueprint diagnostics, requirements, and runtime flow documentation.

// CAPABILITY MAP

Feature groups with the value of each part made explicit.

Grouped from plugin modules, public APIs, automation hooks, and documented workflow surfaces.

Thin integration

The bridge is intentionally small because both products already have clear jobs.

  • Register an IIS embedding executor named llmstore.
  • Expose registered-state diagnostics.
  • Keep IIS independent from provider SDKs.
  • Keep LLM Store independent from IIS catalog internals.

Governed embeddings

The value is that embeddings follow the same policy as every other AI task.

  • Resolve embedding routes through LLM Store.
  • Use central secret handling instead of indexer-owned keys.
  • Preserve fallback, runtime mode, and provider governance.
  • Let cost reporting include indexing-related AI use.

Operational clarity

Teams can explain exactly why the bridge exists.

  • IIS owns catalog, chunks, vectors, retrieval, and context packs.
  • LLM Store owns provider configuration, secrets, policy, and cost.
  • The bridge owns request/response adaptation only.
  • Both products remain independently shippable.

// OPERATOR TOOLS

Concrete actions, expected result, and mutation boundary.

This is the part that keeps product marketing honest: buyers can see which buttons, APIs, or MCP tools matter and what they change.

// ACTION

Resolve embedding route

Why it matters
Asks LLM Store which provider/model should serve an IIS embedding task.
Operator result
The indexer avoids hardcoded provider decisions.
Change surface
Read/resolve operation in LLM Store config.
// ACTION

Execute embedding route

Why it matters
Submits embedding work through the governed route.
Operator result
IIS receives vectors while LLM Store owns execution policy.
Change surface
Provider call plus IIS job updates.
// ACTION

Simple embedding

Why it matters
Runs a diagnostic embedding request through the bridge.
Operator result
Operators can prove the integration path works.
Change surface
May call configured provider route.
// ACTION

Executor registered state

Why it matters
Reports whether the llmstore executor is available to IIS.
Operator result
Setup issues are visible before jobs fail.
Change surface
Read-only diagnostic.
// ACTION

Executor ids

Why it matters
Lists the bridge executor identifiers IIS can see.
Operator result
Operators can confirm the bridge is the path IIS will use for embeddings.
Change surface
Read-only diagnostic.
// ACTION

Route readiness probe

Why it matters
Checks whether the configured LLM Store embedding route can resolve.
Operator result
A broken provider/route/secret setup is caught before a full index job runs.
Change surface
Read-only or provider-readiness diagnostic depending on route implementation.

// TYPICAL FLOW

From inspection to use without losing the product boundary.

01

Install IIS, LLM Store, and the bridge side by side.

02

Configure LLM Store embedding routes such as iis.embedding.code.

03

Run IIS embedding jobs through the bridge while preserving product boundaries.

// PROOF AND BOUNDARIES

Signals that make the product specific, plus the limits worth saying out loud.

Each card turns implementation facts into buyer-facing proof without pretending the tool solves the wrong problem.

Type Runtime bridge plugin
Executor IIS embedding executor named llmstore
Boundary Request/response adaptation only
Dependency Requires IIS and LLM Store
Ownership IIS keeps indexing; LLM Store keeps provider, secret, cost, and fallback governance
Diagnostics Registered state, executor ids, simple embedding, route resolution

Outputs

What the plugin leaves behind when the workflow is doing useful work.

  • Embedding vectors

    Vectors returned to IIS embedding jobs.

  • Bridge diagnostics

    Registered state and execution feedback.

  • Governed route usage

    LLM Store can include embedding calls in policy and cost surfaces.

  • Executor registration

    A visible proof that IIS can delegate embedding work to LLM Store.

  • Route resolution feedback

    Evidence that the intended embedding route can be found before expensive jobs run.

Inspection basis

The concrete code, API, and tool surfaces used to shape this product page.

  • Bridge functions

    Resolve/execute embedding route, simple embedding, executor ids, and registered-state functions define the bridge surface.

  • Dependency review

    The bridge depends on IIS and LLM Store, and avoids bundling either product's core responsibility.

  • Execution path

    IIS submits embedding work; LLM Store resolves provider/model/secret/cost policy; the bridge adapts the result back.

  • Packaging role

    The plugin is a companion runtime bridge, not a third provider stack.

Integrations

Where the product connects without losing ownership of its own domain.

  • Internal Index Service

    Receives the executor and keeps ownership of indexing.

  • LLM Store

    Resolves and executes provider routes.

  • Unreal Capability Mesh

    Bridge status and jobs can be surfaced through route declarations.

  • Embedding providers

    Any provider supported by LLM Store can serve IIS embeddings through the governed route.

Safety model

The boundaries that make the tool understandable before automation enters.

  • No duplicated secrets

    Provider credentials stay in LLM Store.

  • Product boundary

    The bridge does not become a third AI platform.

  • Diagnostic state

    Registered executor status makes setup errors explainable.

  • Thin failure surface

    If embedding fails, the diagnosis can be split between route resolution, provider readiness, and IIS job state.

Not for

The cases where the product promise would be the wrong expectation.

  • Teams using IIS without LLM Store.

  • Teams that want IIS to own provider configuration directly.

  • Projects that need custom embedding governance outside LLM Store's route model.

// PRODUCT MEDIA

Tutorial and platform embeds stay attached to product context.

YouTube, Discord, LinkedIn, and Fab widgets are reserved for product presentation, explanation, support context, or tutorials. No third-party widget loads automatically.

Tutorial video

YouTube

Product walkthroughs, setup explanations, and tutorial material.

Embed source pending. No third-party widget is loaded here.

Open platform
Primary support context

Discord

Discord-first product support, quick questions, setup discussion, and community context.

Embed source pending. No third-party widget is loaded here.

Open platform
Professional context

LinkedIn

Company background, provider identity, project credibility, and listing context.

Embed source pending. No third-party widget is loaded here.

Open platform
Marketplace context

Fab

Product listing context, license details, purchase route, and marketplace availability.

Embed source pending. No third-party widget is loaded here.

Open platform

// INFORMATION

All essential product signals in one place.

Status Free companion
Category Example Projects
Unreal Engine 5.4; current descriptor/build line UE 5.8
Source state InternalIndexServiceLLMStoreBridge.uplugin VersionName 1.0.2 / Version 3
Primary surface Embedding executor registration, request and response adaptation, Blueprint diagnostics, requirements, and runtime flow documentation.
Marketplace No product checkout linked
Direct sales None on this website
Support route Discord first; product context lives on this page
Listing context Fab for marketplace, LinkedIn for public provider identity
Fact surface 4 functions / 4 settings / 4 failure modes / 1 bridge
Boundary Free companion bridge that registers IIS executor id llmstore and adapts IIS embedding requests to LLM Store routes without moving provider governance into IIS.
Primary workflow Enable IIS, LLM Store, and the bridge, configure an LLM Store embedding route, verify executor id llmstore, then run IIS embedding jobs through bridge diagnostics or normal IIS workflows.
Publication boundary Free companion example project lives under Documentation/bridge-plugins and is parked outside the active Fab publication framework until the Example Projects track is fully integrated.

// NOTES

Practical boundaries.

The bridge is intentionally small and does not replace or bundle either core product.

The published plugin line is tracked across UE 5.4-5.8.

// LEGAL / PRIVACY

Static information page.

Purchases, downloads, marketplace accounts, and platform-specific license details are handled outside this website. Product or tutorial widgets are loaded only after activation, where configured.

Provider details are listed in the legal notice. The current site template does not set first-party cookies and does not load analytics scripts.

Legal Notice Privacy Policy

// RESOURCES

Open the channel that matches the next question.

Fab seller profile

No product-specific Fab listing is linked yet. The public seller profile remains available.

Open

GitHub documentation

Manuals, quickstarts, settings references, troubleshooting, technical notes, and release material live in GitHub.

Open

Discord support (primary)

Start quick questions, setup help, support context, and product-fit discussion on Discord.

Open

Plugin support email

Formal plugin support requests can be sent to the dedicated support mailbox.

Open

LinkedIn company context

Company background, public provider identity, and listing context are available on LinkedIn; support still starts on Discord.

Open

// RELATED

Nearby tools in the catalogue.

Example Projects

Tiny Tool Execution Integration Bridge

Connects Tiny Tool Execution with Unified MCP Server and Unreal Capability Mesh.

View page
Example Projects

SCD IIS Similarity Bridge

Connects SCD similarity requests and health evidence with IIS retrieval contracts.

View page
Example Projects

SCD PRS Bridge

Connects reviewed SCD placement moves with guarded PRS restructure workflows.

View page

// TOOL NAVIGATION

Continue through the catalogue.

Each tool page keeps the product overview here and routes deep technical material to GitHub.

Previous: SCD UII Migration Bridge Next: UII IIS Bridge