Headless API: One Genie, Any Surface

Headless API means Genies are no longer tied to a single interface. Teams can embed Workato’s agentic AI directly into the products and tools employees already use, instead of building a new interface just to reach a Genie. Genies can also respond directly to business events, act autonomously without a person triggering each step, and run inside any agent harness, coordinating with other agents rather than waiting on a human. This makes it possible to embed conversations, approvals, event-driven actions, and multi-agent orchestration directly into customer applications, websites, mobile apps, internal systems, automated workflows, and other AI agents.

Every Headless API call carries native governance: the calling identity, whether a live user or an approved service account, travels with the request, access is scoped per Genie, and revocation is instant via key rotation. The result is that teams can safely embed Workato’s agentic AI directly into customer-facing products and internal tools, giving users governed access to AI experiences seamlessly within the applications they already use every day.

Also Read: Bizoforce is launching HeyAdmin.ai: An Enterprise-Grade Agentic AI Platform 

Agent Guardrails: Secure by Default, Configurable to the Business

Agent Guardrails give every Genie native controls across three layers:

• Data Protection — Blocks, redacts, or tokenizes PII before it ever reaches the model. Detects and stops profanity, blocked words, and denied topics before they reach the agent. Model flexibility across OpenAI, Anthropic, and AWS Bedrock is embedded using customer credentials.
• Access & Control — Choose a real user identity, connected and approved by the user themselves, or an admin-configured service account. High-stakes actions route to a human for approval in Slack or Teams.
• Auditability & Compliance — Logs every action in a unified, auto-redacted Conversation History. Inherits SOC 2 Type II, ISO 27001, HIPAA, and PCI-DSS 4.0 certification from the platform.

Guardrails are customized to a Genie’s audience, capabilities, and data, so Genies are secure and compliant by default, with flexible controls that let enterprises move fast where it’s safe to do so and apply stricter oversight where it isn’t.

“As orchestration becomes the backbone of the AI era, agents can’t just wait for a person to type into a chat window. They need to act on business events, coordinate with other agents, and orchestrate interactions across business applications, all without losing sight of who they’re acting on behalf of, what systems they’re touching, and what processes they’re running,” said Bhagat Nainani, Chief Product Officer at Workato. “Workato can now deliver secure agents anywhere, backed by Headless API and Agent Guardrails.”

“Most enterprises have proven that agents work in a pilot. Customers are looking for a solution to solve the harder problem of using AI in production without renegotiating security and compliance for every new application surface,” said Larry Carvalho, Principal Analyst at RobustCloud. “By making Headless API and Agent Guardrails native to one platform, Workato is removing the governance rework that keeps agents confined to pilot projects. Workato ensures every action is tied to a real identity, and PII is protected before it reaches the model.”

“Workato lets us build one secure, trusted place where agents can interact with all of our enterprise systems,” said Kristina Frost, Senior Director, Enterprise Business Systems at Nasuni. “If we can take a manual task off someone’s to-do list, I’ve opened time for them to do meaningful, impactful work.”

Source: BusinessWire

The post Workato Introduces Headless API and Agent Guardrails, Bringing Governed AI Agents to Any Business Application appeared first on ITDigest.

Highlights

• Grounded answers & action execution: Agents answer from the company’s knowledge base (documents, databases, PDFs, videos, etc.) and can invoke enterprise tools and APIs to execute tasks and automate workflows to complete user requests.
• Self-improving and learning: Every feedback (thumbs-up or thumbs-down) triggers automatic fine-tuning of the retrieval models.
• Open architecture: Switch AI providers, storage backends, or deployment models – cloud, on-premise, or air-gapped without rewriting your agents.
• Cost you control: Run on open-source LLMs to cut token cost, with spend limits enforced automatically.
• Enterprise-grade: Has in-built data privacy, security, governance, observability and compliance

Also Read: Kong Announces Insomnia and Kong Konnect Integration to Unify API and AI Development Workflows 

Why we built HeyAdmin

Foundational models are remarkable, but they are general-purpose by design. These models are not designed for any specific company. HeyAdmin is built to be the layer above it: a platform that uses foundational models and fine-tunes the SLM for an agent that knows your business, operates across your channels, and improves on every rated conversation.

“We have envisioned the most flexible, and agile approach to deploy enterprise-grade Agentic AI. Our Agentic AI platform has been built for AI-First workflows at the lowest possible cost and with a unique “horizontal-vertical” architecture that facilitates use cases and workflows across verticals that can be deployed through video and voice agents.” Bala Palamadai – Chief Executive Officer, Bizoforce

