Approve the provider and plan
NODIF verifies the operator, service identity, privacy/support URLs, brand rights, and intended plan before issuing tenant credentials.
NODIF knowledge center
Operate a better VPN experience.
Role-based guidance for launching NODIF, connecting Remnawave, supporting users, protecting credentials, interpreting quality signals, and responding to incidents.
Choose your path
Start with your job.
Each path begins with the decisions and checks that role owns. Cross-links lead to deeper reference material.
Provider owner
Choose a plan, complete approval, assign operators, launch safely, and understand what NODIF does and does not provide.
DevOps / NOC
Configure scoped response headers, test a canary, rotate tokens, monitor health, roll back, and escalate without leaking secrets.
IT / support
Install the app, add subscriptions, explain Smart Route, solve common Windows and Android problems, and gather safe diagnostics.
Complete guides
Find the exact runbook.
Search by task, platform, symptom, or responsibility.
Provider quick start
Approval, plan selection, identifier glossary, first portal access, brand review, production launch, and offboarding.
Open quick start →Remnawave integration
Exact header values, ordering, scope, cache behavior, verification, HWID handling, token rotation, and rollback.
Open integration guide →NODIF app & support
User-facing installation and connection guidance, quality controls, diagnostic boundaries, and platform availability.
Open app guide →Provider API & access
Provider keys, roles and scopes, authentication, safe examples, error handling, rate limits, and automation patterns.
Open API guide →Analytics guide
Metric definitions, cohort suppression, coverage, freshness, safe comparisons, known limitations, and action playbooks.
Open analytics guide →Operations runbook
Responsibility boundaries, service checks, change control, backup expectations, incident triage, and escalation evidence.
Open operations runbook →Troubleshooting
Decision trees for subscription, branding, analytics, API access, Windows TUN, Android permissions, HWID, and route quality.
Open troubleshooting →Security & privacy
Data boundaries, consent, coarse context, retention, deletion, tenant isolation, credential handling, and incident response.
Open security guide →No guide matches that search. Try a platform, task, metric, or error such as “Windows”, “branding”, “latency”, or “403”.
Safe launch path
From approval to production.
The order matters: approve identity first, test on a restricted squad, then expand while watching quality.
Store the one-time credentials
Place the provider key and branding token in an approved secrets manager. Never put either in chat, source control, screenshots, URLs, or tickets.
Configure one Remnawave External Squad
Add the public provider slug and opaque branding token only to the NODIF client response rule for a small internal canary.
Verify branding and connection behavior
Check subscription states, HWID behavior, support/renewal links, route discovery, connection, and safe failure behavior on representative networks.
Expand gradually and measure
Increase the assigned cohort in stages. Compare success, latency, jitter, loss, throughput, and error stages only where the privacy threshold is met.
Capability truth
What is available now.
This matrix prevents sales, support, and technical teams from promising features before they are released.
| Capability | Status | Operator guidance |
|---|---|---|
| Android signed direct-download app | Live | Use the verified NODIF download and compare its SHA-256 when distributing outside Google Play. |
| Windows x64 client | Signing gate | The build exists but should not be publicly distributed until trusted Authenticode signing is complete. |
| macOS client | Build gate | Requires a Mac, Apple Developer signing, and notarization before distribution. |
| Signed provider branding | Live | NODIF approves and publishes the live profile. Provider-side self-service changes require moderation and must not replace the live profile prematurely. |
| Aggregate Intelligence analytics | Live | Available to active entitled plans and scoped keys. Every returned cohort must meet the server’s disclosure threshold. |
| Provider-scoped API keys and branding-token rotation | Live | Use least-privilege scopes; credentials are displayed once and hashes are stored server-side. |
| Custom account-status messages | Not released | Use Remnawave’s own subscription status/remarks behavior. Do not expect NODIF signed branding to deliver custom status copy yet. |
| Provider-visible audit history and team UI | Not released | NODIF keeps internal control-plane audit metadata; a provider self-service audit view is not currently available. |
| Provider-managed node/entry/balancer catalog | Not released | Some aggregate dimensions can be empty or opaque. Catalog registration and full entry/balancer attribution are not provider self-service features yet. |