One server can hold every package your builds pull, publish, and cache, so the team stops juggling a different registry for every language. Astrum Repository hosts your own artifacts, proxies public registries so builds keep working when an upstream is down, and groups both behind a single address your tools already understand. Thirty-nine formats share that address: Docker and OCI images, Maven, npm, PyPI, Cargo, Go modules, Helm charts, NuGet, Terraform modules, APT and Yum packages, Hugging Face models, browser extensions, Git LFS, and even remote caches for Nx and Turborepo. Blob storage grows with you, moving between disk, S3, and agent-connected stores that combine into groups without relocating data. Access stays deliberate through users, roles, privileges, and content selectors, with LDAP and OpenID Connect sign-in and access tokens minted for CI pipelines. Day-to-day operations are visible rather than guessed: health endpoints, Prometheus metrics, scheduled tasks, cleanup policies, audit trails, and backups are built in, and several servers can share one database when a single node is no longer enough. The web interface speaks twelve languages, so a platform team spread across regions still works in one console. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

One trusted home for every package your build pipeline consumes: kkRepo hosts, proxies, and groups artifacts for Maven, npm, PyPI, Docker and OCI, Helm, Cargo, Go, NuGet, Composer, Terraform, Conda, APT, Conan, RubyGems, Yum, and more than twenty formats in total. Point your existing Nexus clients at it and nothing changes, because repository domains, the /repository/ URL layout, and the permission model carry over, and a one-click migration moves hosted data while clients keep building. Upstream proxies can be tuned per repository with their own outbound proxy and credentials, group repositories present many sources as one endpoint, and cleanup policies retire old artifacts before disks fill. Every stored artifact can be scanned against known vulnerabilities with SBOM generation and download enforcement, while Local, LDAP, and OIDC sign-in with fine-grained permissions decides who may publish or pull. Prometheus metrics and ready Grafana dashboards show throughput and storage, and multi-replica deployments share state through MySQL or PostgreSQL with blobs in S3-compatible storage. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache 2.0 licensed.

Public registries rate-limit your CI, log every pull, and pick the worst moment to go down; Nora replaces that dependency with a self-hosted artifact registry that hosts and caches seventeen package formats behind a single address. Point Docker, Maven, npm, pip, Cargo, and eleven other clients at one endpoint, and Nora serves your private artifacts while transparently caching upstream packages fetched from Docker Hub, Maven Central, npmjs, and crates.io. Each base image or library downloads once and is then served locally, so builds get faster, stop tripping rate limits, and survive upstream outages. Curation rules decide what is allowed to reach your builds: allowlists and blocklists filter packages by name, minimum release-age rules hold back freshly published versions, and new digests can wait in quarantine until approved. Anything you publish keeps its name: a hosted package is never silently replaced by an upstream package sharing it. Pipelines publish without stored secrets through OIDC identity from GitHub Actions and GitLab CI, and API tokens with read, write, and admin roles cover the rest. A web dashboard shows downloads, cache hit rates, storage usage, and recent activity for every registry, and audit logs plus Prometheus metrics feed your monitoring. For disconnected networks, a mirror command prefetches whatever your lockfiles name, an import tool migrates Artifactory or Nexus repositories, and backup and restore keep a spare copy. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Private npm packages without shipping code to the public registry or paying for npm Enterprise: Verdaccio is the standard lightweight, zero-config private registry and caching proxy. It runs as a single Node.js process with its own tiny embedded database; no external database is required to start. Point npm, yarn, or pnpm at it and everything behaves as expected: install, publish, unpublish, dist-tags, and deprecation all work against the standard npm endpoints. The uplink system is where it earns its keep: packages not found locally are fetched from configured upstreams (npmjs.org, yarn, JFrog, Nexus, or another Verdaccio), cached as tarballs, and served locally thereafter - cutting CI latency and surviving registry outages. Multiple uplinks chain for failover, and per-package glob patterns in config.yaml route scopes to specific upstreams while controlling access, publish, and unpublish rights per group. You can even override a public package by publishing a patched version under the same name locally. A plugin architecture swaps in auth backends (htpasswd default, LDAP and others available), storage drivers (S3, Google Cloud Storage), middleware routes, and metadata filters. With official Docker images and a Kubernetes Helm chart, it slots into any pipeline in minutes.

