Artificial agents often show good results during pilot testing because the scope of application is narrow, data is controlled, and requests are predictable. However, the production environment is different, and this gap leads to the halt of many projects.
Gartner predicts that by the end of 2027, over 40% of AI agent projects will be canceled due to rising costs, uncertain business value, or insufficient risk control. According to Nitin Vagulde, Regional Director for Asia-Pacific at VeloDB, a significant part of the problem lies not in the model itself, but in the data level.
In his presentation titled 'AI Agents at Scale: Surviving After Demonstration,' Nitin detailed how AI agents use data differently from humans, what they need to operate reliably at large volumes, and how companies are restructuring their data infrastructure to support these systems.
Nitin started with an example: in a traditional system, a manager could get last year's sales data by running a ready-made report. The situation changes drastically when you ask an AI agent to explain the drop in sales over the last three quarters. The agent must extract order records from ERP and CRM systems, analyze support tickets and chats for major client issues, and study sales department reports on territory dynamics. If its reasoning is incomplete, it asks for more information.
He noted: 'What used to be completed with one simple search or one simple query now requires hundreds of search operations to obtain the same information.' Previously, the main consumers of business data were people and reports, and systems were built around fixed reports with clear boundaries.
Now, according to Nitin, AI has become a new customer of this data, and it behaves completely differently. Agents work around the clock, ask numerous questions simultaneously, and function in an iterative cycle: asking, thinking, searching, and repeating attempts until an answer is received. Their questions are also not pre-written, creating a strong and unpredictable load on the data layer.
The complexity is compounded by the fact that business data is distributed across multiple locations: transactional records, chat memory, documents, dashboards, and vector stores for semantic search. The agent has to search all these sources and combine the results before providing an answer.
Every additional data query increases costs. If the data is outdated, the answer will be incorrect. Nitin compared this to driving with an inaccurate traffic map. Furthermore, when data comes from multiple sources, it becomes harder to determine the source of the answer, which creates a trust issue.
He compared this situation to sending a person to five filing cabinets to collect papers. By the time the person returns from the fifth cabinet, the information from the first may already be outdated.
Nitin outlined four requirements that agents must meet to transition from pilot mode to full operation. VeloDB's answer is a unified engine that satisfies all these needs. The company was founded in 2023 by initial developers of Apache Doris, an open-source real-time analytics database that became a top-level project of the Apache Software Foundation in June 2022. According to VeloDB, Apache Doris has over 14,000 stars on GitHub and 700 contributors, and is used by more than 5,000 enterprises worldwide.
To reduce the number of back-and-forth queries slowing down agents, VeloDB supports hybrid queries. One query can combine SQL, vector search, and text search, performing deterministic and probabilistic searches in parallel. The result is a single reliable source instead of disparate data.
Nitin presented two examples of companies using such an architecture in their work. The first is one of the largest cryptocurrency exchanges with over 120 million users, which he did not name. The exchange provides transaction data to AI agents, which retail investors can request, for example, to see the positions of major traders in a certain asset. He reported that its agents process about 33,000 dialogues with a final latency of about 3 milliseconds, operating around the clock.
The second example is the Chinese AI company MiniMax, which listed on the Hong Kong Stock Exchange in January 2026 and serves 212 million users in over 200 countries. MiniMax rebuilt its logging system on Apache Doris after abandoning Grafana Loki, as logs became a valuable source of information worth retaining and querying.
Nitin specified that MiniMax uploads data at a rate of 10 Gbps and can query about 10 petabytes in less than two seconds, while reducing costs by 70%. VeloDB separately stated that the Doris-based system now supports logs across all of MiniMax's business lines in petabyte scale with availability exceeding 99.9%.
The same problems apply to early-stage startups creating agents, added Nitin. VeloDB collaborates with fintech startups facing the same scaling challenges as MiniMax or the crypto exchange, just at an earlier stage.
His concluding thesis was that agents will always ask hundreds of questions, so the infrastructure must ensure that each one is cheap, fast, and up-to-date. For Nitin, scaling AI agents depends less on finding the best model and more on providing agents with reliable, real-time data from a single source. He argued that companies that correctly configure the data layer can make decisions faster, reduce costs, and confidently move their agents from pilot mode to operational use.



