The news
Rory Blundell, CEO and co-founder of Gravitee, appeared on Bloomberg Brief with Vonnie Quinn. He stated that teams building or deploying AI must place governance, security, and control at the center of their work. The comments came during a segment focused on the current state of AI adoption and the risks that surface when those three areas receive less attention than model performance or speed of rollout.
Context
Blundell spoke against the background of rapid AI tool deployment across industries. Gravitee works with API and integration infrastructure, areas that increasingly intersect with AI services. The prior pattern in many organizations has been to add AI features first and address oversight later. Blundell’s position reverses that order. The interview aired on Bloomberg Technology on August 7, 2026, as part of ongoing coverage of enterprise technology risks.
Details
Blundell listed three areas explicitly: governance, security, and control. He framed them as requirements rather than optional extras. The interview did not include specific metrics or product announcements from Gravitee. No timelines for new features or policy changes were given on air. Bloomberg presented the segment as part of its ongoing coverage of enterprise technology risks. The discussion centered on the need for organizations to treat these priorities as foundational when scaling AI systems that interact with existing data flows and external services.
The single-source nature of the segment means the remarks stand as one executive’s assessment rather than a consensus view from the broader API or AI platform sector. Blundell’s background at Gravitee, a company focused on API management and integration, gives his comments a perspective rooted in infrastructure rather than model development itself. No counter-statements from other executives appear in the available material.
Why it matters
Companies that treat governance, security, and control as afterthoughts now face concrete exposure. AI systems can generate outputs at scale, call external services, and retain context across sessions. Without defined oversight, those capabilities create paths for data leakage, unauthorized actions, and compliance failures. Security teams already manage API traffic; extending that discipline to AI endpoints is a direct extension of existing work rather than an entirely new discipline. Control mechanisms determine who can change model behavior, which data the model sees, and which downstream systems it can reach. Governance supplies the decision rights and audit trails that let organizations prove they acted reasonably when something goes wrong.
The interview adds one more public signal that the conversation inside enterprises has moved from “how fast can we ship AI” to “how do we keep it within bounds.” API platforms already enforce rate limits, authentication, and logging; applying the same patterns to AI calls reduces the chance that a model will trigger unintended actions or expose sensitive data through an integration point. Organizations that embed the three priorities early can reuse existing API management patterns and reduce the chance of headline incidents. Those that delay this work will spend later on remediation instead of prevention. Blundell’s emphasis aligns with the practical reality that AI does not remove the need for these layers; it multiplies the surface that must be covered.
---
Sources:
{"word_count": 612, "sources_used": 1}
No comments yet