Featured
Posted by
Crista Perlton on December 24th, 2025.
If you work with CI/CD pipelines, artifact repositories, or DevOps workflows, you’ll be familiar with Amazon S3. It’s flexible and widely used, but as your repository grows, costs can add up fast. Storage is just one piece of it; request charges and egress fees can catch teams off guard, especially when traffic spikes. As you...
Featured
Posted byCrista Perlton on December 11th, 2025.
If you’re managing projects that rely on multiple teams delivering consistent components, you’ve probably noticed the chaos that comes from storing build artifacts and libraries in shared folders. Each team has its own way of organizing files, versions get mixed up, and no one really knows which asset the project should be using....
Featured
Posted byCrista Perlton on December 9th, 2025.
You’re likely pulling OSS packages straight from NuGet.org, npmjs.com, or PyPI.org, via the CLI. It’s the path of least resistance and the fastest way to get what your teams need. But without something sitting in the middle, it’s hard to know exactly what’s being pulled in or whether it meets your org’s requirements. When you pull OSS...
Featured
Posted byCrista Perlton on December 4th, 2025.
Internal registries are a smart way to manage OSS packages. They let you curate reusable code for your apps and cut down on risky repeat pulls from the wild. But when every team spins up its own siloed registry and tooling sprawls across the org, you end up with duplicate work, outdated packages, and security headaches that didn’t need...
Featured
Posted byCrista Perlton on November 28th, 2025.
Inedo’s newest whitepaper, “Migrating from Sonatype to ProGet“ releases this month, available both as a free PDF eBook, or as a series of articles on our blog. Migrating from Sonatype Nexus to ProGet is more than just copying your packages over. Nexus spreads its features across different products—Repository, Lifecycle,...
Featured
Posted byCrista Perlton on November 25th, 2025.
Many teams pull open-source packages into their projects without thinking twice. They might stash them locally, pass them around through CI pipelines, or build and test on their own. But without internal repositories or any guardrails in place, each team ends up working in its own bubble. That kind of flexibility can feel great at first,...
Featured
Posted byCrista Perlton on November 11th, 2025.
Using GitHub Packages for internal package sharing is a common choice for many teams. Since it’s already part of the GitHub ecosystem, teams adopt it naturally, without spending much time looking over other options. Each project manages its own dependencies, and publishing or consuming internal libraries is relatively straightforward. On...
Featured
Posted byCrista Perlton on November 6th, 2025.
Cloud storage has become a go-to option for storing data. It’s generally reliable and designed to scale easily as needs grow. Having said that, it does come with its challenges. User interfaces often change as providers update their platforms, permission models tend to be complex, and managing cloud storage often demands a...
Featured
Posted byCrista Perlton on November 4th, 2025.
Many organizations think that letting independent development teams manage their own package workflows is efficient …but in practice, it’s not. Every team tends to develop “its own way” of versioning, approving, and documenting packages. One might use a NuGet Server, while another stores artifacts on a shared drive....
Crista Perlton on December 24th, 2025.