“We have built the HeyAdmin platform using an architecture that allows rapid deployment and seamlessly integrates with a variety of Enterprise systems and databases, and can be deployed leveraging any LLM including Open-source, or cloud-based AI models in the company’s ecosystem.”
Sudhanshu Pandey – Chief Digital Officer, Bizoforce

Source: Globenewswire

The post Bizoforce is launching HeyAdmin.ai: An Enterprise-Grade Agentic AI Platform appeared first on ITDigest.

Teams still argue over priorities. Customers still wait. That is exactly why figuring out how to adopt a DevOps culture in big organizations matters. It’s not just about adding yet another tool, or building one more CI/CD pipeline, you know. DevOps is more about shifting how people actually team up, how decisions get made, and how responsibility is shared, from the whole planning part through to production. The organizations that get this right see the difference.

McKinsey’s April 2026 software development research found that the top-performing companies achieve 16 to 30 percent improvements in productivity, time to market, and customer experience, along with 31 to 45 percent gains in software quality. The technology helps, but the culture is what decides whether it delivers results.

Beyond the Dev and Ops Divide Through Cross Functional Teams

Enterprise DevOps rarely breaks because engineers lack technical skills. It breaks because the whole organization was designed like, long before DevOps even became the thing. Development, QA, Security, and Operations live in separate teams, report to different managers, and chase different targets. People do their bit, pass it along to someone else, and then wait. Then, when feedback finally comes back, the context is already half gone. The process keeps trudging forward, but the speed of progress gets worse with every single handoff.

Most orgs try to fix it by adding yet another approval layer or another tool. That sort of thing deals with the symptom not the actual issue. The structure has to shift instead. Cross functional product teams work because they own the outcome, not just one stage of delivery. Developers, testers, security engineers, and operations engineers work through problems together right from the start. Conversations show up earlier, choices get made quicker, and responsibility stops ricocheting around departments.

Platform Engineering pushes this further. A dedicated platform team builds an Internal Developer Platform with standardized environments, reusable services, and self-service capabilities. Developers do not waste half the sprint waiting for infrastructure or recreating the same setup every time a project starts. They spend that time building features that actually move the product forward.

The same kind of thinking applies to performance too, you know, because if Development is rewarded for shipping faster, while Operations is rewarded for avoiding change and conflict, then it’s basically inevitable that they’ll clash. Shared Service Level Objectives help keep everyone aimed at customer outcomes not the little departmental wins, or whatever. McKinsey reflects this shift as well. It found that 29 percent of organizations cocreate strategic plans throughout the year across business and technology teams, while that figure rises to nearly half among top-performing companies. That is not collaboration for the sake of culture. It is collaboration because it produces better business results.

Automating Software Delivery Without Sacrificing Enterprise Governance

Speed sounds impressive until it collides with compliance. That is the reality for largest organizations. A startup might push updates several times a day with minimal oversight. An enterprise cannot. Every release has to meet security policies, internal controls, and regulatory stuff like SOC 2, ISO 27001, HIPAA, or PCI DSS. But when governance sits outside the delivery process, well, every single deployment turns into some sort of long approval affair, with no end. People wait, context kind of evaporates, and yeah frustration builds up on both sides.

The point is not picking speed over control, or control over speed. It’s folding governance right into the delivery pipeline from the very beginning. Compliance as Code basically means that the whole manual checking routine gets swapped for automated policy tests, that fire every time code moves through CI/CD. At that point infrastructure configurations, access rules and even the approval requirements turn into repeatable patterns and not something that depends on who happened to be reviewing that day, or whether they were in a ‘good mood’ or not. Audits become easier because evidence is generated continuously rather than collected at the last minute.

Security needs the same treatment. Too many organizations still treat it as the final checkpoint before production. By then, fixing vulnerabilities is slower, more expensive, and often delayed to meet release deadlines. When you start integrating SAST and DAST scans into the pipeline, it changes that. Developers catch issues while they are still writing code and security teams spend less time firefighting, plus fixing problems becomes part of the usual engineering flow not a separate event.

The strongest governance models also share one thing in common. They are intentional. PwC’s 2026 AI Performance Study found that AI leaders are 1.6 times more likely to have a Responsible AI framework, 1.7 times more likely to have documented governance from use case selection through monitoring, and 1.5 times more likely to have a cross functional AI governance board. DevOps works the same way. Mature delivery is built on consistent guardrails, not constant supervision.

