Databricks
Databricks Unity AI Gateway hits GA: a governance guide
Unity AI Gateway is now GA, bringing centralized AI traffic control, provider routing, MCP governance, and cost monitoring under Unity Catalog.
#governance
9 stories tagged governance.
Snowflake
Cortex AI Gateway: Snowflake's agent governance layer
Cortex AI Gateway is Snowflake's centralized control plane for AI agent access and cost. It governs 100+ MCP servers, but most features are in private preview.
Snowflake
Snowflake tag-based data protection policies: a governance shift
Snowflake tag-based data protection policies entered public preview on July 21, 2026, letting you attach row access, aggregation, projection, and join policies to tags. Objects with the tag auto-inherit the policy, cutting policy attachments from thousands to one per group.
Snowflake
Snowflake workload identity federation kills static credentials
Snowflake workload identity federation is now GA, letting Snowflake act as an OIDC provider so workloads authenticate to external services with short-lived tokens instead of static credentials. It costs zero additional credits and eliminates credential rotation for outbound API calls.
Databricks
Databricks Lakeflow Designer GA cost guide for teams
Databricks Lakeflow Designer is GA for visual, governed data prep. Use it for analyst-built transforms, but meter previews and jobs.
AI
Multi-agent safety gets Google’s $10 million test
Multi-agent safety is the problem of keeping interacting AI agents from amplifying failure. Google’s $10 million bet starts small.
Matillion
Matillion Context Engine: setup, limits, and costs
Matillion Context Engine is a public preview knowledge graph for Maia AI Agents. Start with restricted domain graphs and watch crawler scope.
Matillion
Matillion Context Engine grounds Maia agent work
Matillion Context Engine is a public preview metadata layer that gives Maia AI Agents knowledge graphs for safer pipeline work.
Snowflake
Snowflake RBAC and masking: lock it down without grinding to a halt
Snowflake access control is role-based: privileges attach to roles, not users. Splitting access roles from functional roles collapses thousands of direct grants to a few hundred, and one masking policy can protect thousands of columns at query time.