Guideline 4.3(a) — Design — Spam
Rejection 1 of 6
A business, ready to runMeerGuard: 11,381 users on this exact stack
Your own VPN service, turnkey — apps, backend and payments
Assembled to fit: iOS and Android apps, a backend that controls payments, panel setup, a site and AI support. The same stack MeerGuard runs on.
- Around 8 apps already shipped to the stores
- Modular — you pay for the parts you need
- Everything is handed over as your property
How it fits together
Four layers. We build the ones you do not have and connect them to the ones you do.
01
Servers and VPN panel
Protocols, configs, keys. We set the panel up — basic, or tuned for restrictive networks.
02
Backend
Subscriptions, Apple and Google payment control, key issuing, security.
03
Client apps
What your customer actually uses. Any combination of channels.
- iOS
- Android
- Telegram
- Website
04
Payments and your revenue
The customer pays in the app, in Telegram or on the site — the money goes to you.
What you cannot see from the outside
A bot with a pay button is a weekend. What follows is the part the tutorials skip — we went through it on our own service.
App Store review
Guideline 4.3: a saturated category and "similar to others in code, description or concept". VPN hits both — we were rejected six times.
The niche moves under you
What gets a build approved changes: the approach that worked last release does not work on the next one.
A company, D-U-N-S and an org account
Publishing as a business requires an organisation account: a registered company and a D-U-N-S number.
Configs that actually work
Off-the-shelf configs do not work in Russia. When they do, it is usually on Wi-Fi only.
Five layers below the surface
Client on the device, configs on the server, network and protocols, backend with payments and an admin panel, support. From outside you only see the pay button.
Users leave without a word
When it breaks in the evening they do not write to support — they cancel. Retention here costs more than acquisition.
Rejection 1 of 6
Red closes this letter and brings up the next, yellow lists all six, green shows what got that build through.
What the service is assembled from
Take all of it or only the missing parts — you decide the scope.
iOS app
Native Swift, prepared for App Store submission.
Android app
A Google Play build with everything review asks for.
Backend and payment control
Subscriptions, Apple and Google receipt validation, key issuing, security.
Payments in Telegram
Selling subscriptions and issuing keys in the bot — the channel the audience already uses.
VPN panel setup
Panel, protocols and configs, plus a mode for difficult networks.
Website
From a landing page to a site with an account area, payments and SEO.
Admin panel
Users, servers and tariffs in one place.
AI support bot
Answers customers and closes the routine tickets without you.
What your service will cost
Answer a few questions and get a ballpark price right away — no call required.
Build your service
Answer step by step — the price comes at the end
Step 1 of 5
Which apps do you need?
You can pick both platforms — together they cost less
A live product, not a mockup
This is MeerGuard VPN — our own service on the same stack. Screenshots from the App Store.
One-tap connection 
Server picker and paid subscription 
Split tunnelling 
Settings, profiles and purchase restore
What is behind those screens
The part a store listing never shows: where the money is counted and where the traffic actually runs. Both are from our own service, with the revenue figures in the admin panel painted out.
Admin panel: MRR, revenue, subscriptions, plans, referrals 
Node panel: traffic, users online, node load
Why only our own product is shown here
Client work is shown on a call: other people’s services are other people’s brands and revenue, and we will not publish them without permission. Our own product is fully open — you can download it and check.
See MeerGuard liveHow the work goes
Enquiry and a call
You send an enquiry, we get on a call and go through the idea, the brand and the details.
Fixing the scope
We work out what we build and what you already have. Quote and timeline in writing.
Development
We build the apps, backend, panel and site under your brand.
Publishing and handover
We publish to the stores and hand over the code, accounts and access.
The service runs
Payments, key issuing and support run themselves. You do the marketing.
Proof
The same stack runs our own service
MeerGuard is ours, built on exactly this set. The numbers come straight out of its database.
- users in 10 months on our own VPN
- 11,381
- successful payments from those users
- 7,062
- of signups convert to a payment
- 39%
Data as of 13 August 2026 · Full MeerGuard case study
Frequently asked
How long does a launch take?
It depends on scope. A client app with no backend is weeks; a full service with backend, panel and site takes longer. Timelines are fixed in writing after we talk.
Will the apps definitely pass review?
Reviewing VPN apps is its own skill and we have been through it more than once. What gets you through is correct packaging and working the appeals — both are part of the job, not a promise.
Why pay for a developer account?
If you already have Apple Developer and Google Play Console, we publish on yours and there is nothing extra. If not, we register them and hand them over.
Who owns the service after handover?
You do. Apps, backend, site and accounts become your property.
Do I need a technical team?
No. Payments, key issuing and support run themselves. You need a team only if you want to grow the product further.
What are the running costs?
Mostly servers. For reference, our own infrastructure costs about ₽35,000 a month. The exact figure depends on user count.
Tell us what you already have
We will put together a scope for your case and give you a range. We reply within 10 minutes on Telegram.