Engineering Psychological Safety Where Mistakes Become Learning Opportunities

Fear is expensive, especially inside large engineering organizations. When one failed deployment can affect promotions, performance reviews, or leadership trust, people naturally become defensive. They tend to push releases back, sidestep the hard choices, and sometimes they do not mention a small glitch before it turns into a much bigger incident. From far away, everything looks fine, like it’s all in control. But underneath, the org is slowly piling up technical debt, uneven communication, and other kinds of quiet hazards, that later pop up at the worst moment possible.

So yeah, a solid DevOps culture really leans on psychological safety almost as much as on automation. The teams need the kind of assurance that if someone reports a mistake, the outcome will be a stronger system, not some quiet effort to point fingers. A blameless post mortem helps set that tone. It begins by putting together a crisp timeline of the incident, and then going through what happened and why it happened. In each conversation, the center has to stay on systems, routines, the choices that were made, and how people communicated. The real issue is never about who messed up. The real question is, what made the failure possible, and what can the organization do so it won’t keep repeating, you know without just saying ‘lessons learned’ and moving on. Also every review should end with things people can actually do, actionable upgrades, clear ownership, and deadlines that are realistic not pie in the sky stuff.

Learning takes space to try new paths as well. Nobody is really eager to poke at a bold idea, if one small slip could hit millions of users at once kind of like with canary deployments and feature flags, those approaches help cut that risk down because they shrink the blast radius of each release. Then the teams can look at the changes in production, grab signal from real user behavior, and if anything goes sideways they can roll back quickly.

Clear communication makes that process even stronger. DORA notes that a clear and well communicated AI stance amplifies AI’s positive impact and reduces friction. The same thinking applies to DevOps. When expectations are consistent and teams understand the direction, people spend less time second-guessing decisions and more time improving the system together.

Also Read: Strategic Steps for a Successful Digital Transformation Roadmap: A Practical Guide for Enterprise Leaders 

Measuring What Actually Moves the Needle with Enterprise DORA Metrics

One mistake shows up almost everywhere. Organizations start measuring everything simply because they can. Suddenly every dashboard is full of numbers. Lines of code. Story points. Tickets closed. Resource utilization. It looks like progress until you ask a simple question. Did any of those numbers actually help customers get better software? Most of the time, the answer is no. In fact, chasing those metrics usually creates the opposite effect. Teams start optimizing for the dashboard instead of the product. Developers rush work to hit targets. Operations become hesitant because stability is all they are judged on. Before long, everyone is protecting their own score instead of improving delivery together.

That is why the DORA Metrics have become the benchmark for measuring DevOps performance. They don’t reward activity. They measure outcomes. Deployment Frequency tells you how often value reaches production. Lead Time for Changes shows how long an idea takes to become usable software. Mean Time to Recover reflects how quickly teams recover when something breaks. Change Failure Rate reveals how often deployments introduce problems that need fixing. Looking at one metric in isolation tells only part of the story. Looking at all four together gives a much more honest picture of how software delivery is actually performing.

The important part is what happens after the numbers appear. Good engineering leaders do not wave a dashboard around asking why Team A is slower than Team B. That completely misses the point. The conversation should be about friction. Where are approvals getting stuck? Which handoffs keep delaying releases? Why are the same failures showing up every sprint? Those discussions improve systems. Blaming people never does.

DORA’s own research supports this thinking. It states that software delivery performance metrics predict better organizational performance and team well-being. That is exactly why these metrics matter. They are not another reporting exercise for leadership. They create visibility into how work flows across the organization. When teams use them to remove bottlenecks instead of ranking people, continuous improvement stops being a slogan. It becomes part of how the organization works every single day.

The Long Term Horizon of Enterprise Transformation

A lot of organizations seem to believe that DevOps is basically done the moment the pipelines are automated. Which is kind of true, but also no, because that’s typically where the messy work starts.

Yes, technology can make release cycles faster, but it doesn’t really mend the gaps between groups, or the unclear reasons behind things, and also not the general mood where people kind of hesitate to say what they actually see. Those problems don’t just disappear, they slide around, slowly, through practiced routines, sharper leadership, and systems that nudge collaboration rather than create friction.

Platform Engineering, blameless learning, and useful metrics count too, but only once they’re woven into what the org does every day, like it’s ordinary. Sure, a company can copy the tools, and with effort they can mimic certain processes. Still, copying culture is way harder trust between people, continual refinement, and everyone rowing the same direction. Over time, that ends up being the toughest advantage for competitors to reproduce, and it also tends to drive the biggest business value.

