Nexus Repository Hosting on MassiveGRID PaaS
Nexus Repository Manager OSS is Sonatype's open-source artefact repository, hosting and proxying Maven, npm, Docker, PyPI, NuGet, Helm and many other formats from one server. The MassiveGRID PaaS package deploys Nexus with persistent blob storage in one click, giving your builds a fast, private, cached source of dependencies.
Nexus Repository on MassiveGRID PaaS installs in one click in New York, London, Frankfurt or Singapore, costs about $157.44 a month for the Starter configuration, a Nexus Repository OSS node (8 GiB), and starts with a 14-day free trial. See the sizing table.
Both buttons open the MassiveGRID PaaS dashboard with Nexus Repository pre-selected. Sign up without a card, name the environment, pick a region, and the package installs in a few minutes.
Nexus Repository Package Facts
| Attribute | Value |
|---|---|
| Package | Nexus Repository Manager |
| Type | Application (installs a complete environment) |
| Category | DevOps & Admin Tools |
| Software vendor / project | Sonatype |
| Licence | EPL 1.0 (Nexus Repository OSS, open source) |
| Runtime / stack | Nexus Repository OSS on a Java node with persistent blob storage |
| Regions | New York, London, Frankfurt, Singapore |
| Billing | Pay-per-use, about $157.44/month for the Starter configuration (64 cloudlets at $0.003372 per cloudlet-hour), no licence fee |
| Free trial | 14 days, no credit card |
| Uptime SLA | 100% |
What is Nexus Repository?
Every build pulls dependencies from public registries, and every deploy pushes artefacts somewhere. A repository manager sits in the middle: it caches public packages so builds are faster and immune to registry outages, hosts your private libraries and container images, and gives you one place to control what enters your supply chain. Nexus OSS supports more formats than any other free repository manager.
The package deploys Nexus on a Java node with persistent storage for blobs and the internal database, exposes the web UI over HTTPS and sets the initial administrator. It pairs with the Jenkins and GitLab packages to complete a self-hosted CI/CD tool-chain inside your MassiveGRID region.
What the Nexus Repository Package Deploys
Marketplace packages are not bare container images. One click provisions a complete, production-shaped environment on MassiveGRID infrastructure. How these nodes are sized and what they cost.
- Nexus Repository OSS: The current OSS release on a Java node with JVM settings sized to the cloudlets.
- Persistent blob storage: Disk for cached and hosted artefacts, expandable from the dashboard, with snapshots.
- HTTPS web UI and repository endpoints: Access on the platform subdomain, with additional ports for Docker registries.
- Initial administrator: Admin credentials delivered after installation for creating repositories and users.
What Nexus Repository Costs to Run
Three starting configurations for the Nexus Repository package, sized in cloudlets (1 cloudlet = 128 MiB RAM + 400 MHz CPU) and priced at the published rate of $0.003372 per cloudlet-hour, or $2.46 per cloudlet-month. Sonatype's smallest published sizing profile is 4 vCPU and 16 GiB per node with two thirds of the RAM given to Nexus; the Starter row sits below it and suits a small team's proxy, not a busy production registry. Blob storage is billed per gigabyte on top.
| Configuration | Topology | Cloudlets | Est. per month |
|---|---|---|---|
| StarterA small team's proxy and private artifacts | Nexus Repository OSS node (64 cloudlets, 8 GiB) | 64 | $157.44 |
| StandardSonatype's XS profile | Nexus Repository OSS node (128 cloudlets, 16 GiB) | 128 | $314.88 |
| ProductionDocker and Maven registries under CI load | Nexus Repository OSS node (192 cloudlets, 24 GiB) | 192 | $472.32 |
Estimates assume the environment averages the listed cloudlets around the clock; billing is hourly, vertical auto-scaling lowers the figure when the application is idle, and volume discounts apply as usage grows. Disk and external traffic are billed per gigabyte on top. No licence fee applies to the package. Pick a row in the installer by setting the cloudlet limits per node, or start small and let auto-scaling grow it. Price a different topology or a working-hours schedule in the PaaS pricing calculator; the PaaS page describes the billing model.
Why Teams Choose Nexus Repository
Universal formats
Maven, Gradle, npm, Yarn, Docker, PyPI, NuGet, RubyGems, Helm, APT, YUM, raw and more.
Proxy and cache
Cache Maven Central, npmjs and Docker Hub locally so builds are fast and survive upstream outages or rate limits.
Private hosting
Publish internal libraries and images with role-based access control and LDAP integration.
Supply-chain control
Group repositories, cleanup policies and routing rules govern what your builds may consume.
How to Install Nexus Repository on MassiveGRID PaaS
Installing the package takes three steps and a few minutes of waiting. No servers to provision, no configuration files to edit.
Open the installer
Click Install with free trial or Install to my account. The MassiveGRID PaaS dashboard opens with the Nexus Repository package pre-selected, so nothing has to be copied or pasted.
Sign up or sign in
New to the platform? Sign up for the free 14-day trial, which needs no credit card. Existing customers sign in with their usual dashboard credentials.
Choose region and deploy
Name the environment, pick New York, London, Frankfurt or Singapore, and confirm. The platform builds every Nexus Repository node, wires them together and hands you the live URL and credentials.
Who Runs Nexus Repository on PaaS
Development teams
Faster, more reliable builds through local caching of public registries.
Private container registries
Hosting Docker images for Kubernetes or Swarm deployments inside your region.
Regulated environments
Organisations that must control and audit third-party dependencies.
Why Run Nexus Repository on MassiveGRID PaaS
Built for uptime. Nexus Repository runs on MassiveGRID's high-availability platform, where every environment is covered by a 100% uptime SLA. Nodes live on redundant hosts, storage is replicated, and failed containers are restarted or migrated automatically.
Pay for what you use. Billing is hourly and per cloudlet (128 MiB RAM plus 400 MHz CPU). Vertical auto-scaling adds and removes cloudlets as load changes, so a quiet Nexus Repository environment costs a few dollars a month and a busy one grows without a migration. Full details are on the PaaS page.
Your choice of jurisdiction. Deploy in New York, London, Frankfurt or Singapore and keep data inside the region your users or regulators require. MassiveGRID is ISO 27001 and ISO 9001 certified and GDPR compliant, and has run hosting infrastructure since 2003.
No lock-in. The package is a standard Jelastic Packaging Standard (JPS) manifest. You keep root-level access to the containers, can export the manifest, and can move the workload to any other Jelastic-compatible platform or to your own servers at any time.
Related on massivegrid.com: DevOps Support.
Nexus Repository Questions
Nexus Repository Guides from the MassiveGRID Blog
Scenario-driven guides on running Nexus Repository on MassiveGRID PaaS, written for the developers, operators and buyers who deploy it. Browse the blog.
More from the Marketplace
Packages that are often deployed alongside Nexus Repository, or that solve the same problem a different way. Browse all 83 packages.
Deploy Nexus Repository Today
Start the free 14-day trial and have Nexus Repository running in minutes. No credit card required.