Discussion about this post

User's avatar
Neha Garg's avatar

100%. That's precisely also the reason we are building our solution to be on-prem based.

Israel Rosental's avatar

Great perspective. I’d add what I believe is a foundational architectural principle for AI platforms: AI applications should be designed across two distinct but connected domains:

service/agent domain

data domain.

They need to communicate constantly, but they should not be governed or protected in the same way.

In this model, AI doesn’t necessarily need broad access to raw enterprise data. It needs governed access to the context layer - metadata, semantic relationships, and retrieval paths - with a built-in security layer at that boundary.

The AI operates on the "map" of the data first; direct access to sensitive resources happens only after a filtered, policy-controlled request is validated.

This is why AI-native security must be a platform design principle, not just an infrastructure choice. The Service Domain handles orchestration and execution control, while the Data Domain handles sovereignty, lineage, and policy enforcement.

This separation is still under-discussed, yet it’s exactly how secure AI platforms move from risky experiments to core, sovereign business capabilities.

That is why the direction you’re taking with Cylake is so relevant.

3 more comments...

Ready for more?