The post How to Adopt DevOps Culture in Large Organizations: A Practical Guide to Enterprise Transformation appeared first on ITDigest.

A global corporation, for example, by allowing smart coding machines to work with its confidential codes, might expose itself to huge risks such as differing coding styles, unexpected dependencies, security holes, and inadvertent disclosure of intellectual property. For this reason, most of the enterprise AI work has been confined only to narrow sandbox environments, with no links to main-line deployment workflows.

To eliminate this operational friction, global digital business and IT services giant NTT DATA announced a strategic partnership with Cursor, the leading multi-model AI coding platform.

By embedding Cursor’s advanced AI agents directly into its global engineering engine under a strict, enterprise-grade governance framework, the company is systematically modernizing its delivery layer. For the IT Services, Systems Integration, and Digital Engineering industries, this milestone launch redefines how software is built and maintained, bridging the gap between machine-speed development and absolute corporate compliance.

Technical Integration: Codebase-Wide Context Paired with Enterprise Guardrails

The core capability behind the partnership is the deployment of Cursor Enterprise across NTT DATA’s global software engineering practices. Unlike basic single-file code completion extensions, Cursor embeds advanced AI agents directly into the developer’s Integrated Development Environment (IDE), providing multi-model flexibility alongside codebase-wide logical reasoning.

Also Read: Innovaccer and AWS Launch Healthcare Alliance to Advance Clinical AI Autonomy

To safely scale this acceleration across complex enterprise client environments, the integrated architecture introduces a series of strict administrative controls:

Codebase-Wide AI Context: Autonomous agents continuously index and parse full enterprise code repositories, enabling developers to write, refactor, and review code with complete contextual awareness of internal system dependencies.

Organization-Wide Privacy Mode: Hardens the development environment by ensuring that proprietary client source code, internal comments, and telemetry strings are never ingested or utilized to train external public models.

Centralized Policy Enforcement: System administrators gain granular control over agent capabilities, backed by centralized Single Sign-On (SSO), real-time audit logging, and audit-ready policy guardrails.

Cursor Center of Excellence (CoE): NTT DATA is establishing a specialized internal practice to standardize development prompts, build tailored enablement rubrics, and scale agentic coding capabilities across global practices and industries.

Transforming the IT Services and Systems Integration Market

The institutional deployment of an advanced, agentic coding platform across a $30+ billion technology services giant triggers critical shifts across the global tech consultant landscape.

The Evolution from Headcount to AI-Native Output Metrics
For decades, the global system integration market operated on linear, headcount-driven commercial models. If an enterprise required a legacy mainframe modernization or a massive cloud migration, the service provider billed according to the sheer volume of software engineers assigned to the project.

The integration of Cursor agents into the core of NTT DATA‘s delivery engine challenges this model. As AI-native tools dramatically compress the time required to refactor legacy code, competing IT vendors can no longer justify bloated, labor-heavy timelines. The industry is being pushed into an era of high-velocity, platform-led delivery, where service providers are compensated based on execution speed and technical accuracy rather than hours logged.

Elevating the Developer Profile to System Architect
As autonomous agents assume the routine, repetitive burdens of software engineering such as syntax translation, unit testing generation, and monotonous boilerplate coding the baseline role of the systems engineer is undergoing a structural upgrade.

Software developers will spend significantly less time manually writing code fragments from scratch. Instead, their career paths will pivot entirely toward high-level system design, defining precise architectural constraints, and verifying agent outputs shifting IT consulting from manual labor to strategic platform orchestration.

Broad Operational Impact on Enterprise Businesses

For Fortune Global 100 enterprises navigating complex digital transformation initiatives, deploying an AI-native, governed engineering pipeline yields clear commercial advantages.

Accelerating the Modernization of Core Legacy Estates
A number of enterprise firms are constrained by large legacy estates that are key to their operation, yet fragile and costly to manage. The manual refactoring of such an environment can take months or even years and will introduce serious faults into the system.

The use of self-sufficient AI to analyze the environment and generate recommendations for its transformation helps the corporate boards resolve technical debt swiftly. They can upgrade their system backends, transition to modern cloud solutions, and introduce new features, all within a reduced budget and without impacting system operation.

