Skip to content
Paquetier

Tiers and License Keys

A self-hosted Paquetier instance runs one of three tiers, set by a license key from devXY. An instance without a valid key runs Free.

Free Team Enterprise
Mirroring and scans Unlimited Unlimited Unlimited
Packages of your own 5 25 Unlimited
Repositories hosting your own 1 5 Unlimited
Git builds No Yes Yes
Git sources None 10 Unlimited
Audit log No Yes Yes

The limits apply per instance. Prices and the shop are at licensing.devxy.io.

What counts

The limits count what you host: packages you upload, or that a git source builds on the instance. A package counts once per name per repository, with all its versions, binaries and archived versions. ggplot2 in two repositories is two packages, and its 40th version is still one.

Mirroring is free on every tier. Packages that an upstream mirror copies or a scan imports never count, however many there are. If you upload a version of a mirrored package, it becomes one of your own and counts from then on.

Creating repositories is free too. The repository limit counts only the repositories that host packages of your own, so a mirror repository never takes a slot.

What happens at a limit

The limits are soft. At the package limit the server refuses a new package of your own, and once every repository slot hosts packages it refuses a package of your own in another repository. The error names the limit. A package that is already there keeps taking new versions and binaries.

Nothing on the install path is ever blocked: every published package keeps installing from R, and no request from R checks the license. When the package limit is full, the app shows a banner to everyone who can add packages, so a refusal is never a surprise.

Git builds

Building packages from git sources on the instance is part of Team and Enterprise. On Free, build packages yourself, in CI or on a workstation, and publish them with paquetier upload or the upload API; binaries go up the same way.

  • Free refuses a new git source and every new build, manual, polled or retried, and stops polling git sources.
  • Team allows 10 git sources, each of which builds one package. The eleventh is refused, and deleting one frees its slot.
  • Sources beyond a limit, such as those left after a move from Enterprise to Team, stay and keep building; only new ones are refused.

Git sources and builds made under an earlier key stay listed and editable, and a build queued before a key lapsed still runs.

License keys

A key is a short text. Keys bought at licensing.devxy.io start with key/, and keys devXY issues by hand start with paquetier-license-v1.; both work the same. A key states the tier, the licensee, the expiry, about a year out, and the public URL of the one instance it is for, signed with Ed25519. The server checks the signature with public keys built into it, so no network call is made and air-gapped instances work. Nothing phones home.

A key works only on the instance whose PAQUETIER_PUBLIC_URL it names. The comparison ignores case, a trailing slash and a default port, so https://Packages.example.com/ matches https://packages.example.com. When you buy a key, enter exactly that URL; when you move an instance to a new URL, you need a key for the new one.

Installing a key

Admins install a key under Admin > License, which also shows the tier, licensee, expiry and usage against the limits. The key is stored in the database and reaches every replica within a minute.

For Helm and other declarative deployments, set the key in the configuration instead:

# the key itself
PAQUETIER_LICENSE_KEY=key/eyJ2Ijox...
# or a file holding it, such as a mounted Secret
PAQUETIER_LICENSE_KEY_FILE=/etc/paquetier/license.key

A key from the configuration wins over one installed in the app, and the app then shows it without letting anyone change it. The server logs the tier, licensee and expiry at startup.

To check a key before installing it:

paquetier-server license inspect --public-url https://packages.example.com key/eyJ2Ijox...

Expiry and renewal

From 30 days before a key expires, admins see a warning in the app. Each renewal comes with a new key for the new term, which you install the same way.

An expired key falls back to Free. Nothing is deleted and every package keeps installing; only new packages, repositories and git sources beyond the Free limits are refused, and git builds stop, until a renewed key is installed. A key that does not verify, or names another instance, also runs Free, and Admin > License says why.

The audit log on Free

On a tier without the audit log nothing new is recorded. Events recorded under an earlier key stay, and admins can still read and export them under Admin > Audit log, which says that recording is off. They are the instance owner’s record, so a lapsed key never takes them away.