Your service's subscriptions
Import, refresh, name, logo and plan details. Use Remnawave or your own panel with a supported subscription format.
DODO / FOR PROVIDERS
Give customers a subscription link — they can add it to DoDo, choose a server and connect. The app gets your service name, logo, expiry and support links from your server. No infrastructure migration or panel access sharing is needed.
Provider registration is open in early access. Full production launch coming soon. Sign in with Google, with no plans or payments. Automatic subscriber linking in the app is a separate integration pilot.
Import, refresh, name, logo and plan details. Use Remnawave or your own panel with a supported subscription format.
Register your service with Google, verify the domain and prepare branding and drafts. Delivering content to subscribers requires separate approval and integration.
Subscription ownership verification, targeted notifications and server selection through your panel's API.
01 / SUBSCRIPTIONS
An HTTPS link is enough to import subscriptions. DoDo dashboard registration is not required.
Server link lists, Base64 and compatible Xray JSON. Full JSON profiles preserve their own DNS, routing rules and balancers.
Formats and examplesSend the name, logo, support, renewal page, expiry and traffic in response headers. DoDo displays them on the subscription card.
HTTP headersWhen requesting a subscription, iOS and Android send HWID, model, OS and OS version. Your panel can use these details to limit the number of devices. The limit itself is enforced on your server.
Device data and limitsYou can use your own panel. DoDo reads subscriptions directly from your server. No administrative API token or migration to Remnawave is needed. Supported protocols and configuration limitations are listed in the documentation.
Issue protected DoDo crypt1 links. iOS 2.2.0 and Android APK 2.2.0 support dodoapp://crypt1/…: the generator encrypts an existing HTTPS subscription address, and the app decrypts it on the device without calling the DoDo API. Standard lists, Base64 and full JSON keep working without panel changes. An SDK and CLI for Node.js 24+ are available for bots. AGE1 — encryption of the server response itself — can be configured separately. Registration, premium access and providerid are not required for these formats. A protected link remains an access key: do not publish it. On Android, use the clipboard or manual entry: crypt1 QR recognition on some HUAWEI devices is still being improved. These formats are not yet available in published macOS; Windows is in preparation.
Prepare a fallback subscription address. iOS 2.2.0 and Android APK 2.2.0 support fallback-url: if the primary source is temporarily unavailable, DoDo tries a previously saved fallback for the same user. This works with normal lists, Base64 and JSON, including with crypt1. Send a full fallback HTTPS address with the required path and token — the app does not invent mirrors. The fallback must be obtained during a successful request to the primary address: if it is unavailable on first import, a backup address cannot be discovered from its response. Registration and premium access are not required; the mechanism is not yet available in published macOS.
02 / SUBSCRIPTION APPEARANCE
Add the required headers to the subscription server response. All fields are optional; the example below uses demo values.
profile-title sets the name; x-dodo-provider-logo-url sets the logo address. Support and renewal page links add the corresponding buttons to the app.
profile-update-interval sets the refresh interval: an integer number of hours from 1 to 168. The app checks whether refresh is due when it can make network requests; the system does not guarantee background execution at an exact time.
In subscription-userinfo, traffic is in bytes and expire is a Unix timestamp in seconds.
EXAMPLE RESPONSE HEADERS
profile-title: Example Provider
profile-update-interval: 2
x-dodo-provider-logo-url: https://example.invalid/logo.png
support-url: https://example.invalid/support
profile-web-page-url: https://example.invalid/account
subscription-userinfo: upload=0; download=0; total=107374182400; expire=1893456000Do not put real UUIDs, passwords, HWID, API tokens or secret links in public examples or logo URLs.
| Your setting | HTTP response header | In the app |
|---|---|---|
| Service name | profile-title | The subscription card name. For Cyrillic and other non-ASCII characters, you can use base64:… with UTF-8 encoding. |
| Logo | x-dodo-provider-logo-url | Logo in the top section. A public HTTPS image, not the app's store icon. |
| Support and dashboard | support-urlprofile-web-page-url | Support and renewal page buttons. |
| Expiry and traffic | subscription-userinfo | Status, expiry date and volume. Values are set by your server. |
| When to refresh the subscription | profile-update-interval | Update check interval in hours, subject to OS background execution limits. |
| Fallback address | fallback-urlproviderid — optional | A full backup HTTPS address for the same subscription. If providerid is specified, the fallback response must return the same value. This is not payment verification or access to the DoDo dashboard. |
| Announcement | announce | Text on the subscription card. It does not create a story or send a notification. |
| Traffic rules | routing / autorouting | Routing for this subscription. Rules can also be supplied inside full Xray JSON. |
Headers are sent with a successful response at the HTTPS subscription link. Value formats, supported body comments and limitations are described in the header reference.
The name and support contact help track service statistics. In iOS 2.2.0, DoDo groups reports by public profile-title and sanitized support-url. Reports include device model, iOS and app version, and saved configuration count. Key addresses, configurations themselves, HWID and traffic content are not sent in these reports. This counts DoDo installations that submitted data, not all your subscribers or online users.
Analytics are enabled by default; a previously saved opt-out is respected. Users can disable sending and request data deletion in the app under “Settings → Privacy Policy”. No more than two sending attempts per 24 hours; statistics server unavailability does not block import or VPN. Reports are currently available only to the DoDo developer — separate provider access to their own reports is in preparation. A service name and support contact do not prove service ownership or grant dashboard access.
03 / PROVIDER DASHBOARD
Create a dashboard yourself with Google. Registration is free; each provider works only with its own service and materials.
The owner manages the service and invites editors. Editors prepare materials; the owner publishes stories. Other providers cannot access your settings or materials.
Enter the name, logo, support and website. The mockup shows how they look in light and dark themes. The accent selected in the mockup is currently for preview only — iOS uses the system color.
DoDo's own name and icon in the store and on the device remain unchanged.
Add an image or short video, title and caption. Save it as a draft, preview it before publishing or move it to the archive. In-app display is currently available to testers.
Feature availabilityPublic branding and stories — no module installation. Create a dashboard with Google, verify the exact subscription domain using DNS TXT, wait for DoDo approval and add x-dodo-provider-id from your dashboard to a successful HTTPS subscription response. No signing key or panel API token is needed. Preparing settings does not confirm server deployment, publication of a new app version or iPhone testing.
| Type | Format | Limitations |
|---|---|---|
| Image | JPEG, PNG, WebP | Up to 10 MiB. Images are saved as JPEG after upload. |
| Video | MP4 | Up to 20 MiB and 30 seconds. Files are validated and processed on the server. |
| Publication | Title and short caption | Title up to 80 characters, caption up to 500; duration 12 or 24 hours. |
04 / PUBLIC CONTENT
Public content is linked to the service's exact domain and ID. It is not verification of an active or paid subscription, nor a private audience.
x-dodo-provider-id — the UUID from your own dashboard. The app accepts it only from a real successful HTTPS response on the exact subscription host, not from body comments, errors or redirects.
Valid DNS TXT verification and DoDo approval are required. A signed connector is not required for public branding and stories.
Branding and posts are served separately through /api/provider-content/v1. Publishing stories requires valid DNS verification and service approval. Display requires a compatible app version.
A public ID does not prove subscriber payment, create a verified private audience or authorize targeted campaigns. Material intended only for paying subscribers must not be posted here.
Verify the exact domain with DNS TXT. The dashboard issues a unique record and checks it. Manual approval history is stored separately and is not DNS verification. Verifying one host does not cover neighboring subdomains. Public content does not change the subscription body, HWID policy or VPN operation.
The optional signed protocol remains separate from public content. DNS does not replace subscriber verification. The panel must check the subscriber and device, then return dynamic signed verification for x-dodo-subscriber-challenge in x-dodo-subscriber-token. One shared permanent string for all users is not allowed; a public ID does not weaken these checks.
Targeted campaigns require a separately verified audience and user permission; ready-to-use push delivery is not promised here. Keep the panel's administrative token, private signing key and passwords only on the server. They must not be sent in subscriptions, apps or public pages.
Advanced protocol and limitations05 / YOUR PANEL STAYS WITH YOU
Your servers and subscriber management stay with you. DoDo needs no administrative panel access to connect to VPN.
Deliver subscriptions in a supported format. For full Xray JSON, send the entire profile: DNS, routing, balancers and all related settings.
Check the formatAdd x-dodo-provider-id to an existing successful HTTPS response. Public branding and stories require no new endpoint, signer or full administrative panel API. Use Remnawave or your own system with configurable HTTP headers.
Subscriber verification and device policy stay on your server. A public ID does not verify their outcome.
The map shows the distribution of subscription requests by country, approximate city group and carrier network (ASN) for 24 hours, 7 or 30 days. A Remnawave data source is connected manually with read-only permissions; custom panels require a separate connection.
The map does not show exact locations or online user counts. Small groups are hidden; source IPs and HWID are not sent to the dashboard.
Routing geofiles are already bundled with the app. geosite.dat and geoip.dat let you define rules by domain and IP categories. They are not used to build a subscriber map.
06 / SERVER AUTO-SELECTION
Supply a balancer in a full Xray JSON profile. DoDo's separate auto-selection button is currently hidden on iOS; balancing through the panel API is still in development.
| Method | How it works | Status |
|---|---|---|
| Xray balancer | Define selection rules inside the full JSON profile: tags, observatory and balancers. DoDo uses the compatible configuration in full. | Available |
| DoDo auto-selection | The separate measurement-based server selection button is temporarily hidden on iOS. Balancers inside full JSON profiles are not disabled by this. | Currently hidden on iOS |
| Auto-selection through the provider API | The panel will be able to recommend a server based on its load, priorities and routes available to the subscriber. | In development |
Ping and speed are different measurements. In iOS 2.2.0 and Android APK 2.2.0, standard TCP shows the measured connection time without division. On Android, a simple JSON with one TCP server is also checked by a direct connection; Hysteria, balancers and complex profiles are checked via HTTP. HTTP GET and HEAD test a request through the server configuration. Only the estimated DoDo Ping mode divides the HTTP GET result by 3.3. TCP or ICMP may respond even when a server's VPN is not working, and a successful HTTP measurement does not guarantee download speed or that every route works.
07 / GETTING STARTED
Start with a test subscription. You can connect the dashboard and stories later — VPN operation is unaffected.
Prepare an HTTPS link with a server list, Base64 or Xray JSON. Test import, refresh and connection. Do not use live keys in public examples.
Quick startAdd the name, logo, expiry, traffic and support links to response headers. Make sure the subscription card looks as expected.
Sign in with Google, enter your service name and support contact. Verify the exact domain using the TXT record from the dashboard. Then you can prepare branding and stories.
Open provider dashboardAdd x-dodo-provider-id from your own dashboard to a successful HTTPS subscription response. After DoDo approval and DNS verification, prepare public branding and stories. No module or key pair is needed; display requires a compatible app version.
Integration stepsDODO PROVIDER CONSOLE
Install the panel with Docker Compose and open it on your own HTTPS domain. Sign in with Google on the DoDo website, confirm the installation and manage your service's branding, DNS and stories. The central API checks permissions for every request and does not expose other services' data. No Remnawave module or VPN node access is required.
Statistics in 0.1.1 are separated by provider ID and verified domain: models, OS and app versions, reports for 1/7/30 days. An updated compatible iOS client is required; older versions and Android do not yet send this scope. These are devices with reports, not people online or paid subscriber counts. Data and published files remain with DoDo. VPN operation does not depend on the dashboard.
08 / AVAILABILITY
Core key features are available without registration. The free dashboard is open in early access; full production launch and targeted campaigns are being prepared separately.
Working — ready to use. In testing — access by invitation. In development — not yet available. Not supported — not part of DoDo's current features.
| Feature | Status | What to know |
|---|---|---|
| Subscription import and refresh | Working | Works without a dashboard. Formats and protocols are listed in the documentation. |
| Protected DoDo crypt1 links and AGE1 | iOS and Android APK | Available in iOS 2.2.0 from the App Store and Android APK 2.2.0. For crypt1 with a normal response, no panel changes are needed; server-side AGE encryption is configured separately. On some HUAWEI devices, paste the protected link from the clipboard or enter it manually instead of using QR. How to set up. |
| Name, logo, expiry, traffic, links | Working | Configured using subscription server response headers. |
| Team, roles, branding and preview | Early access | Available after dashboard registration. The mockup accent color does not yet apply on iOS. Public branding requires DNS, DoDo approval and x-dodo-provider-id, but no signed connector. |
Fallback subscription: fallback-url | iOS and Android APK | Available in iOS 2.2.0 and Android APK 2.2.0: normal lists, Base64 and JSON. providerid is optional and does not verify payment. Published macOS does not yet have this mechanism. How to prepare the server. |
| Service statistics by name and support contact | iOS and Android APK | iOS 2.2.0 and Android APK 2.2.0 send limited statistics by profile-title and support-url, respecting the user's choice. Sending can be disabled in the privacy policy. Provider ID tracking for the provider dashboard is not yet connected on Android. How statistics work. |
| Story editor and media upload | In testing | Drafts, preview, posts lasting 12 or 24 hours and archive. |
| In-app branding and stories | In testing | Available on separately enrolled iOS devices. The simple public method requires DNS, approval and an ID header, with no module. This description does not confirm a new production version or a live test. |
| Automatic subscriber verification | In development | Will require subscription verification and a signed provider server response. |
| Notifications to your subscribers | In development | Targeted delivery after subscription verification and user consent. |
| Private stories for verified subscribers | In development | A separate task involving subscription verification. Not part of public stories and not enabled by a provider ID alone. |
| Country, city group and ASN map | In testing | The data source is connected separately. The map shows aggregate statistics only. |
| Auto-selection through the panel API | In development | Server selection using provider data on load and available routes. |
| Self-service provider registration | Early access | Google sign-in, your own dashboard and domain verification with DNS TXT. Free, with no plans or payments. Full production launch coming soon. |
| Other clients' Lite Mode and Premium API | Not supported | Other clients' commands for changing themes, forcing settings, managing HWID and the premium-url button are not executed. |
| Happ encrypted links and commands | Not supported | Compatible JSON subscriptions can be read; Happ crypto and Happ deeplinks are not processed. |
| Platform / version | Features | Note |
|---|---|---|
| iOS · 2.2.0 on the App Store | Import and refresh, full JSON profiles and balancers, crypt1 and AGE1, fallback address, HWID, ping modes, routing, geofiles, logs and error reports with user consent. | For iOS 15 and later. Analytics controls are in the privacy policy. Dashboard and stories are in testing; targeted delivery to all subscribers is not yet available. |
| Android · APK 2.2.0 (2107) | Full JSON and balancers, crypt1 and AGE1, fallback address, key details and refresh interval, routing, geofiles, TCP ping without division, MTU and IPv4 / IPv6, live logs and voluntary error reports. | APK dated November 10. The Google Play update will be announced separately. On some HUAWEI devices, use the clipboard or manual entry instead of QR for crypt1. Stories and provider notifications are not yet enabled on Android. |
| macOS · 2.0.8 on the Mac App Store | The app is available on the shared iOS App Store page. | The previous version, 2.0.8, remains available for Mac. |
| Windows · coming soon | A Windows version is in preparation. | The installer link will appear after release. |
In the next iOS update — local SOCKS protection. These changes are not yet published on the App Store. Internal connection credentials are generated for each session and are not carried over to another provider. Usable local credentials from a full profile are preserved. Remote SOCKS server authentication remains unchanged; no node reconfiguration is required. Compatibility depends on profile parameters — security requirements are not disabled just to connect.
Protection and new diagnostics detailsError reports are sent with user consent. They go to the DoDo developer, not the provider dashboard. Providers do not gain access to shared diagnostics or information about other services. Reports help investigate app failures. Not all system crashes and hangs appear automatically. HWID headers in subscription requests go to your server separately.
What a report containsSTART NOW
The documentation covers supported formats, example headers, import links and routing rules.