Insulating Corporate Brands from Compliance and Security Failures
Using unmonitored consumer AI platforms to generate code introduces severe regulatory compliance liabilities, particularly around data handling, copyright tracking, and information security. If a developer accidentally leaks sensitive proprietary configurations into an un-governed external model, the company faces immediate intellectual theft and legal friction.

Moving all AI-assisted engineering into a single, centralized workspace governed by organization-wide privacy constraints eliminates this operational liability. Corporate compliance officers gain real-time visibility and an unalterable audit trail of how software is being built—allowing companies to confidently capture the productivity benefits of AI without exposing the enterprise to reputational or regulatory penalties.

The post NTT DATA and Cursor Partner to Launch Governed AI Coding Platform for Enterprises appeared first on ITDigest.

As organizations race to move AI from experimentation to production, fragmented infrastructure remains a documented barrier with disconnected tools, siloed teams, and spiraling costs making governance and control of the ecosystem impossible at scale. This integration transforms how developers discover, inspect, debug, and automate API workflows, addressing the three most common sources of friction: API discovery and access, governance and consistency, and the growing need to support AI-driven workflows.

“AI is only as effective as the context it has access to,” said Marco Palladino, CTO and Co-Founder of Kong. “By integrating Insomnia with Kong Konnect, we’re giving both developers and agents instant access to an organization’s entire API ecosystem, resulting in a faster, more seamless experience for developers and a stronger foundation for agentic software development.”

Also Read: CIQ Expands Fuzzball to Full Multi-Cloud so AI and HPC Teams Ship Faster and Spend Less

Core Capabilities for Enterprise API and AI Teams

The integration delivers several key capabilities designed to streamline enterprise workflows:

• Unified Access via Konnect Sync: Developers no longer need to hunt through outdated documentation or manually import API specs. By authenticating with their Kong Konnect Personal Access Token (PAT), developers gain instant access to all available API and AI endpoints directly within Insomnia. This enables developers to seamlessly pull environment configurations from Konnect into Insomnia with a single click.
• A Single Source of Truth: When platform teams update API specifications in Konnect, those changes automatically reflect in Insomnia. This eliminates version mismatches, slashes developer onboarding time, and ensures teams are always testing against approved definitions.
• AI Agent API Access via Insomnia CLI: Coming to Tech Preview – The CLI ensures that large language models (LLMs) and autonomous agents can access the collections, environments, and configurations, directly inside Insomnia without approximation or workarounds. Enterprises can now automate, orchestrate, and extend API testing using AI without workflow bottlenecks. The CLI outputs structured JSON responses specifically optimized for parsing by LLMs, bridging the gap between human-readable interfaces and agentic automation.
• Native Git-Powered Version Control: In tandem with the CLI, collections and configurations can now be managed completely via Git from the command line empowering developers to work from their chosen CLI tool.

Source: PRNewswire

The post Kong Announces Insomnia and Kong Konnect Integration to Unify API and AI Development Workflows appeared first on ITDigest.

AI is everywhere now. Customer support teams use it. Marketing teams use it. Security teams use it. Leadership teams are pushing forward AI initiatives because nobody really wants to be the company that gets left behind, right. The whole rush feels understandable, even if it’s a bit frantic. The part that gets messy is governance, because that’s not moving at the same speed.

Most organizations have spent years saying things about fairness transparency, and accountability. But talking and actually doing, are two totally different animals. The gap is bigger than a lot of leaders are imagining, and it shows up fast. The World Economic Forum says less than 1% of organizations have fully operationalized responsible AI. You’d think that number would make every executive feel pretty uneasy, and not just slightly. AI adoption is scaling. Responsible AI practices are not.

That is why creating responsible AI development frameworks has become a business priority, not a compliance exercise. The goal is simple. Build AI systems that people can trust, regulators can understand, and organizations can manage without creating unnecessary risk.

Ethical AI vs Responsible AI

A lot of people treat ethical AI and responsible AI like they’re the exact same thing. They are connected, sure, but they aren’t identical. Sometimes it feels like they’re just, you know, one concept, but no.

Ethical AI is mostly about principles. It’s about fairness, human rights, privacy, transparency, and also the broader societal impact. Those ideas matter because they kind of set the direction, what organizations should aim for, in the first place.

Responsible AI is more like what follows after the talk ends. It’s the execution part, the practical side, when the conversation turns into decisions.

It turns principles into actions. It asks practical questions. Who owns AI risk? How will bias be tested? What documentation exists? How will decisions be explained? What happens if a model fails?

