Artifact Repository
Artifact Repository in Nexus Repository Manager is designed around Universal artefact repository manager for Maven, npm, Docker, and PyPI and tied to measurable business objectives.
Package Proxy
Nexus Repository Manager brings Package Proxy into a controlled workflow with roles, approvals and traceable data paths.
Repository Policies
Repository Policies can connect to operations, reporting and adjacent systems instead of remaining an isolated function.

Nexus Repository Manager Self-Hosting: Installation, Operations & Support
WZ-IT plans, installs, migrates and operates Nexus Repository Manager on your infrastructure (Universal artefact repository manager for Maven, npm, Docker, and PyPI), with monitoring, backups, updates and clear responsibilities. Instance and licence stay with you.
About the technology
What is Nexus Repository Manager?
Nexus Repository Manager addresses Universal artefact repository manager for Maven, npm, Docker, and PyPI. A running application alone is not enough for production: data, identities, integrations, updates and recovery have to be designed as one system.
Scoping focuses on Artifact Repository, Package Proxy, Repository Policies, roles, data paths and recovery. WZ-IT turns these requirements into a documented target architecture and, on request, takes over migration, integration and ongoing operations on your infrastructure.
Functions and operating components for Nexus Repository Manager
Artifact Repository
Artifact Repository is configured and documented in Nexus Repository Manager around roles, data paths and operational requirements.Package Proxy
Package Proxy is configured and documented in Nexus Repository Manager around roles, data paths and operational requirements.Repository Policies
Repository Policies is configured and documented in Nexus Repository Manager around roles, data paths and operational requirements.Roles and access
Separate administrators, business users and technical accounts with traceable permissions.Interfaces
Connect APIs, webhooks, directory services and adjacent business systems in a controlled way.Data and recovery
Protect persistent data, configuration and restart procedures according to the agreed scope.Migration and takeover
Assess existing data and configuration, migrate them in a test run and move to managed operations through a controlled cutover.Identity and secure access
Secure SSO, roles, administrative paths and external access for the application and existing infrastructure.Backup and recovery
Back up all stateful components consistently and document the recovery path for the agreed scope.Updates, monitoring and operations
Monitor and update the application and its technical dependencies and operate them under the agreed service level.
Managed operations
Operating Nexus Repository Manager with clear ownership
With Nexus Repository Manager, repositories, artefacts, runners or runtimes, credentials and target environments form one delivery chain.
Application platform
Operate runtime, dependencies, proxy and persistent components reproducibly.Data and state
Protect databases, files, configuration and retention in a traceable way.Integrations
Connect APIs, identities and downstream systems with defined failure paths.Maintenance and recovery
Combine monitoring, updates, backups, restore and incident response.
Area
Responsibilities without operational gaps
Platform operations, business configuration and integrations are separated and adapted to your environment in the proposal.
| Area | Responsibility | Scope boundary |
|---|---|---|
| Platform and runtime | WZ-IT | Deployment, hardening, monitoring, maintenance and technical documentation. |
| Backup and recovery | WZ-IT | Backup scope, supervision and agreed recovery exercises. |
| Configuration and roles | Shared | WZ-IT implements technically; your team approves business roles and permissions. |
| Business data and processes | Customer | Content, data quality and business decisions remain with the organisation. |
| Edition and licence | Shared | WZ-IT reviews the technical scope; required rights are agreed jointly. |
| Extensions and development | Expandable | Plugins, custom functions and deep integrations can be added as a retainer or project. |
Use and integration
Introducing Nexus Repository Manager around the actual process
Value is created when the application, data, permissions and downstream systems are designed as one end-to-end workflow.
Connect Artifact Repository
Data sources, APIs and import paths for Artifact Repository are versioned, protected and tested for failure states.
Connect Package Proxy
Identities, roles and process hand-offs around Package Proxy are aligned with existing business systems.
Connect Repository Policies
Monitoring, notifications and exports for Repository Policies route technical signals into the responsible workflows.
Record the version, edition, extensions and licence state of the Nexus Repository Manager environment
Review Artifact Repository including data, configuration and dependencies
Map Package Proxy together with connected identities and interfaces
Verify Repository Policies, monitoring, backup and recovery in practice
Full operations on your infrastructure
Nexus Repository Manager - fully operated on your infrastructure
Nexus Repository Manager remains on your infrastructure. We define the operating scope, backup architecture and service level based on the existing system and its criticality.
Operations on your infrastructure
- Installation, configuration and ongoing operations
- Regular updates, CVE monitoring and prioritised patches for critical vulnerabilities
- Central logs with immutable retention
- 24/7 proactive monitoring
- Backup and retention according to the agreed architecture
- Five service levels, 24/7 P1 response with Production or Critical
- Infrastructure and data remain under your control
- Personal technical contact
Straightforward provisioning within a few business days
- Bank transfer
All prices are net and exclude statutory VAT. The offers are addressed to businesses. All on-premises options
Service levels
Five service levels for different operating requirements
Response target = initial technical response to critical incidents (P1) · Price and flexible operations allowance per customer environment and month · Hourly rate for additional work
Essential
Next business dayby end of dayInitial technical response to critical incidents (P1) by the end of the next business day
includedin the base operations price
no allowance- Hourly rate
- Standard rate
- regular service hours
- €120
- outside regular service hours
- €240
For less time-critical systems, staging and internal applications.
Business
Popular4 hwithin service hoursInitial technical response to critical incidents (P1) within 4 service hours
+€99.90
0.5 h allowance- Hourly rate
- 5% below standard
- regular service hours
- €114
- outside regular service hours
- €228
For production systems without contractual night and weekend on-call coverage.
Priority
1 hwithin service hoursInitial technical response to critical incidents (P1) within 1 service hour
+€199.90
1 h allowance- Hourly rate
- 10% below standard
- regular service hours
- €108
- outside regular service hours
- €216
For business-critical systems requiring a fast response during the service window.
Production
60 minnights and weekends includedInitial technical response to critical incidents (P1) within 60 minutes, 24/7
+€349.90
1 h allowance- Hourly rate
- 15% below standard
- regular service hours
- €102
- outside regular service hours
- €204
24/7 P1 on-call coverage for business-critical production environments.
Critical
after audit30 minnights and weekends includedInitial technical response to critical incidents (P1) within 30 minutes, 24/7
+€549.90
2 h allowance- Hourly rate
- 20% below standard
- regular service hours
- €96
- outside regular service hours
- €192
Available after audit, runbook and capacity approval.
Business, Priority, Production and Critical include the first covered workload in a customer environment. Further covered workloads cost €29.90, €39.90, €49.90 and €59.90 per month respectively. For monitoring-only servers, we notify within the level's window for €14.90, €19.90, €24.90 and €29.90 per server and month respectively; without a service level, during service hours.
The flexible operations allowance applies to planned work during regular service hours and expires at month end. Operations, monitoring, backups, maintenance and updates within the agreed scope do not reduce it. Additional work beyond the agreed operations and the allowance, as well as further incident work, is billed at the hourly rate of the service level of the affected environment. The standard rate applies to commissioned work without a service level. Hour packages and fixed prices have their own prices. All prices are net and exclude statutory VAT. The offers are addressed to businesses.
SLA & Service Levels →Sizing and deployment location
Sizing Nexus Repository Manager for real usage
User count alone does not determine sizing. Concurrency, data volume, background jobs, integrations and recovery objectives define the required environment.
| Usage profile | Starting point | Decisive factors |
|---|---|---|
| Small production entry | Technical discovery | Users, data, integrations and protection requirements are classified. |
| Several teams or departments | Load and role profile | Concurrency, permissions and background processes are assessed separately. |
| High data or transaction load | Capacity assessment | Growth, I/O, caches and bottlenecks are measured or modelled. |
| Business-critical operations | HA and recovery design | Outage objectives, maintenance windows and restart targets shape the architecture. |
- The calculator is technical guidance. Data volume, high availability, integrations, migration, edition and service level are assessed before a binding proposal.
Sizing and deployment location
Available deployment locations
Nexus Repository Manager runs in your cloud, on premises or in a hybrid setup. The instance and, where required, the vendor licence stay with you; WZ-IT operates it on your behalf.
Your cloud
Operations in your existing cloud account with clear separation of platform and account ownership.On premises
Deployment in your data centre or server room close to internal data sources and business systems.Hybrid
Distribute application, data and integrations across locations through controlled private connections.
Target architecture
Embedding Nexus Repository Manager safely in the system landscape
User access, control plane, execution environments and artefacts are isolated so untrusted code receives no unnecessary platform rights.
Business users and systems
Controlled use through browsers, clients, APIs or automated processes.
Access and network boundary
TLS, reverse proxy, private access and restricted administration paths.
Identities and roles
SSO, directory services, role model and technical service accounts.
Nexus Repository Manager platform
Application services, configuration, jobs and business runtime state.
Persistent data
Databases, object storage or files with a defined backup scope.
Interfaces
APIs, webhooks, queues and directory services connected to adjacent systems.
Operational signals
Logs, metrics, health checks and alerting for the agreed scope.
Production and administration access are separated; secrets and technical accounts are not kept in uncontrolled configuration files.
Licence and edition review
Offering Nexus Repository Manager with the appropriate usage rights
The licence has undergone a technical review. Before the proposal, we align edition, functionality, operating model and vendor terms with the concrete use case.
| Licence model | Reviewed on |
|---|---|
| EPL-1.0 | 2026-10-15 |
- How licensing enters the proposal: The source code of Nexus Repository (nexus-public) is licensed under EPL-1.0 and contains only the core. The full feature set is delivered by Sonatype as a Community Edition package under its own terms of use (https://github.com/sonatype/nexus-public/blob/HEAD/README.md), which apply to you. WZ-IT therefore does not offer Nexus Repository as hosting, but installs and operates it as your own instance on your infrastructure and on your behalf. On request, we support you in obtaining any required vendor licence.
- Nexus Repository Manager is a trademark or product name of its respective owners. WZ-IT is an independent service provider, neither a partner nor a representative of the project, and is not affiliated with it.
- Open official licence source
Role in the overall system
Related services for Nexus Repository Manager
This page covers installation and the agreed platform operations for Nexus Repository Manager. Custom code, the access layer and special confidentiality requirements remain clearly separated responsibilities that can be added when needed.
Support custom code and integrations
Keep custom extensions, interfaces and dependencies controlled, updated and supportable.
View service Secure accessConnect users, sites and systems
Add identity-based access and private network paths as a separate operational layer.
View service Operate confidentiallyAssess Section 203 requirements separately
For professional secrecy holders, define contractual, access and infrastructure requirements in a dedicated operating model.
View serviceThree relevant adjacent paths instead of a long list of further products.
View the overall systemFrequently asked questions about Nexus Repository Manager self-hosting
Answers about operations, migration, licensing, infrastructure and integrations.
- Depending on the agreed scope we take over target architecture, installation, secure baseline configuration, monitoring, backups, updates, recovery, documentation and technical incident handling. The instance runs in your environment and belongs to you.
- Yes. Before takeover we assess version, edition, data, extensions, identities, integrations, backup status and known legacy issues, then define a controlled takeover or migration plan.
- At the review date of this page, EPL-1.0 was identified. Before deployment we verify the concrete version and edition again and document the applicable licence source. The source code of Nexus Repository (nexus-public) is licensed under EPL-1.0 and contains only the core. The full feature set is delivered by Sonatype as a Community Edition package under its own terms of use (https://github.com/sonatype/nexus-public/blob/HEAD/README.md), which apply to you. WZ-IT therefore does not offer Nexus Repository as hosting, but installs and operates it as your own instance on your infrastructure and on your behalf. On request, we support you in obtaining any required vendor licence.
- No. The licence terms of Nexus Repository Manager restrict operating it as a service for third parties. WZ-IT therefore installs and operates Nexus Repository Manager exclusively on your infrastructure, in your cloud, on premises or hybrid, and only within the scope of your licence.
- Typical integrations include Git, CI/CD, container registries, package sources, cloud or Kubernetes targets, SSO and secrets management. Permissions are bounded along the delivery chain.
Reviews & projects
Client feedback and projects worldwide
Networking & Provisioning
WZ-IT moved our studio infrastructure from decentralised individual devices to a central platform: every site is securely connected via VPN, new devices are onboarded automatically and an entire site is provisioned from a template, without manual steps on location. What impressed me most is the breadth and depth of their knowledge: Timo and Robin are not a typical IT provider who sets up a server and leaves. The two of them think their way into highly complex infrastructure and software topics, work through every requirement we put in front of them, and build networking, provisioning and operations so that everything fits together in the end. WZ-IT is an excellent partner for complex software, network and architecture projects.
Steve KirchnerManaging Director, nextGYM GmbH
International
Built in Germany's Ruhr Valley. Running worldwide.
WZ-IT designs, develops and operates infrastructure and software for clients in Germany and internationally. We deliver projects remotely and continue supporting them in ongoing operations after go-live.
Selected projects
- LiveRemote access platform for distributed water treatment plantsABCO Water Systems · Australia · Secure Access & OT
- 81%AWS migration with substantially lower operating costsEVA Real Estate · UAE · Cloud exit & infrastructure
- 98%Provision new sites in minutes instead of hoursnextGYM GmbH · Germany · Automation & IoT

Read client reviews
Full operations on your infrastructure
Enquire about operating Nexus Repository Manager on your infrastructure
Briefly describe the current state and objective for Nexus Repository Manager. We assess infrastructure, integration, and ongoing operations.
- Straight with Timo and Robin - no sales team, no pitch
- A professional assessment of your situation
- Concrete next steps for infrastructure, software or AI
The conversation is free and non-binding.
WZ-IT's advice on our Azure migration was technically sound and completely non-binding right from the intro call - we took away a great deal.
Jakob ÖschlbergerInno7 GmbH

WZ-IT's advice on our Azure migration was technically sound and completely non-binding right from the intro call - we took away a great deal.


















