This week, we're excited to unveil a major infrastructure upgrade with the launch of our new connections model. For a full list of recent changes, read our 2026 changelog.

🔗 Connections make credential management easier than ever

We've launched a new connections model that replaces the existing split between Secret definitions, OAuth, and cloud credentials. Instead of storing just the sensitive part of a credential, a connection stores the whole thing: URL, username, and secrets as a single reusable object.

This means:

• Reusability and portability: change a connection once, and it updates everywhere it's referenced
• Environment-specific properties: vary connection properties by environment without using project variables
• Consolidated management: Secret definitions, OAuth, and cloud credentials are now managed from a single Connections tab

We've also shipped the ability to create any type of connection—new or legacy—inline in Designer, so you can add your credentials without leaving your pipeline.

Important info:

• Gradual rollout: not every component supports the new model on day one. Support is being added component by component. Components that have been updated show a Connection field in their config panel.
• Existing pipelines keep running: your published pipelines will continue to run as normal. The next time you open a pipeline in Designer, upgraded components are automatically backfilled with the [Legacy connection] option so they keep working when you next publish.
• No forced migration: if a component supports the new model but you'd rather use your existing credentials, just select [Legacy connection] from the dropdown.

Read the full documentation for complete details on what's changed and frequently asked questions.

This week, we're excited to bring you powerful updates that enhance your control and efficiency within Maia. From improved Designer functionality to smarter task management in Mission Control, these features are designed to streamline your workflows and give you more precision in how you work. Check out the changelog updates for full details.

⏪ Undo and redo improvements in Designer

You can now undo and redo changes from any panel in Designer, with no risk of confusion between undoing work on the canvas or in a panel. In addition, pipeline validation no longer re-runs after you undo cosmetic-only changes, such as moving a component or editing a note.

This means you can confidently undo from anywhere in Designer—the variables panel, component properties panel, or the canvas—without needing to refocus. Skipping validation when you undo a minor change saves unnecessary processing time and lets you continue building pipelines efficiently.

🚩 Task priorities in Mission Control

You can now set a priority level for each Mission Control task—High, Medium, or Low—to control the order in which Maia Team works on them.

When you queue up a backlog of work, not everything is equally urgent. Use task priorities to tell Maia Team what matters most, so your important tasks are always picked up first.

What's new:

• Set a priority level: Choose High, Medium, or Low priority when creating or editing a task.
• Smarter backlog ordering: Tasks in your backlog are automatically worked on by priority, highest first. When priorities match, the oldest task goes first—so nothing gets buried.
• Filter by priority: Use the filters on the Mission Control board to focus on just High, Medium, or Low priority tasks.

Read the Auto-start section of our Mission Control documentation to learn more about task priorities, or check out our guide to Tasks in Mission Control to find out how to set a task’s priority level.

💬 We'd love to hear from you!

Let us know how these new features are improving your workflows—we're all ears! Feel free to add any comments or questions below.

Welcome back to the Maia New Features Blog! This week, we're excited to introduce the Upgrade Assistant, a powerful new tool designed to streamline your migration experience and make transitioning to Maia smoother than ever.

✨ Migrate to Maia with our new Upgrade Assistant

We're excited to announce the Upgrade Assistant, a powerful new tool within Maia that simplifies and streamlines the migration of Matillion ETL workloads.

This new feature lets you connect Maia directly to your existing Matillion ETL instances, which makes it easier and quicker to migrate your workloads to Maia. With the Upgrade Assistant, you can:

• Migrate schedules, jobs, secret references, shared jobs, API Extract profiles and API Query profiles
• Configure advanced import options, including migrating Python workloads to Script Pushdown components
• Create custom connectors automatically from API Extract profiles
• Migrate shared jobs without needing to create custom mapping documents

Ready to get started? Check out the Upgrade Assistant documentation!

💬 We'd love to hear from you!

Let us know how these new features are improving your workflows—we're all ears! Feel free to add any comments or questions below.

Welcome back to the Maia New Features Blog! This week, we're excited to introduce Impact Stream, a game-changing feature that transforms how you handle pipeline failures by automatically surfacing downstream dependencies right when you need them most.

🔍 Trace dependencies in seconds with Impact Stream

When a pipeline fails, there’s always one question that your engineers need to answer: What else is affected? Until now, answering that required previous tribal knowledge or manual review—locating the failed dataset and tracing dependencies by hand.

Impact Stream solves this problem. It surfaces downstream dependency information automatically at the moment of a pipeline failure, with no manual lineage navigation required. It’s made up of two parts:

• Pipeline tree: The pipeline tree on the left shows the hierarchy of pipelines involved in the run, starting from the root pipeline. Each node displays the orchestration or transformation pipeline’s name, its environment, and a colored dot indicating its status.
• Impact Stream canvas: When lineage is available, the Impact Stream canvas shows how datasets and pipelines connect to one another, with arrows showing the direction of data flow. Each node is outlined in a color indicating its status:
  • 🔴 Failed:The pipeline or dataset encountered an error
  • 🟡 Potentially affected: The pipeline or dataset is downstream of the failure and may be affected, but wasn't directly executed
  • ⚪ Unaffected: The pipeline or dataset has no dependency relationship with the failure
  • 🟢 Success: The pipeline or dataset was processed without error
  • Not executed: The pipeline or dataset didn't run as part of this execution

