🔌 This Week in Maia: Connections

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.