🎉 What's new

Atlan Lakehouse just got faster, more data and more reliable. Anything you need out of Atlan, from AI usage data to asset metadata to full exports, is available from the same open, governed layer, and is performant enough to build any application on. 

📊 Track how your teams use Atlan's AI interfaces

Atlan offers several conversational AI interfaces, so your teams can work with their enterprise context layer from any tool they want, whether it's their own agentic tools via Atlan MCP, Slack and Teams, or Atlan's built-in Conversational AI chat. You can now easily track how your teams use those interfaces directly in your own Atlan Lakehouse with two new tables:

The USAGE_ANALYTICS namespace in your Lakehouse now has two AI usage tables, refreshed daily: AI_TOOL_CALLS (one row per tool call across all of Atlan's AI interfaces) and AI_TURNS (one row per user question in Conversational AI, Slack, and Teams). Both sit alongside the metadata and product usage data already in your Lakehouse.

• Identify active AI users: Count questions and tool calls, and see your most active AI users by joining the new AI usage tables with USAGE_ANALYTICS.USERS.
• See which tools and clients lead: Use the client_name column to see which clients your teams use (e.g., Claude, Cursor, Codex, VS Code), and the tool_name column to see which Atlan capabilities they call most.
• Measure conversation depth: Group AI_TURNS by conversation_id ordered by timestamp to separate new questions from follow-ups, and understand how your teams' conversations evolve.
  
• Find friction fast: Use the is_error and duration_ms fields to see where AI calls fail or make people wait.

📊 Meanwhile, your asset exports just got dramatically faster

All asset export workflows (advanced, basic, admin) now run on a shared backend built on Atlan Lakehouse. It’s same UI, same configuration, same output but built on a faster, more scalable foundation. Exports that used to take more than a day now complete in less than half an hour, moving over a million assets. The switchover is behind the scenes – no changes needed from you.

👏 Get all the benefits of Atlan Lakehouse today

Atlan Lakehouse is generally available for all Atlan tenants.

• Use any engine: Pick up configuration details from Admin/Settings → Lakehouse (admin users only), and point any Iceberg REST-compatible engine at it, e.g., Snowflake, Trino, DuckDB.
• Use any AI tool: Install the /atlan-lakehouse skill to your favorite AI tool (e.g., Claude Code) and use natural language to ask any questions about your Atlan asset metadata and usage data – no query engine required.

And what might you want to access?

• Usage analytics: The USAGE_ANALYTICS namespace exposes page views, user actions, and adoption data you can analyze directly, with MCP and conversational AI logs now available.
• Relationship analytics: Metadata for all of your Atlan assets are in the Lakehouse, including user-defined relationships with full edge semantics, meaning your business-graph relationships are queryable for both your AI agents and analytical use cases, not just linked-asset lookups.

💥  More on the way!

Lakehouse already works with engines such as Snowflake, Databricks, BigQuery, Trino, and DuckDB. We're also building Atlan-managed Lakehouse Compute for when you want to query your data without running the compute layer yourself. More details to come!

🎉 What’s new

The Atlan MCP Server is a powerful way to bring AI into your metadata workflows (such as managing your assets or glossaries), without sacrificing control or context.

With this update, you can use our remote MCP servers instantly in your IDE (think Cursor or Windsurf) or AI workflow tool of choice (like Claude or n8n) with no local overhead and authentication managed securely via Atlan.

✨ Let’s dig deeper

Here’s what this means for you in practice:

• Connect your IDEs or AI workflow tools to a remote MCP server using just the server’s URL and credentials
• Manage access with OAuth (SSO) or API keys
• Use MCP powered capabilities inside tools like Claude, n8n, Microsoft Copilot Studio, Windsurf, or Cursor without local setup
• Switch between multiple servers easily, helpful for dev, staging, and production environments
• Collaborate seamlessly, since teammates can connect to the same remote MCP without replicating installs
• Keep your local machine clean while still tapping into full MCP functionality

👏 Give it a shot

Read the setup guide for step-by-step instructions.

And be on the lookout for what's next with Atlan's MCP, from new actions to integrations with Slack, Teams and beyond

🎉 What's new

This one's for our Python developers — announcing the initial release of our Python SDK! The Python SDK allows you to integrate with and automate actions in Atlan using all the features you know and love in your favorite IDE — type-ahead coding support, debugging, dependency management, version control, and so on.

✨ Let's dig deeper

Our SDKs abstract the need for you to understand all the underlying details of our REST APIs — their payload formats, endpoints, the universe of possible fields, and so on.

Here are some cool things you can do:

• Write your metadata ingestion — for example, integrate a custom set of data quality metrics from a homegrown solution right into your metadata assets in Atlan.
• Code up a custom report combining complex search criteria and lineage navigation and filtering in just a few lines of code and a matter of minutes.
• Deploy an event-based integration that calculates new metrics or enforces the validity of a change any time metadata is changed in Atlan — whether by a user in the UI or through an out-of-the-box crawler or some other programmatic automation.

👏 Give it a shot

Get started with integrating and automating actions in Atlan with Python, available to include in your project today directly from PyPI!

Learn more here:

• Get started with the Python SDK
• Star the public GitHub repository
• Review useful code that already uses the Python SDK

🎉 What's new

This one's for our Java developers — announcing the initial release of our Java SDK! The Java SDK allows you to integrate with and automate actions in Atlan using all the features you know and love in your favorite IDE — type-ahead coding support, debugging, dependency management, version control, and so on.

✨ Let's dig deeper

Our SDKs abstract the need for you to understand all the underlying details of our REST APIs — their payload formats, endpoints, the universe of possible fields, and so on.

Here are some cool things you can do:

• Write your own metadata ingestion — for example, reading an OpenAPI spec and creating the relevant API objects in Atlan.
• Code up a duplicate detection algorithm to identify tables that appear to be duplicates of each other, even when the names of those tables and the ordering of their columns might differ.
• Deploy an event-based integration that calculates new metrics or enforces the validity of a change any time metadata is changed in Atlan — whether by a user in the UI or through an out-of-the-box crawler or some other programmatic automation.

👏 Give it a shot

Get started integrating and automating actions in Atlan through Java, available to include in your project today directly from Maven Central!

Learn more here:

• Get started with the Java SDK
• Star the public GitHub repository
• Review useful code that already uses the Java SDK