Offer lower pricing/higher efficiency for isolated KB folders

User Story: Efficient & Scalable KB Folders/Projects for Lower Cost and Better Performance

As a TypingMind user with multiple projects,

I want the ability to compartmentalize my Knowledge Base (KB) by folders or projects (with each project/folder having its own isolated vector database),

so that:

Each project’s KB search is only run within its own folder (avoiding global searches over unrelated data),

I can scale storage efficiently and keep compute costs down,

And I only pay for the actual search/compute/storage resources truly required for each project, instead of being billed by a single, global KB character cap.

Why:

In practice, searching many smaller, isolated KB folders is consistently faster, cheaper to compute, and easier to manage than indexing everything into a single giant KB—even if the total character count is the same.

For my use case (and many others), different projects have unrelated data, and there’s no need for global search across all folders.

Currently, even if I have 5 projects and isolate their KB, I’m limited by one global character cap, which makes scaling costs higher than necessary.

My ask:

Please consider allowing pricing/add-ons for additional KB folders or per-folder/project KB limits, rather than only one global total across all folders.

This way, users/teams managing lots of unrelated projects could keep storage and cost efficient—aligned with how vector DBs operate behind the scenes.

Business/Technical Rationale:

More isolated folders = better performance, more manageable cost for both user and provider.

This incentivizes “good data architecture,” helps power users, and keeps TypingMind competitive for those with lots of projects but moderate per-project storage needs.

Thank you for considering!