Sponsor a RIRRd-managed node

Sponsor a dedicated VM and receive a hosting credit in the regional directory. The Rust daemon and bundled self-hosted console remain open source. The community platform and its operator workflows are maintained separately.

Starting specifications

These are engineering starting points, not measured minimums or a capacity promise. We qualify imports, recovery, sustained queries and disk headroom before accepting a node. The current 19-source production profile retains routing objects. The expanded development profile retains all 19 standard classes across 21 datasets and needs considerably more disk space. Budget for the serving database, the previous verified generation, a new offline candidate and its normalization files; independent backups need separate capacity. The full builder also refuses to start below 64 GiB free. Do not use routing-only disk figures to size a full-class node. Cache limits are not total RAM limits. Prebuilt binaries avoid needing a compiler on the sponsored machine.

Use Debian 12/13 or Ubuntu 24.04 LTS, Linux x86-64 or ARM64, stable public IPv4 and IPv6 and outbound access to selected upstream feeds. Public service ports are TCP 43, 80 and 443; SSH management must be reachable by our operators. PostgreSQL and Redis are not runtime requirements.

Root access is required for managed sponsorship

RIRRd operators require continuing, key-based root access, or a dedicated administrator with unrestricted passwordless sudo. We need to install, patch, monitor and audit the guest, check binaries/configuration, source hashes/serials and consistency of served IRR data. The daemon runs as an unprivileged user.

Offer only a dedicated VM you control and are authorised to grant access to. Do not offer a production router, storage server, shared customer host or guest containing unrelated private data. Root grants control of the guest and access to its files. It enables integrity checks; it does not guarantee correctness of every upstream registry record or make beta software production qualified.

Operator public key

Download our onboarding public key. Add it to the administrator's SSH authorised keys. Keep your own management access working. We retain the private key; do not send passwords or private keys through the form.

After enrolment, we replace this bootstrap key with a separate, revocable key for that node and remove bootstrap access. You can revoke access by removing our key; the managed listing is paused/removed if required access is lost.

Request review

Contact and management details go into a private review queue. Nothing connects to the supplied host or publishes its details automatically. Ownership, access scope, machine role and sponsor credit are confirmed before enrolment.