This distinction is becoming increasingly important as governments and regulators move from discussion to action. UNESCO’s Recommendation on the Ethics of Artificial Intelligence became the first global standard on AI ethics and applies across 194 member states. The message is clear. Ethical AI is no longer a theoretical concept. Organizations are expected to prove that responsibility exists inside their operations.

Pillar 1: Corporate Governance and Oversight

Every responsible AI framework starts with governance. Not technology. Not models. Governance.

One of the biggest mistakes organizations make is treating AI as a technical project owned only by data teams. AI decisions can create legal, operational, security, and reputational consequences. That means governance needs broader representation.

A strong AI governance board should include legal teams, compliance leaders, cybersecurity experts, data scientists, and business stakeholders. Different perspectives matter because AI risks rarely stay inside one department.

However, governance without authority is useless.

If a model shows a pretty major risk, then at least somebody should get the authority to stop the deployment. Governance structures need enforcement mechanisms, escalation routes that make sense, and also clear ownership, not just nice words.

Ownership is where many organizations seem to get stuck. When AI systems fail, a lot of people go ahead and blame the algorithm. That kind of framing avoids taking responsibility, it kind of sidesteps accountability instead of actually creating it. Every stage of the AI lifecycle should have a clearly assigned owner. Somebody owns the data. Somebody owns testing. Somebody owns compliance. Somebody signs off on deployment.

The urgency is obvious. IBM’s 2026 Tech Leader Study found that only 11% of CIOs and CTOs feel fully prepared for the scale of AI agent deployment expected over the next year. Companies are moving fast. Readiness is not.

Pillar 2: Data and Model Lifecycle Methodology

Responsible AI starts long before a model reaches production.

Everything begins with data. Poor data creates poor outcomes. If organizations cannot explain where data came from, whether consent exists, or how bias entered the dataset, they are creating risk from day one.

This is why data lineage matters. Teams should be able to trace data sources, understand transformations, and document ownership throughout the lifecycle. That visibility becomes critical during audits, investigations, and compliance reviews.

The next challenge is transparency.

High-performing models are valuable. Models that nobody understands create a different problem. Organizations increasingly need explainability, especially when AI influences customer experiences, employee decisions, or regulated processes.

Tools like SHAP and LIME help organizations understand why a model reached a specific conclusion. That explanation builds confidence and creates accountability.

Then comes testing.

This is where many companies cut corners. They test for functionality and assume everything else will work itself out. That approach does not survive in modern AI environments.

Responsible AI requires adversarial testing. Teams need to look for prompt injection risks, data leakage, harmful outputs, and unexpected behavior before deployment.

Google offers a useful example of this mindset. Google’s Content Adversarial Red Team completed more than 350 exercises during 2025 to identify vulnerabilities and stress-test systems. Gemini 3 also underwent Google’s most comprehensive safety evaluations to date. The lesson is simple. Strong AI systems are challenged before they are trusted.

Also Read: Best Practices for Cloud Migration and Modernization: A Strategic Roadmap for Enterprise Success

Pillar 3: Regulatory Compliance and International Standards

The compliance landscape is becoming more complicated every year.

Organizations now face overlapping regulations, privacy requirements, and industry standards. A framework that works in one market may not satisfy requirements somewhere else.

The EU AI Act reflects this shift a bit, and honestly it feels like it is saying, ‘not all AI is the same.’ Rather than just treating every AI system identically, it moves toward a risk based approach. In other words, higher-risk applications get tighter duties, while certain uses may even be limited or restricted completely.

At the same time, organizations really should look at the guidance coming from different frameworks like NIST AI RMF, the MeitY recommendations, and also consumer protection authorities.

The biggest mistake companies make is treating compliance as paperwork.

Real compliance is evidence. It is documented testing, risk assessments, governance reviews, monitoring records, and decision logs. When regulators ask questions, organizations need proof that controls exist and actually work.

Standards like ISO/IEC 42001 can help, kind of create that structure. They give you a formal framework for governance and accountability, but also for risk management, and then this whole continuous improvement loop. And more than that, they tend to make things consistent across teams, as well as across business units.

Pillar 4: Operational Monitoring and Continuous Auditing

Many organizations think deployment is the finish line.

It is not.

AI systems change because the world around them changes. Customer behavior evolves. Market conditions shift. New data enters the system. Over time, model performance can drift away from original expectations.

That is why continuous monitoring matters.

Organizations should track performance, review outputs, monitor anomalies, and create alerts when unusual patterns emerge. Waiting for customers to discover problems is not a monitoring strategy.

