May 21, 2026
By Hubert Brychczynski

TechEx North America 2026, held May 18–19 at the McEnery Convention Center in San Jose, was an intensive, two-day conference with separate tracks for AI & Big Data, Cyber Security, Digital Transformation, IoT, Data Centers, Intelligent Automation, and Edge Computing.
James Ash, our Business Development Executive, stepped into this cross-section of industries for insights around AI, and the breadth of topics broadened the picture. You could not talk about agents without someone asking about identity, observability, or unit economics in the next room. As for AI itself, the discussion centered less on the foundation models and more on the engineering that makes them work in production.
This article highlights the most pointed conversations from the conference and the relevant work we do at Janea Systems; it also draws on the patterns we keep seeing in client engagements when AI moves from pilot to production.
A recurring theme across at least five sessions was that the gating factor for enterprise AI is no longer the model. It is the data estate underneath it.
The presentation "The AI Pipeline Starts with Storage: Architecting Scalable Data Foundations" framed it bluntly: the model is the engine, but the data pipeline is the fuel. Most enterprise pipelines are clogged by legacy cloud constraints and egress gatekeeping. "From AI-Ready Data to Agentic Action" echoed a similar point: AI agents are being deployed faster than the data infrastructure beneath them can support. And finally, "From Fragmented Data to Agent-Ready" sharpened the consequence: humans can work around inconsistent data; agents cannot. This makes data quality structurally critical.
Our engineers see this gap in most engagements. For a fintech client whose historical data was not stored in a way ML could touch, we built an AI-ready data lake on Delta Lake and Azure Synapse; that foundation later supported an agent factory on top, a multi-assistant system handling between 15,000 and 50,000 delinquency cases a day. For a multinational biopharmaceutical client, we built the Extensible Data Connector to lift a 2,000-row processing ceiling in the Signals Notebook used by more than 6,000 scientists.
Two of the more sober sessions on the agenda dealt with money. "The Real AI Apocalypse: When Token Economics Break Your Business Model" laid out the case that early pilots optimize for accuracy and use cases while production reveals a different problem entirely: token consumption, inference costs, data movement, and infrastructure inefficiencies compound into spend that nobody projected. "The Hidden Cost of Scaling AI That Nobody Budgets For" came at the same problem from the data infrastructure side: every agent query reaches back into the underlying data warehouse, and at scale the parallel load forces overprovisioning and produces cloud bills nobody projected.
The cure is usually architecture. Our taxonomy-driven JSPLIT framework filters Model Context Protocol servers down to the few relevant to each query, cutting input token cost by up to 100x in high-density environments while holding accuracy near 70%, where baseline systems collapse below 40%. Lower-level optimization compounds the savings: refactoring the TensorFlow and PyTorch implementations of Microsoft Bing Maps' DeepCAL model delivered a 50x speedup on the TensorFlow side, 7x faster training runs, and 2x speedup in batch processing.
Three sessions on the agenda converged on the same uncomfortable observation: "Ship Agents at Developer Speed: Without Asking Permission," the panel "The AI Risk Stack," and "Trust as a Competitive Advantage." Authentication answered who the agent is. Nobody answered what the agent is allowed to do.
The first session framed the gap as Agent Personas, where the agent's job description becomes the runtime guardrail: allowed tools, data scopes, and rate limits, defined at deploy time and enforced automatically. The second focused on building the broader AI assurance stack: risk classification, monitoring, logging, and audit trails. The third positioned transparency itself as the differentiator, with a discussion centered on what real-world explainability looks like across finance, healthcare, and logistics.
These three threads point at the same problem from different angles, and our agentic AI security work for banking has converged on a layered answer that sits outside the model, testable like any other software. The base layer is least-privilege access enforced at the data-access layer rather than the prompt: the agent is read-only and tenant-scoped, which means it can neither tamper with data nor leak another customer's, because it never has either in context. Sensitive values then flow through a deterministic filter on the user-to-LLM round trip, masked going in and restored on the way out where the user is authorized to see them, with a continuous-evaluation loop using paired LLM and human judges for the cases regex cannot catch.
This complements the Agent Personas model from the TechEx session: Personas define what an agent is allowed to do at deploy time; these controls enforce it at the data layer at runtime. Observability sits alongside. Langfuse with Datadog, canary and blue-green deployment, and unified runbooks brought MTTR below 30 minutes on the sports analytics platform.
The session "Beyond Copilot: Architecting Agentic AI for Real Business Impact" called out the obvious tension: most organizations are running AI pilots, very few are seeing the kind of business outcomes the AI investment thesis promised. The session's argument was that the next step is not better copilots but agents that act on insights within existing enterprise systems. The pattern is a layer that automates workflows, orchestrates processes, and produces measurable results, rather than a full stack rebuild.
That description matches the agentic systems we have shipped to production.
The agent factory we built for the fintech client handles between 15,000 and 50,000 delinquency cases a day depending on the assistant and channel, with the same modular foundation on track to absorb roughly twenty assistants across audiences without a rebuild each time. A sports analytics platform we delivered serves more than 50,000 prompts a month and processes more than 6 billion tokens, holding query response times in the seconds even under traffic spikes through load shedding, just-in-time context generation, and a RAG pipeline that encodes frequent queries into a specialized vector store. In both cases, throughput at production scale came from operational maturity built in before the first agent even shipped.
The closing panel worth dwelling on was "Buying vs Building AI – What's Right for Your Enterprise?", a cross-sector discussion on off-the-shelf platforms versus in-house custom solutions, vendor lock-in, IP ownership, and long-term cost.
Most enterprises frame this as a binary choice, and the framing usually fails them. The data tells a more interesting story. As we documented in Be the 5%: How Businesses Succeed With AI:
In MIT's sample, external partnerships with learning-capable, customized tools reached deployment roughly 67% of the time, compared to 33% for internally built tools. The gap is consistent across organizations. More enterprises attempt internal development, but success rates heavily favor external partnerships.
That two-to-one advantage shows up because external partners have built the muscle for what most enterprises only do once or twice: moving systems from prototype to production, with the data engineering, MLOps, security, and observability all wired together correctly the first time.
The work we did for BigFilter shows when leveraging off-the-shelf components is the right call. BigFilter needed to validate a fact-checking concept on a tight budget and timeline. Training custom AI models would have been impractical for a prototype. So we used publicly available LLMs as stand-ins for custom models, designed a segmented architecture for observability, and delivered a functional prototype in three months. That prototype gave the client the strategic insights they needed to make data-driven decisions about whether and how to invest further.
For more advanced production systems (the agent factories, the accuracy-first analytics engines, the AI-ready data lakes), the calculus shifts. You still want external expertise to get the architecture right, and you also need the system customized to the business, with the data engineering and operational layer built around your specific workflows. That is when external partnership matters most, and where the MIT data shows the biggest gap.
TechEx North America 2026 made the through-line clear: AI's hardest problems are no longer about the model. They are about the data underneath, the cost curve around it, the trust layer on top, and the operating discipline that holds it all together long enough to deliver business outcomes. The teams that succeed treat AI as production engineering, not as something exempt from the usual rules.
That is the work we do at Janea Systems. We help enterprises build AI systems that hold up in real-world conditions: data foundations that agents can trust, cost architectures that scale predictably, security and observability that survive audit, and the operational maturity that turns pilots into platforms.
If you are mapping out the next phase of your AI program, get in touch via the form below. Our AI Maturity Workshops run three to fifteen business days and focus on identifying the use cases most likely to pay off, validating whether your current infrastructure can support them, and outlining how those solutions would be deployed and monitored in your existing environment. Or check out our full range of Services to start a more specific conversation.
Ready to discuss your software engineering needs with our team of experts?