In brief
On August 24, 2026, the era of automic.com will come to an end. Broadcom is migrating central Automic resources such as documentation, downloads, Marketplace content and the Docker Registry to new platforms under broadcom.com.
This does not mean that Automic content will simply disappear. Many resources will remain available, but familiar URLs, access paths and established workflows are changing. For Automic admins, operators, support teams and everyone maintaining internal documentation or automations, this is an important topic.
Because the important question is not only: “Where do I find the new documentation?”
It is also: “Where have we built in old automic.com links over the years?”
What exactly is happening?
Broadcom is bringing the existing Automic platforms more closely into the central Broadcom platforms. From a user perspective, this mainly affects the following areas:
| Area | Previously | New |
|---|---|---|
| Automic documentation | docs.pemautomic.com | Broadcom TechDocs |
| Product downloads | downloads.automic.com | Broadcom Support Portal |
| Marketplace content | marketplace.automic.com | Broadcom Support Portal |
| Docker Registry | gcr.io | packages.broadcom.com |
| Support and central information | various Automic portals | Broadcom Support Portal |
The reasoning behind this is understandable: Broadcom wants to provide product resources in a more centralized way. For new users, this may even make things clearer in the long term. For existing Automic environments, however, it first means migration work.
Why is this important?
In many companies, Automic links have grown over many years. They are not only stored as browser bookmarks, but often also appear in internal wikis, operations manuals, installation guides, onboarding documents, training materials, scripts or automated download processes.
That is exactly why the shutdown of automic.com may have more impact than you might expect at first glance.
Typical examples:
- An operator opens an old documentation link from an internal wiki.
- An admin follows an installation guide with a download link pointing to downloads.automic.com.
- A script still uses the Download REST API.
- A Kubernetes setup refers to the previous Docker Registry.
- AWI help links still point to old documentation paths.
- A team searches for a Marketplace package in the place where it used to be for years.
All of this may work differently after the migration, or may no longer work directly at all.
What changes for the documentation?
The Automic product documentation is moving to Broadcom TechDocs. In principle, this is a positive step because the documentation becomes part of Broadcom’s central documentation landscape.
However, one thing is important: Old links to individual documentation pages will likely not always redirect directly to the exact matching new subpage. In many cases, you may end up on a higher-level product or version page and need to search for the relevant section again.
In everyday work, this is especially relevant if you frequently link to specific documentation pages, for example in:
- internal wikis
- operations documentation
- SOPs
- runbooks
- training materials
- tickets and knowledge base articles
- code comments or script documentation
Our recommendation: Do not only check your most important documentation links. Prioritize the links that are actually used in day-to-day operations.
What changes for downloads and Marketplace content?
Software downloads, integrations, Action Packs, agents and other extensions will be provided through the Broadcom Support Portal in the future.
This means that access will depend more heavily than before on your Broadcom account, permissions and assignment to the relevant organization. If you already work smoothly with the Broadcom Support Portal today, you will probably have less effort. If you have mainly used the familiar Automic download pages so far, you should test access early.
Especially important:
- Can all relevant admins access the required products?
- Are Support Site IDs and permissions configured correctly?
- Can the required versions and components be found?
- Are internal download guides still valid?
- Were old Marketplace links used in documentation or training materials?
If you use Marketplace content for integrations, plugins or agents, you should also check where this content will be located in the future and how it can be downloaded.
What changes for Docker images?
For container and Kubernetes scenarios, the Docker Registry is particularly important. The previous registry under gcr.io is being replaced by packages.broadcom.com.
This especially affects teams working with Automic Automation Kubernetes Edition or teams that have built their own Helm charts, deployments or internal mirroring processes.
Pay particular attention to the following:
- Do Helm charts still point to old registry paths?
- Do image pull secrets or tokens need to be adjusted?
- Are registry tokens for packages.broadcom.com available?
- Are there internal mirror registries that need to be updated?
- Are build and deployment pipelines affected?
For container setups, early testing is especially worthwhile. An incorrect registry path or missing token often only becomes visible when a deployment actually needs to run.
Which functions will be discontinued or change significantly?
In addition to the obvious URL changes, there are also some functional changes that admins should be aware of.
The following are particularly relevant:
The Download REST API will be discontinued
If you have implemented automated downloads via the previous Download REST API, you should review these processes. According to Broadcom, this API will be discontinued without a direct replacement.
This may affect:
- automated installation processes
- internal update pipelines
- scripts for component downloads
- documented standard processes for new environments
The Automic Package Manager can no longer install packages directly
The Package Manager is affected as well. If you have previously used direct installations or package retrieval through existing mechanisms, you should test what your future workflows should look like.
Some legacy tools will be replaced or discontinued
Some older tools and overviews will not be continued one-to-one. These include functions related to release notes, the compatibility matrix, the component support lifecycle and other helper areas.
This does not automatically mean that all information will disappear. In some cases, content will be integrated into other areas. In other cases, the previous direct access will no longer be available.
What does this mean for AWI help links?
One point that is often overlooked: Links from the Automic Web Interface to the product documentation may also be affected.
If your AWI environment is configured so that help links point to the old documentation, you should check whether these links need to be updated to the new Broadcom TechDocs URLs.
This is not a dramatic issue, but it is a typical admin topic that is easy to forget. And at some point, someone clicks “Help” and does not land where they should.
What should I do now?
Here is a pragmatic checklist for Automic admins and operators:
1. Check internal links
Search for old links to:
- automic.com
- docs.pemautomic.com
- downloads.automic.com
- marketplace.automic.com
- gcr.io Automic paths
Typical places include wikis, runbooks, operations manuals, training materials, installation guides and knowledge base articles.
2. Test download processes
Sign in to the Broadcom Support Portal and check whether you can find the required Automic products, versions, components and extensions.
It is not enough that one person has access. What matters is that the right people in operations have access.
3. Review automations
If you have automated downloads, installations or updates, review the technical dependencies.
The following are especially critical:
- REST API access
- hard-coded download URLs
- scripts with old paths
- CI/CD jobs
- internal installation helpers
- containers and Helm deployments
4. Update the Docker Registry
If you pull Automic images from a registry, plan the switch to packages.broadcom.com. Check tokens, secrets, Helm charts and internal documentation.
5. Update documentation
Do not replace old links blindly. Check whether the new target page really matches the old information. Especially with deep documentation links, the new structure may look different.
6. Inform your teams
Admins are not the only ones affected. Operators, support staff, developers and external service providers may also access old links regularly.
A short internal note can help avoid many unnecessary questions later.
What does this mean for PEM Automic?
We are also looking closely at this topic. Especially on a learning platform, links to official documentation, downloads and technical references are naturally very important.
That is why we are checking which content is affected and where updates are required. At the same time, we have created a compact overview for PEM Automic members that summarizes the most important changes and impacts.
➡️ Go to the PEM Automic article:
automic.com is shutting down – here’s what you need to know now
You should also keep an eye on the official Broadcom notification, as Broadcom says it will continue to be updated:
➡️ Official Broadcom Migration Notification:
Important Update: Migration of automic.com Digital Platforms
Conclusion
The shutdown of automic.com is not a catastrophe, but it is not just a cosmetic change either.
For many teams, little will change in everyday work as long as they only search for documentation occasionally. For admins, operators and companies with mature Automic processes, however, the migration can have very real effects.
The most important recommendation is therefore: Do not wait until old links no longer work.
Check your documentation, download processes, scripts, registry access and internal guides now. This ensures that your team can still quickly find what it needs after the migration.