Continuous auditing is equally important. Governance controls should be reviewed regularly. Risk assessments should be updated. Compliance obligations should be reassessed as regulations evolve.

There should also be a clear response process. High-risk systems need escalation procedures and kill-switch capabilities when necessary. Problems are easier to manage when organizations act early rather than react late.

Conclusion

The real challenge with AI is no longer adoption. Most organizations have already crossed that bridge. The challenge is building systems that remain trustworthy after deployment.

Governance, accountability, transparency, compliance, testing, and monitoring are no longer optional layers. They are becoming core business requirements.

The financial part is kind of coming into view more. McKinsey’s 2026 AI Trust Maturity Survey found that organizations putting $25 million or more into responsible AI are more likely to see EBIT impact above 5% reported. And yeah, that shifts the whole conversation a bit, because it’s not only about lowering risk. Responsible AI is becoming, sort of, a real competitive edge. The firms that catch that early will probably be the ones that end up getting the biggest benefit.

The post Creating Responsible AI Development Frameworks: A Guide to Building Ethical, Transparent and Compliant AI Systems appeared first on ITDigest.

By delivering real-time, context-aware work intelligence across the market’s primary generative ecosystems, Smartsheet eliminates vendor lock-in and allows enterprises to extract deep operational value from the AI tools they have already deployed. Concurrently, the provider rolled out Smart Assist, a native in-product companion that utilizes the exact same continuous data models to surface actionable insights directly inside the Smartsheet interface.

Unifying Distributed Corporate Strategy with Actionable Context

Unlike basic, isolated API integrations that offer simple read-only access without an underlying understanding of corporate workflows, Smartsheet’s MCP architecture links intelligent assistants directly to live data. Grounded in 20 years of rich enterprise performance metrics, the server translates complex, multi-tiered project dependencies, row histories, and cross-functional communications into structured, clear instructions that external algorithms can process accurately. This removes the reliance on generic textual summaries, enabling corporate AI instances to generate real-world, actionable solutions.

“The problem most teams run into isn’t access to AI. It’s that their AI has no idea how their organization actually works,” said Pratima Arora, chief product and technology officer at Smartsheet. “Today’s assistants make one person faster inside one system. But enterprises don’t deliver that way — the build, the launch, the transformation run across teams and systems all at once. That context lives in Smartsheet because that’s where the work happens. When every major AI assistant connects to it, teams stop chasing information and start making decisions.”

Also Read: Cognizant and Snowflake to Drive Enterprise AI Adoption via Cortex-Powered Intelligent Agents

Escalating Enterprise Market Momentum and Tool Utilization

The introduction of the multi-assistant model arrives amid unprecedented customer adoption following the initial rollout of Smartsheet’s MCP server earlier this year. Corporate performance analytics demonstrate that introducing an open, protocol-based layer successfully shifts artificial intelligence from a passive conversational novelty into active operational plumbing.

Key adoption and performance metrics recorded since the platform’s initial compliance launch include:

• Substantial Transaction Volumes: Over 22,000 unique corporate users have executed more than 3 million distinct AI actions within the ecosystem.

• Accelerated User Growth: Weekly active adoption has grown nearly 9x since week one, expanding from fewer than 1,000 active users at launch to more than 9,000, while overall weekly tool call volumes jumped from 42,000 to more than 700,000.

• Consecutive Record Invocations: The first 10 days of June alone yielded more than 860,000 AI actions, achieving consecutive all-time daily usage peaks on June 9 and June 10 with 1,767 and 1,825 active organizations, respectively.

• Measurable Productivity Shifts: Nearly one in three AI-driven queries explicitly creates, updates, or modifies live operational records, illustrating that connected workflows generate concrete business outcomes rather than simple text outputs.

• Rapid Ecosystem Scaling: Approximately 3,000 net-new organizations integrated the technology into their workflows over the last 30 days, averaging close to 700 new corporate teams connecting to the server each week.

“We specialize in complex, technical construction projects—from building large-scale data centers to state-of-the-art healthcare facilities,” said Matthew Feagin, regional operations leader at DPR Construction. “There are thousands of people involved in these projects, and Smartsheet is the backbone for managing all of the most dynamic parts of the process. Now with the Smartsheet MCP Server, our teams can securely connect to their preferred AI tools to quickly build workflows, test ideas and get answers using natural language, all in a fraction of the time. That means our frontline workers can easily create Smartsheet solutions tailored to their unique challenges, helping them solve problems faster and reduce errors.”

