One engine runs every app we make.
Vidus6 builds consumer apps — 17 so far. All of them run on Vidus Engine, a platform we built ourselves. It watches our stores, our ads, our revenue and our reviews; its AI prepares the next move; one of us approves it.
- App Store Connect
- Google Play Console
- Apple Ads
- Meta Ads
- Google Ads
- RevenueCat
- Reviews & support
- Our apps' analytics
Vidus EngineOne engine. One timeline. Our AI on the same data.- Store text in 39 languages
- Screenshots for every market
- Prices in both stores
- Ad bids, budgets and pauses
- Ad optimisation across networks
- Review replies
- Remote settings & forced updates
- Daily automated summaries
Everything in one place.
Before the engine, every app meant eight dashboards: two store consoles, three ad networks, sales, support, analytics. None of them talked to each other. Now every ranking, price, review and sale for every app sits in one place, on one timeline.
- Rankings, prices, reviews and sales for every app, side by side
- Eight systems read for us every morning
- Every change on one timeline
Germany: “versteckte kamera” back to #4 · installs +18% this week
Screenshot set B live in 39 languages · conversion up 1.2 pts
A rival changed its Japanese subtitle · we still rank #2 for “card scanner”
New store text approved for 12 markets · written as drafts, awaiting release
AI prepares. We decide.
We ask a question in plain words. The AI reads the stores, the ads and the reviews, explains what happened, and prepares the fix. Nothing changes until one of us approves it.
- The AI reads first and changes nothing on its own
- Every change is shown to us before and after
- Releases and store submissions are always done by a person
Why did NSpy drop in Germany last week?
A rival changed its German subtitle on Sep 14, and scans fail since 2.4.0. I drafted a new subtitle to win the ranking back.
Every change is measured.
Most teams change a price or a screenshot and never learn what it did. We write every change down, and a week later we see what it changed — a new subtitle, a lower bid, a screenshot set.
- The week before and the week after, side by side
- Made by us, by the AI, or spotted in the store
- One card per change, no report to build
Installs per day · Germany
Before
312
After
790 +153%
New German subtitle · approved by our team
We add apps. Not cost.
Our newest app costs us the same to run as our first. That is the whole point: one engine does the launching, the watching and the fixing for all of them, so every new app starts with everything the others learned.
- One engine launches, watches and fixes all of them
- Every new app starts with what the others learned
- Our team ships a portfolio, not one app at a time
Trusted with the keys. Not with the decisions.
We gave our AI a useful connection to the work, with limits we set. It reads everything and changes nothing on its own.
AI prepares · we decide
Our store passwords and keys never leave our servers
The AI works through the engine. It sees rankings, spend, reviews and sales, never credentials.
Every change is shown to us first
Before and after, side by side. It happens only when one of us approves, and the record says who.
Releases are made by people
Store submissions and app releases are always done by a person on our team.
Works with any AI
The engine speaks the open Model Context Protocol, so any assistant that does can drive it.
- Claude
- Claude Code
- Cursor
- Gemini
- Mistral
- Perplexity
- DeepSeek
- Ollama
- GitHub Copilot