If you have any questions about Nexus please contact us. We have engineers (not just sales guys) ready to answer your questions.
Key Features
| OSS | Pro | |
|---|---|---|
| Technical support | No | Yes |
| Support you need from the experts who built Nexus. | ||
| Availability architecture | No | Yes |
| Avoid downtime by deploying Nexus in a highly available configuration without sacrificing performance. | ||
| Repository health awareness | No | Yes |
| Improve quality and avoid problematic components. See popularity, licensing and security data for every component. | ||
| Security reporting | No | Yes |
| Identify components with known security vulnerabilities. | ||
| License reporting | No | Yes |
| Identify all licenses associated with each component, including those listed in both the POM and sources. | ||
| Popularity reporting | No | Yes |
| Choose the best components by knowing which ones other developers are using. | ||
| Enhanced proxy | No | Yes |
| Deploy proxy repos for even the largest teams without sacrificing performance. Updates are now pushed from the master repository. | ||
| .NET package repository | No | Yes |
| Improve collaboration, share .NET components and standardize on a single repository manager. | ||
| Enterprise LDAP | No | Yes |
| LDAP authorization based on group, map Nexus roles for external users, mirror fall back support and intelligent authentication caching. Utilize user and group templates, test user login and get support for multiple servers and schema. | ||
| Atlassian Crowd integration | No | Yes |
| Integrate your existing single sign-on and identity management system. | ||
| Staging and build promotion | No | Yes |
| Improve your release process using staging repositories. Ensure builds meet your criteria before being promoted. | ||
| Component procurement | No | Yes |
| Control which components are allowed in the repository with white and black lists. | ||
| Collaboration | No | Yes |
| Improve your teamwork by hosting project websites on the Nexus server, and sharing Maven settings and archetypes with your team. | ||
| Enriched search | No | Yes |
| Search by custom metadata, browse archives and view component dependencies. | ||
| Maven settings templates | No | Yes |
| Standardize your Maven configuration by distributing Maven settings to developers. | ||
| Hosting project websites | No | Yes |
| Deploy your project’s website to the same infrastructure that hosts the project’s build output. | ||
| Add Maven archetypes | No | Yes |
| Share custom archetypes within in your organization to start up new projects quickly using a standard POM. | ||
| Control which components are allowed in the repository using white and black lists. | ||
| Automatic procurement on/off control | No | Yes |
| Ensure that updates to remote components are not downloaded unless you explicitly want them to be. | ||
| Component verification with PGP signatures | No | Yes |
| Validate that components come from a trusted developer. | ||
| Promotion rule sets | No | Yes |
| Ensure your development standards are met. Repositories are not promoted unless they meet all defined rules. | ||
| OSGi Bundle and P2 repositories | No | Yes |
| Proxy, host, and group OSGi and P2 repositories. | ||
| .NET package repository | No | Yes |
| Improve collaboration, share .NET components and standardize on a single repository manager. | ||
| Proxy .NET gallery | No | Yes |
| Provide local, controlled access to .NET open source components to reduce risk and speed development. | ||
| Deploy .NET packages | No | Yes |
| Add .NET packages to the repository using NuGet from within Microsoft Visual Studio or the command line interface. | ||
| Search by custom metadata | No | Yes |
| Find components that contain user defined custom metadata. | ||
| Archive browsing | No | Yes |
| Explore the contents of an archive stored in the repository. | ||
| View component dependencies | No | Yes |
| Display a component’s dependencies using metadata in the POM. | ||
| Self-service user registration | No | Yes |
| Allow anonymous users to sign-up for a Nexus account without administrative intervention. | ||
| CAPTCHA-protected user registration | No | Yes |
| Ensure that automated systems don’t create accounts when self-service registration is used. | ||
| Nexus configuration backup | No | Yes |
| Reduce risk by ensuring you always have a recent snapshot of your Nexus configuration. | ||
| Customize with your own logo | No | Yes |
| Add your own logo to the Nexus UI. | ||
| Features Included in both OSS and Pro | ||
| Basic repository | Yes | Yes |
| Reduce build times, increase control, and improve collaboration with hosted and proxy repositories. | ||
| Infrastructure | ||
| Native file system | Yes | Yes |
| Components are stored in the native file system and are directly accessible for emergency access and backup. | ||
| Support the largest deployments | Yes | Yes |
| Scales to support thousands of developers and hundreds of thousands of components. | ||
| Repository Hosting | ||
| Host Maven repositories | Yes | Yes |
| Store and manage your own components to encourage collaboration and code reuse. | ||
| Maven 1, 2, & 3 support | Yes | Yes |
| Backwards compatible with Maven 1, 2, and 3. | ||
| Maven 1 to Maven 2 conversion | Yes | Yes |
| Converts Maven 1 to a format understood by Maven 2 clients. | ||
| Load components via UI or through Maven | Yes | Yes |
| Populate your repo using multiple methods. | ||
| Repository Proxying | ||
| Proxy the Central Repository and other remote repositories | Yes | Yes |
| Locally store open source components for remote repositories to speed up builds and control access to components. | ||
| Proxy internal repositories | Yes | Yes |
| Mirror master repositories near consuming developers to reduce build times. | ||
| Single URL access | Yes | Yes |
| Consolidate multiple repositories under a single URL to simplify the configuration of your development environment. | ||
| Customize proxy security parameters | Yes | Yes |
| Implement your security policies when using a remote repository. | ||
| Mirror configuration and control | Yes | Yes |
| Reduce risk by allowing you to control which remote repositories can be used. | ||
| Repository Browsing & Search | ||
| Search for components | Yes | Yes |
| Search by GAV Coordinates, Class Name or a Class Name Pattern, or Checksum. | ||
| OpenSearch | Yes | Yes |
| Search for components from your browser’s search bar. | ||
| View POM, Javadoc, and file metadata | Yes | Yes |
| View component details from within Nexus. | ||
| Remote repository browsing | Yes | Yes |
| Find components that meet your needs and defined criteria without having to log into a remote repository. | ||
| Search with Nexus Indexer support | Yes | Yes |
| Search for public components locally without downloading the Internet first. | ||
| User Security | ||
| User authentication & authorizations | Yes | Yes |
| Implement your organization’s user security policies using standards-based tools. | ||
| Role-based access control | Yes | Yes |
| Control user privileges based on their role. | ||
| Fine grained control | Yes | Yes |
| Create detailed security policies using regular expressions to easily describe your requirements. | ||
| LDAP authentication | Yes | Yes |
| Use your existing LDAP infrastructure to authenticate users. | ||
| Operations | ||
| Scheduled tasks | Yes | Yes |
| Reduce administrative overhead by automating common functions. | ||
| Extensibility | ||
| Easily customize and extend with plugins | Yes | Yes |
| Extend the functionality of Nexus to meet your needs. No longer requires JavaScript or other plugin wrappers. | ||
| Flexible Plugin Licensing | Yes | Yes |
| License your Nexus plugins however you wish. You are no longer required to license them under AGPL. | ||
| Maven 3 metadata support | Yes | Yes |
| Use Maven 3 generated metadata that provides extra content. | ||
| IDE Integration | ||
| Eclipse integration via M2Eclipse | Yes | Yes |
| Search repositories from the Eclipse IDE, reducing your need to context switch between interfaces. | ||
