Package your Applications and Components
Create any number of feeds to organize and distribute your packages to different groups or even to external customers.
Combine multiple feeds – both internal and external – with connectors so that consumers need only one feed and can access external packages even when the external feed is unavailable.
Avoid costly open-source license violations by defining licensing policies that ProGet will use to block non-compliant packages.
Scan packages for vulnerabilities and block access to those deemed too risky or unsafe based on rules you configure.
Promote packages between feeds to ensure that only approved and verified packages are used in the right environments, such as production.
Deploy your application and component packages to servers and the cloud by integrating BuildMaster’s reusable workflows that automate testing, deployments, and if necessary, rollback.
ProGet records deployments from other tools as well, including Otter, Octopus Deploy, or even your own custom scripts, so you can see which packages were deployed to which servers.
Use package statistics to see which users and servers are accessing which packages so you can make informed decisions on updating or retiring development libraries, scripts, or other types of packages.
Configure webhooks to trigger automatic deployments, alters, or even audit activity when packages are added, promoted, deployed, and deleted.
Add as many web server nodes as you need to load balance traffic from various teams and build servers around the world.
Leverage Amazon S3 or Azure Blob storage for inexpensive, pay-as-you-go scaling of your package file storage.
Replicate feeds among different ProGet instances across the globe to allow different teams to share feeds without setting up complicated, global infrastructure.
Use ProGet’s high availability mode to ensure there is no single point of failure, and that your packages can be accessed even if there’s a hardware failure.
Created exclusively for infrastructure automation and orchestration, the Inedo Execution Engine makes it easy to deploy and execute across hundreds of servers, and provides detailed logging (with sensitive debugging details hidden from certain users) to let you quickly identify what went wrong
A lightweight, highly-optimized agent that allows a server to be securely orchestrated by a connected Inedo product. It’s simple to deploy and upgrade, but is also backwards- and forwards-compatible to minimize change risks.
A lot of Inedo’s product functionality is delivered through extensions, and you can add or modify functionality and capabilities to our product by creating an extension. Because this is a shared SDK, you can write a component once and introduce the same functionality across all of our products