The first container registry to reach CNCF graduated status with over 29,000 GitHub stars since VMware open-sourced it in 2016, Harbor transforms the basic Docker Distribution into a hardened enterprise registry with vulnerability scanning, supply chain signing, multi-datacenter replication, and project-level access control out of the box. Trivy scans every pushed image against the NVD, GitHub Advisory Database, and distribution-specific vulnerability feeds, with scan-on-push policies that block deployment of images exceeding configurable severity thresholds. Artifact signing through Cosign keyless signatures and Notation enforces content trust policies ensuring only cryptographically verified images reach production clusters. Policy-based replication synchronizes images and Helm charts between Harbor instances across multiple datacenters using repository, tag, and label filters with automatic retry and bandwidth throttling — enabling hybrid-cloud and disaster-recovery topologies. The RBAC model isolates projects with per-project quotas, robot accounts for CI/CD automation, webhook notifications, and audit logging that tracks every pull, push, delete, and configuration change. LDAP, Active Directory, and OIDC authentication integrate with existing identity providers, while the proxy cache transparently caches images from Docker Hub, Quay, and other upstream registries to reduce pull latency and rate-limit exposure. The RESTful API with embedded Swagger UI, tag retention policies, garbage collection scheduling, and immutable artifact rules complete the lifecycle management. Deploy via Docker Compose or Helm Chart on Kubernetes. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache 2.0 licensed.

Instead of querying a private registry with curl and its HTTP API, open Docker Registry UI and click through repositories, tags, digests, and layers in a browser. The catalog groups images by namespace, shows tag counts, and filters as you type in the search bar, which Ctrl+F or F3 focuses. Each repository's tag list shows creation date, size, content digest, and CPU architecture, sorts numerically, and copies a ready-made pull reference with one click. A history page expands any tag into its operating system, entrypoint, environment variables, exposed ports, and layer-by-layer build steps, and a Dockerfile view reconstructs the file from those steps. The same view also covers multi-architecture images and OCI Helm exports. When the registry allows deletion, tags go one at a time or in bulk with checkboxes, Alt+Click for a whole page, and Shift+Click for a range. One interface can switch between several registries from its menu, or be locked to a single registry with your own title. Basic authentication passes through the browser, and a built-in proxy option forwards requests to your registry container so CORS needs no configuration. Light, dark, and automatic themes come with color variables for custom branding, and a weekly notice announces newer releases. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. AGPL-3.0 licensed.

Tapflow puts your team's iOS simulators and Android emulators in every teammate's browser, so QA stops queueing for the one Mac that happens to have the right build installed. A relay server you host serves the dashboard and API, stores your builds and recordings, and keeps accounts and device control on infrastructure you own. Agents on your Macs connect out to the relay and drive the simulators already installed there, injecting touches directly without WebDriverAgent or any cloud device pool. From the browser you tap, swipe, and pinch at about 30 frames per second, open deeplinks from the QA toolbar, sync the clipboard both ways, hear device audio, and cut the network to see how the app copes offline. The App Center takes .app.zip and .apk uploads and tracks each build from backlog to done, and sessions can be recorded and shared before the relay purges them after about 72 hours. CI pipelines and AI agents get a screenshot endpoint and scoped access tokens, deterministic YAML flows replay checks with a JUnit report, and roles keep viewers, QA, developers, and admins in their lanes. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Measure is an open-source mobile monitoring platform that shows mobile teams what broke, how often, and what the user did right before it happened. Crashes, ANRs, and app hangs are grouped into single issues, and each fatal error arrives with a session replay: an ordered timeline of screens opened, taps, network calls, logs, and lifecycle events, with CPU and memory charts alongside screenshots and wireframe layout snapshots. Bug reports can be filed with a device shake or an SDK call and carry the same history of user actions. Performance traces and spans break slow startups and screens into steps, and network monitoring ranks the slowest and most error-prone endpoints. Funnels built from custom events show conversion and drop-off at each step, with a Friction view that ties every step to the crashes, errors, slow traces, and network requests users hit there. User journeys chart how people move between screens, and Adaptive Capture changes sampling, replay length, and screenshot masking remotely, with no new app build. SDKs cover Android, iOS, Flutter, React Native, and Kotlin Multiplatform. Teams sign in with Google or GitHub, invite colleagues by email, and send alerts to Slack, and an optional Measure Agent lets a coding agent or Slack help debug production issues. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.

AsoBeast keeps score of your app in the App Store and Google Play, so you always know which keywords you rank for, which ones moved, and what to fix next. Paste a store URL and tracking starts on import: rankings are checked daily in your home storefront and any other market you add, and every keyword is scored for popularity, difficulty, and opportunity so you can tell a winnable term from a vanity one. The dashboard leads with your keywords in the top 10, this week's movement, and an Action Center that turns the data into specific moves, like defending a keyword where two new rivals just entered the top 10, with the reason and the fix spelled out beside each item. Competitor listings are diffed over time, so a rival's new title, subtitle, version, or release notes show up as a before-and-after entry instead of a surprise. Metadata snapshots keep the raw store payload, localization and keyword field analysis shows wasted words, reviews feed the audit score, and the same data is exposed to your AI tools through the built-in MCP server. Registration closes itself once your owner account exists, and store requests run from your own server. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. AGPL-3.0 licensed.