To access a failed pipeline’s impact stream, in the left navigation, click Activity, then Pipeline runs. Click the target icon next to any failed run to view its impact stream.

It’s important to note that Impact Stream isn't a replacement for Lineage. Lineage is your always-on, comprehensive dependency map. Impact Stream is a run-specific, on-demand triage view, scoped to a single failure, generated instantly.

For more information, read our Impact Stream guide.

💬 We'd Love to Hear From You!

Let us know how these new features are improving your workflows—we're all ears! Feel free to add any comments or questions below.

‍

This week, we're focusing on making your Maia experience smoother and more efficient. We've introduced a major performance upgrade for Designer, streamlined selecting items when configuring components, and added new connectors to expand your data loading capabilities. Check out the changelog updates for all the details.

🎨 Mission Control gets a new look

You can now switch between two views in Mission Control: the classic Kanban view and our new List view.

List view is designed to help you keep track of your work when you’re juggling a lot of Mission Control tasks, by highlighting tasks that need your attention. Whenever Maia Team needs your help or asks you to review a completed task, these tasks are stacked at the top of the new view by default.

Use the view toggle in the top right of your Mission Control board to switch between List view and Kanban view. Maia remembers your choice, so your Mission Control board will always open to your most recently selected view.

One more update—it’s now super easy to rename Mission Control tasks to help you keep track of the work being done in each task.

Keen to get started? Check out the Mission Control documentation.

⏩ Designer performance improvements

The pipeline canvas now runs up to 14× faster, with a particular impact on Windows enterprise hardware, giving you a noticeably smoother experience when you're moving items around the canvas, updating pipelines, and browsing files in large projects.

🎯 Configure components without losing sight of your work

Every dual listbox style component property has been upgraded. The new design of these properties lets you select one or more items from a list in the component properties panel, without a dialog blocking your view of the canvas.

As a result, you never lose sight of your pipeline and other Designer elements, such as the Maia Team chat panel and Variables tab, when configuring components. This gives you a fully in-context, uninterrupted configuration experience.

🔌 New connectors

We’ve released the following new connectors this week, making it easier than ever to bring data from these sources into your Maia projects.

For all projects:

• Google Analytics

For Snowflake and Google BigQuery projects:

• Amazon DynamoDB Load
• Bing Ads Load
• ElasticSearch Load
• Excel Load
• Facebook Ads
• SharePoint Load
• Stripe Load
• Zoho CRM Load

Click the name of a connector in the list above to learn more about each one!

💬 We'd Love to Hear From You!

Let us know how these new features are improving your workflows—we're all ears! Feel free to add any comments or questions below.

This week, we're bringing you powerful new capabilities that enhance flexibility and streamline your workflows in Maia. From dedicated script runners to seamless repository migrations and improved pipeline management, these updates are designed to make your data operations more efficient and adaptable. For a full list of recent changes, check our changelog updates.

💻 Script Pushdown component and runner

We're excited to announce an upgrade that allows you to run Python and Bash scripts in a dedicated runner when using a Hybrid SaaS deployment.

This new feature provides allows you to:

• Have a dedicated script runner that is scaled appropriately for these workloads, keeping your Maia runner scaled for average task loads.
• Deploy this script runner as part of your Maia runner deployment.
• Use your existing process to load libraries.
• Migrate large script workloads from Matillion ETL when upgrading to Maia without adjusting for runner architecture.

As part of this change, we've also introduced sizing options for both script runners and Maia runners.

The Script Pushdown component supersedes the Bash Pushdown component. The Python Script and Python Pushdown components are not affected. Python Script can still be used for smaller workloads that do not impact your Maia runner, and Python Pushdown is still used for Full SaaS deployments.

Read the Script Pushdown component guide to learn more.

🔄 Migrate your project’s repository using our API

The new Migrate Repository API endpoints gives you more flexibility than ever. You can now change the repository that your Maia project is based on.

Whether you’ve department switched Git providers or you need to move away from a hosted repository, the Maia API supports migrations from hosted Git to GitHub, GitLab, and Azure, as well as between GitHub, GitLab, and Azure providers. This means you can adapt to organizational changes without losing your project progress or having to start from scratch.

Read our Repository Migration API guide to get started.

✍️ Automatically update pipeline references

When renaming a pipeline in Designer, you can now ask Maia to update all references to the renamed pipeline in other pipelines in your project—for example, if you rename an orchestration pipeline that’s referred to in a Run Orchestration component in another pipeline.

This update streamlines project management by automatically updating all pipeline references, eliminating the need to manually track down and update these references, saving time, and reducing the risk of broken links when reorganizing your pipelines.

💬 We'd love to hear from you!

Let us know how these new features are improving your workflows—we're all ears! Feel free to add any comments or questions below.

‍