If you are responsible for keeping software delivery moving, more ecosystems usually mean more overhead.

More package types can turn into more tools to manage, more one-off workflows, and more chances for things to slow down or fall out of policy. At the start of 2026, Sonatype Nexus Repository moved in the opposite direction: expanding support for Terraform and Swift while also making the platform easier to run, automate, and trust.

The result is not just broader format support. It is a more practical way for development, DevOps, and IT teams to centralize software components, reduce tool sprawl, and keep work moving across a growing mix of languages, packages, and infrastructure artifacts.

More Format Support With a Clear Payoff for Users

One of the biggest themes at the start of the year was broader format support, especially for teams working in infrastructure as code and the Apple ecosystem.

Terraform Support

With support for Terraform, teams can manage more of their infrastructure artifacts through Nexus Repository instead of handling them through separate, disconnected workflows. That means a more consistent way to access providers and modules, better performance through caching, and stronger control over both internal and external Terraform dependencies.

For DevOps and platform teams, that is especially useful. Infrastructure artifacts no longer have to live off to the side with their own process and tooling. They can be managed with the same level of control, visibility, and consistency as the rest of the software supply chain.

Swift Support

Support for Swift brings the same kind of simplification to teams building for Apple platforms. With Swift packages now supported in Nexus Repository, teams can centralize dependencies, improve build performance, reduce reliance on external Git hosting, and create a cleaner way to manage internal Swift packages alongside approved third-party components.

For development teams, that means less friction in the toolchain. For IT and platform teams, it means fewer exceptions to support and a more consistent way to manage another important ecosystem.

What makes both of these additions valuable is not just that Terraform and Swift are now supported. It is that teams can manage more of their software and infrastructure dependencies in one place instead of stitching together separate workflows for different ecosystems. That leads to a smoother experience for developers and a more scalable operating model for the teams responsible for control, governance, and reliability.

A Better Path Off OrientDB and Into Modern Deployments

Another important update is the new Instance Migrator, which gives customers on OrientDB-based deployments a simpler path to PostgreSQL, H2, or to Nexus Repository Cloud.

That matters because 3.70.x was the last release to use OrientDB, and as of January 9, 2026, support for OrientDB is officially sunset. Older OrientDB-era deployments carry increasing security that have been addressed in newer releases, so for teams still on those versions, this creates a clearer way to move off legacy infrastructure and onto a more modern platform with better performance, security, and manageability.

For teams that have been putting off modernization because migration felt like too much work or too much risk, this is the kind of improvement that can make the next step a lot more practical.

The Platform Got Stronger Too

The start of the year was not only about supporting more formats. It was also about making Nexus Repository easier to operate day to day.

Reduced Operational Complexity

One of the biggest platform-level changes was the move from Elasticsearch to SQL for search. Search now runs directly against the configured database, which reduces deployment complexity and cuts down on moving parts while preserving the search experience teams already know.

This is the kind of change that makes life easier for the people running the platform. Less infrastructure to maintain usually means less operational overhead and fewer things to troubleshoot.

Better APIs and Automation for Teams

There were also useful improvements for teams building automation around Nexus Repository. A new Capabilities API endpoint makes it easier to retrieve capability types and metadata programmatically. Improvements to browse tree cleanup give administrators more control after component deletion. And the new User Token API adds more precise, programmatic control over token creation and management.

For teams trying to automate routine administration and tighten up how credentials are managed, these are practical improvements that save time and reduce manual effort.

Strengthened Security and Operational Resilience

On the security and resilience side, the updates were less flashy but still important. URL validation helps protect against SSRF by blocking outbound connections to private network addresses, localhost, and cloud metadata endpoints. Recovery Mode adds a controlled state for safe reconciliation between the database and blob storage after outages or inconsistencies.

These are the kinds of improvements that matter most when something goes wrong. They help make the platform safer to operate and easier to recover.

A Faster, More Transparent User Experience

The user experience got better too. Faster page loads, lower bandwidth usage, and improved caching efficiency make Nexus Repository feel more responsive in everyday use. There were also improvements to policy-compliant component selection in npm metadata, making it easier for users to understand why a version is unavailable and what they can use instead.

That kind of clarity matters. It removes guesswork and helps teams move faster without having to stop and investigate every policy decision by hand.

A Strong Start to the Year

The start of the year sets the tone for where Nexus Repository is headed: helping more teams bring more of their workflows into a centralized, governed system while continuing to improve the experience of running and managing it.

That means broader ecosystem support, a clearer path off legacy deployments, and ongoing improvements to performance, security, and operations. Taken together, it is a stronger foundation for teams that want more control without more complexity.