Maintaining Security Governance Over Fragmented Tech Stacks

By exposing a single, securely governed data-sharing layer through the Model Context Protocol, Smartsheet provides internal IT departments with a clear blueprint to mitigate the risks associated with “shadow AI” and fragmented corporate software stacks. The system honors all existing, organization-level authorization rules and user permissions, ensuring that automated agents operate strictly within verified, least-privilege guardrails. Additionally, every interactive data request and tool call is fully logged, providing corporate security teams with the transparent audit trails required to maintain regulatory compliance at scale.

The Copilot and ChatGPT connectors are commercially available to United States enterprise accounts immediately, with regional rollouts across Europe, the Middle East, Africa (EMEA), and Asia-Pacific (APJ) scheduled to launch in subsequent product phases. Global corporate networks can access technical documentation, connection maps, and implementation guides via the official Smartsheet developer platform.

The post Smartsheet Expands MCP Server Integration to Support Copilot, ChatGPT, and Gemini Enterprise appeared first on ITDigest.

Also Read: Pega and AWS Partner to Fast-Track Mainframe-to-Cloud Modernization via Generative AI

The hybrid model spans fixed and variable components across subscription, managed-service, and factory delivery frameworks, making it natively compatible with Agentic Engineering, Business AI Transformation, and Application Development & Maintenance (ADM) environments. Underscoring the operational philosophy behind this strategic deployment, Venu Lambu, CEO and Managing Director of LTM, stated: “Enterprises are increasingly looking to align technology investments more closely with measurable business outcomes. BlueVerse Currency brings together talent, platforms, and intelligent agents into a unified commercial model enabling clients to move from input-based constructs to outcome-led value creation, while scaling AI adoption with greater flexibility and transparency.” Ultimately, backed by rigid enterprise security, data governance, and responsible AI guardrails, this formalized solution eliminates wasted technology spend, allowing regulated enterprises to smoothly evolve into scalable, high-performing agentic operations.

Read More: LTM Introduces BlueVerse Currency to Enable Outcome-Based Pricing in the Agentic AI Era

The post LTM Launches BlueVerse Currency to Pioneer Outcome-Based Pricing for Agentic AI appeared first on ITDigest.

Also Read: Hivelocity Launches Bare Metal Cloud Suite to Deliver Predictable Cloud Economics

This automated lifecycle significantly compresses digital transformation timelines, allowing enterprises to rapidly replace decades of technical debt with agile, governed agentic workflows. Emphasizing the operational philosophy driving this collaboration, John Higgins, chief of client and partner success at Pega, stated: “Modernizing core systems isn’t just about moving old code to the cloud – it’s about reimagining how work gets done. By embedding Pega Blueprint AI directly into the time-tested AWS Transform analysis capability, we’re removing friction from the most painful stages of modernization and helping enterprises finally move from legacy COBOL to intelligent, cloud‑ready applications faster and with greater confidence.” Currently available within the AWS Transform platform at no additional cost to existing clients, this joint capability bridges the gap between infrastructure legacy dependencies and the modern requirements of scalable corporate automation.

Read More: Pega Launches AI-Driven Modernization Capability on AWS To Reimagine Legacy Mainframe Apps Into Cloud-Native Systems

The post Pega and AWS Partner to Fast-Track Mainframe-to-Cloud Modernization via Generative AI appeared first on ITDigest.

Also Read: Bitwise and HoneyHive Partner to Advance Governed and Scalable Enterprise AI

This allows organizations to establish a unified platform built for API, AI, event, and agent connectivity while maintaining strict cost and security controls. Explaining the operational necessity of this new offering, Reza Shafii, SVP of Product, Kong, stated: “Every enterprise software vendor is racing to make their platforms accessible to AI agents. The challenge for most organizations is that the APIs powering their business were never designed to be discovered, governed, secured, and consumed by agents. Kong gives customers the platform they need to make their APIs agent-ready, and Ascent dramatically accelerates the journey.” Currently available for migrations from MuleSoft® environments with more platforms to follow, Kong Ascent provides enterprises with the foundational agility needed to confidently scale agentic AI workflows.

Read More: Kong Launches Ascent to Eliminate Legacy API Migration Risk and Help Enterprises Get Agentic AI-Ready

The post Kong Launches Ascent to Accelerate Legacy API Migrations for the Agentic AI Era appeared first on ITDigest.