Question 1

Which package ecosystems are supported?

Accepted Answer

Omni Line supports npm, Composer, Docker, PyPI, Go, Cargo, Maven, RubyGems, and Multipurpose today, all behind one UI and one API. See /registries for an overview of each self-hosted registry, or /docs/registries for setup guides.

Question 2

Can I run it on my own infrastructure?

Accepted Answer

Yes. Omni Line is self-hosted by design. Artifacts are stored through a pluggable storage driver (local disk by default) and metadata in PostgreSQL — all on your servers.

Question 3

What's the difference between hosted, proxy, and virtual?

Accepted Answer

Hosted registries store your own private packages. Proxy registries cache an upstream registry. Virtual registries aggregate several registries behind a single endpoint by priority.

Question 4

How does authentication work?

Accepted Answer

The web UI uses standard login sessions, while CLIs and CI authenticate with personal access tokens. Registries can also allow anonymous read when you want public access.

Question 5

How does licensing work?

Accepted Answer

Omni Line is commercial self-hosted software. You run it on your own infrastructure with a license key from this portal — no per-seat pricing and no vendor lock-in.