Overview
NATE VPN operational status
Owner
Customers—
Online—
Devices—
Published Catalog—
System
Checking…
Connection Catalog
Loading…
First-run setup
Get a fresh NATE deployment ready for its first real app login.
Checking…
Recommended order
1 · VPN Control
Create a network and at least one server profile. Add a payload only when that profile needs one.
2 · Publish
Publish the first usable catalog so the Android app has a verified connection generation to download.
3 · Customer
Create a standard customer login for the first phone test.
4 · Production trust
After staging works, approve the release certificate and complete Deployment checks before enabling production enforcement.
Create customer
Creates a standard NATE VPN customer account.
Selected customer
Click a customer in the table or enter a code / username.
No customer selected.
Customers
Click any row to manage that account.
| Username | Code | Days | Status | Device | Last seen |
|---|
Online devices
Heartbeat and compatible presence records.
| Customer | Device | App | Network / Server | IP | Seen |
|---|
| Account | Device | Model | App | IP | Last seen |
|---|
Catalog status
Loading…
Force publish creates a required catalog release even when the current draft has no new changes.
Release history
Latest 20 catalog releases.
New network
Networks
New server profile
A server profile is the customer-visible VPN endpoint. Its Xray JSON is the actual connection runtime; a payload profile is optional.
When editing an existing profile, use “Load config” before changing its runtime JSON.
Server profiles
These are the endpoints shown to the app.
New payload profile
Payload profiles
Config cache
Loading…
Version gate
Load this page to view impact.
NATE VPN APK update
Official package: com.natevpn.mobile
Loading…
In-app advertising
Ads are controlled independently from VPN configs. Turning this off removes managed ad placements from the app without republishing the VPN catalog.
Loading…
Google Mobile Ads
The Android release must first be built with your AdMob application ID and consent integration. These unit IDs are stored now so the production ads build can change placements remotely without touching VPN configs.
Show at most once after this many successful VPN connections. The app still waits for privacy consent and a loaded ad.
Use the managed NATE banner provider when you want a simple first-party promo/card with no third-party ad SDK request.
Send notification
Notes
Notifications go to the NATE VPN customer inbox/Android notification flow. They are separate from catalog updates, which are generated automatically when you publish a connection catalog.
Notification history
Security incidents
Resolve alerts or take device/account action.
Android release identities
Approve public SHA-256 certificate fingerprints for official NATE APK builds. This does not store private signing keys. Deployment fingerprints remain the recovery baseline; managed fingerprints may be changed here without restarting the API.
Effective client trust
Loading…
Deployment readiness
Checks the NATE API production prerequisites without displaying secret values.
Loading…
Database backup
Create a consistent snapshot of the active NATE VPN SQLite database.
Loading…
Recovery note
Keep database backups together with your server environment values and NATE ownership/recovery material. The database backup does not contain your Android signing private key.
A restore operation is intentionally not exposed in the browser. Restores should be performed during maintenance with the API stopped so a damaged or wrong database cannot be uploaded over a live service.
Console activity
Recent owner and partner actions. Sensitive request bodies and credentials are never shown here.
| Time | Actor | Action | Target | Result | IP |
|---|
Add console account
Available account types are based on your current access scope.
My login
| Name | Username | Role | Status | Actions |
|---|