Separate libraries, less confusion
Keep catalogs and metadata isolated by library. Drive discovery and existing manifests provide a way to reconnect with collections as storage comes and goes.
← The project benchMaker software / TerkTechnologies
ForgeIndex
Make the collection useful again.
A desktop home for maker and model libraries that have outgrown folders alone. ForgeIndex brings file discovery, isolated catalogs, visual enrichment, and review into a workflow you can actually manage.
Per libraryseparate catalog + metadata
Offlinevision enrichment
Reviewbefore promotion
The reason it exists
The file is only useful if you can find it.
Maker collections rarely arrive clean. They grow across drives, downloads, model packs, images, and years of accumulated naming conventions. ForgeIndex is built around making those collections discoverable without pretending that one giant undifferentiated list is enough.
Each library has its own workspace. Visual analysis and optional AI can help describe a collection, but the workflow keeps generated suggestions separate from the decision to accept them. Organization should remain something the operator can understand and direct.
Inside the project
Where the work shows.
Let images contribute
Offline vision can add evidence to a collection. Pending detections can be reviewed and adjusted before they are committed, rather than silently becoming permanent labels.
Keep optional AI optional
A separate manual AI lane supports review and explicit promotion. The public product description makes both global and per-library control part of that workflow.
Inspect the collection’s health
Health and integrity views surface missing material, stale records, broken links, and other issues. Tool discovery and extension-aware launch routing connect discovery with the next making task.
From intention to action
The workflow.
Discover
Locate a drive or collection.
Index
Create an isolated library.
Review
Inspect suggested enrichment.
Use
Find files and open the right tool.
Engineering notes
Local structure, visible decisions
The Windows/.NET application uses SQLite workspaces and an offline vision pipeline. Diagnostic and audit views are intended to make slow operations, library health, and important changes easier to inspect—not just conceal them behind a progress bar.