Launch NODIF for your service.

Know the operating model

NODIF is a VPN client and provider platform; it is not a VPN subscription. Your organization supplies and supports the subscription, gateways, limits, account lifecycle, and Remnawave environment. NODIF supplies the client, signed provider experience, scoped portal/API access, and—on entitled plans—consent-based aggregate quality intelligence.

Choose the plan that matches today’s need

Identifier and credential glossary

Before access is issued

• Verified provider owner/operator and service domain.
• Generic HTTPS support, privacy and optional renewal pages with no per-user token in the URL.
• Evidence that you may use the submitted name and logo.
• Named technical owner, backup operator, and incident contact.
• Remnawave v3 environment with a staging or restricted External Squad.
• Provider privacy notice covering its own account, payment, gateway and support practices.
• Agreement that NODIF analytics is optional, purpose-limited and not an individual-user product.

First portal access

1. Receive the one-time prv_ owner key through the approved delivery channel.
2. Store it before closing the one-time view; NODIF cannot recover plaintext.
3. Open the provider portal and enter the key. It remains in session storage for that browser tab and is never written into a URL.
4. Verify provider name, public slug, plan and subscription state.
5. Create narrower keys for automation or analysts instead of sharing the owner key.
6. Open the Remnawave guide and test only an internal canary first.

Branding approval

The live profile is a signed NODIF object. Subscription responses cannot inject CSS, HTML, scripts, fonts, remote images or alternate control hosts. During the current launch phase, NODIF staff applies and approves production branding so the previous live profile is not removed while a change awaits review.

• Display name: 2–48 plain characters and cannot impersonate NODIF.
• Logo: PNG, WebP or JPEG; maximum 512 KiB and 1024×1024; NODIF-hosted after validation.
• Colors: exact #RRGGBB; the app may apply a safe contrast fallback.
• Theme: dark or system. Layout: standard or compact.
• Links: generic HTTPS URLs with a DNS hostname; no IP literal, userinfo, fragment, token or per-user identifier.
• Announcement: optional, plain text, maximum 240 characters.

Custom signed expired/limited/disabled messages are not released. Configure generic Remnawave remarks for those response-body states and keep actionable URLs in the approved NODIF profile.

Production launch checklist

• Public slug and branding token are scoped to the correct External Squad.
• The narrow NODIF response rule sits above generic rules and has a deliberate fallback.
• Active, expired, limited, disabled, empty-host and every enabled HWID case were tested.
• Users inside and outside the canary squad receive the expected response with no cross-tenant headers.
• Provider links and approved live branding were checked in the app.
• Android installation, subscription refresh, connect, disconnect, route check and safe diagnostic export were tested.
• Support staff know what evidence to request and what sensitive fields are forbidden.
• Rollout has a staged percentage, observation window, rollback owner and success threshold.
• Analytics expectations account for consent, delayed offline upload, unknown context and cohort suppression.

Suspension and offboarding

1. Stop new assignment to the NODIF External Squad.
2. Remove both NODIF pointer headers from provider responses.
3. Revoke branding tokens and provider API keys.
4. Confirm the provider subscription/tenant status with NODIF.
5. Export only permitted aggregate business records; raw user telemetry is not an export feature.
6. Follow contractual retention and deletion obligations for leads, provider metadata and operational records.
7. Remove secrets from automation and rotate any shared upstream credential independently.