Systems | Development | Analytics | API | Testing

Like many other countries, India has made moves to protect consumers’ data. Comparable to the European Union’s General Data Protection Regulation (GDPR), India’s Digital Personal Data Protection (DPDP) Act establishes new, higher standards for data privacy, timely breach notification, and consent management.

You opened the AI assistant for the first time with a fair amount of hope. You typed "write test cases for the login page." You got eight test cases back in about three seconds. Valid login. Invalid password. Empty username. Empty password. The kind of list you could have written in your sleep, missing every scenario that actually matters for your product. So you closed the tool and thought: this is fine for the basics, but it does not really get testing. AI is overhated.

Most AI content assumes your data is in the cloud. But for a meaningful segment of enterprises, cloud-only AI tools block them at the pass. For regulated industries like manufacturing and healthcare, data residency requirements, compliance mandates, security policies, and simple operational reality mean sensitive data must remain on-premises.

In the first part of this series, I argued that discernment, the ability to recognise when an AI-generated answer is wrong, is becoming one of the most valuable capabilities inside an organisation. The question this piece addresses is simpler and harder: who is actually being given the opportunity to develop it? The AI opportunity gap is real. It is not primarily a gap in access to tools. It is a gap in permission. And I believe that gap starts earlier than most leaders realise, often in school.

If you've been following the agentic AI wave, you've probably noticed that the conversation tends to center on the agents themselves: which LLM to use, which orchestration framework to pick, which use cases to tackle first. But a growing body of analyst research is pointing to a different bottleneck, one that's hiding in plain sight: integration. Forrester's David Mooter argues that integration must sit at the center of your AI strategy — not as plumbing, but as a strategic capability.

*You wouldn't expose a REST API without a gateway. What about Kafka?* You would never expose a REST API without an API gateway in front of it. Authentication, rate limiting, observability, access control — these aren't optional extras. They're mandatory, and we've spent the last decade building the API gateway pattern to solve exactly this problem. So here's the question worth sitting with: would you expose Kafka or any event stream without a gateway?