1"use strict";(globalThis.webpackChunklucenia_website_temp=globalThis.webpackChunklucenia_website_temp||[]).push([[6098],{1301(e){e.exports=JSON.parse('{"permalink":"/blog/search-costing-you-millions","editUrl":"https://github.com/lucenia/website/tree/main/blog/2025-07-23-search-costing-millions/index.md","source":"@site/blog/2025-07-23-search-costing-millions/index.md","title":"Why Your AI Infrastructure is Costing You Millions (And What Forward-Thinking Companies Are Doing About It)","description":"A business case for next-generation retrieval technology and why legacy search architecture is holding back your AI initiatives.","date":"2025-07-23T00:00:00.000Z","tags":[{"inline":false,"label":"AI","permalink":"/blog/tags/ai","description":"Artificial intelligence and machine learning"},{"inline":false,"label":"Cost Savings","permalink":"/blog/tags/cost-savings","description":"Cost optimization and savings strategies"},{"inline":false,"label":"Enterprise","permalink":"/blog/tags/enterprise","description":"Enterprise search solutions"},{"inline":false,"label":"Search","permalink":"/blog/tags/search","description":"Search technology and best practices"}],"readingTime":6.44,"hasTruncateMarker":true,"authors":[{"name":"Dr. Nicholas Knize","title":"Co-founder & CEO","page":{"permalink":"/blog/authors/nicholas-knize"},"imageURL":"/img/authors/nicholas-knize.png","key":"nicholas-knize"}],"frontMatter":{"slug":"search-costing-you-millions","title":"Why Your AI Infrastructure is Costing You Millions (And What Forward-Thinking Companies Are Doing About It)","authors":["nicholas-knize"],"tags":["ai","cost-savings","enterprise","search"],"description":"A business case for next-generation retrieval technology and why legacy search architecture is holding back your AI initiatives.","image":"/img/blog/search-costing-millions.png"},"unlisted":false,"prevItem":{"title":"In-Depth Look at Lucenia 0.6.1","permalink":"/blog/in-depth-look-at-lucenia-0-6-1"},"nextItem":{"title":"From Raw Logs to Rich Insights: FluentBit and Lucenia for AI Driven DevOps","permalink":"/blog/fluentbit-lucenia-ai-devops"}}')},28453(e,i,n){n.d(i,{R:()=>a,x:()=>r});var t=n(96540);const o={},s=t.createContext(o);function a(e){const i=t.useContext(s);return t.useMemo(function(){return"function"==typeof e?e(i):{...i,...e}},[i,e])}function r(e){let i;return i=e.disableParentContext?"function"==typeof e.components?e.components(o):e.components||o:a(e.components),t.createElement(s.Provider,{value:i},e.children)}},45245(e,i,n){n.r(i),n.d(i,{assets:()=>l,contentTitle:()=>r,default:()=>g,frontMatter:()=>a,metadata:()=>t,toc:()=>c});var t=n(1301),o=n(74848),s=n(28453);const a={slug:"search-costing-you-millions",title:"Why Your AI Infrastructure is Costing You Millions (And What Forward-Thinking Companies Are Doing About It)",authors:["nicholas-knize"],tags:["ai","cost-savings","enterprise","search"],description:"A business case for next-generation retrieval technology and why legacy search architecture is holding back your AI initiatives.",image:"/img/blog/search-costing-millions.png"},r=void 0,l={authorsImageUrls:[void 0]},c=[];function u(e){const i={em:"em",p:"p",...(0,s.R)(),...e.components};return(0,o.jsxs)(o.Fragment,{children:[(0,o.jsx)(i.p,{children:(0,o.jsx)(i.em,{children:"A business case for next-generation retrieval technology."})}),"\n",(0,o.jsx)(i.p,{children:"If you're a business leader, you've probably realized that infrastru
1cture decisions made years ago are now limiting your ability to capitalize on AI opportunities. You're not alone \u2014 and it's not your team's fault."}),"\n",(0,o.jsx)(i.p,{children:"As the creator of OpenSearch and former early engineer on Elasticsearch, I've watched this industry evolve from the inside. What I've learned is troubling: the fundamental architecture powering most enterprise search today was designed for a different era, and no amount of optimization can fix the underlying economics."})]})}function g(e={}){const{wrapper:i}={...(0,s.R)(),...e.components};return i?(0,o.jsx)(i,{...e,children:(0,o.jsx)(u,{...e})}):u(e)}}}]);
Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.