BigQuery vs Auth0
Side-by-side trajectory, velocity, and editorial themes.
BigQuery doubles down on Iceberg, graph, and global data sharing as the lakehouse fight intensifies.
BigQuery's May 2026 ship list is dominated by three tracks: open-format lakehouse integration (Iceberg v3 with deletion vectors, REST catalog support in Conversational Analytics), graph capabilities maturing inside BigQuery Studio, and global data exchange via multi-region sharing listings reaching GA. Alongside the feature work, Google is tightening Data Transfer Service security (MFA on Google Ads transfers) and warning about Ads retention changes that will cap historical backfills from June 1. The release notes show a mature warehouse continuing to absorb adjacent workloads rather than reinventing itself.
BigQuery is positioning itself as the federated query and sharing fabric for a multi-format world, with Iceberg getting closer to first-class status and Conversational Analytics extending across external catalogs. The graph and notebook work signals a push to keep more analytical work inside Studio instead of bouncing to specialized tools. Expect continued layering of governance, AI-assisted query, and open-table support on top of the existing engine rather than core engine reinvention.
Next obvious step is GA for Iceberg v3 features and full conversational graph querying without Preview gating. Watch for additional first-party data sources getting MFA mandates, mirroring the Google Ads tightening.
Auth0 ships Auth for MCP GA and starts unbundling the rest of identity for AI agents.
Auth0 just made Auth for MCP generally available — a bundle of CIMD client registration, On-Behalf-Of token exchange, and OAuth resource-parameter compatibility purpose-built for AI agents talking to MCP servers. Around it, the team is reworking core identity primitives: non-unique emails reached GA, online refresh tokens entered beta with session binding, and the Account API now supports step-up auth for sensitive scopes. Smaller polish items (CMD+K palette, Resend GA, signing algorithm coverage) round out the release stream.
Auth0 is repositioning from a B2C/B2B login provider to an authorization layer for agent ecosystems. The MCP work is the centerpiece, but the supporting moves — session-bound refresh tokens, step-up auth on the Account API, non-unique emails — all point at use cases where users, agents, and resources have more complex relationships than classic OIDC was designed for. Outbound event streams to AWS EventBridge and Okta Workflows extend the same direction outward.
Expect Auth for MCP to gain a managed catalog of pre-vetted MCP clients and deeper Actions-based policy hooks for OBO token exchange, plus online refresh tokens reaching GA within a quarter.
See more alternatives to BigQuery →
See more alternatives to Auth0 →