Open source, self-hosted ASO tool · AGPL-3.0
The same open source ASO tool that runs the hosted service, on your own server: App Store and Google Play keyword rank tracking, competitor diffs, reviews, the Action Center and the MCP server. Docker Compose, two variables, about five minutes.
Needs Docker, about 2 GB of memory and 5 GB of disk. No account with anyone.
$ curl -fsSLO https://raw.githubusercontent.com/AsoBeast/asobeast/main/docker-compose.pull.yml$ printf 'POSTGRES_PASSWORD=%s\nAUTH_SECRET=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env$ chmod 600 .env$ docker compose -f docker-compose.pull.yml up -d --waitSelf-host
Published images from GHCR, no clone required. Prefer building from source? The README has that version too.
Docker with Compose, roughly 2 GB of memory and 5 GB of disk. Postgres 18, Redis 8 and the app come up together.
Open localhost:3001 and create the owner account. Registration closes automatically once it exists.
Paste an App Store or Google Play URL. The first rank pass is scheduled the moment the import finishes.
Only two variables are required, POSTGRES_PASSWORD and AUTH_SECRET. Everything else has a working default.
Built in the open
AsoBeast is AGPL-3.0 with no open core. The hosted service runs the same code you can read and clone, so you pay for hosting, never for a locked feature, and you can always take your data and leave.
Start a trial, paste a store link, done.
Docker Compose, two variables, about five minutes.
Self-hosted: no telemetry, and nothing leaves your server until you configure an integration such as webhooks, email, OpenAI assistance, Apple Ads popularity, a store status check, an egress proxy or offsite backups.
AGPL-3.0 with no open core. Every feature the hosted service runs is in the repository.
Registration closes automatically once the owner account exists.
Backups, restore and upgrades are documented, and the 1.x line keeps a compatibility promise.
Same software
Every store request runs on the machine hosting AsoBeast. Pick who runs that machine.
| What differs | Self-hostedyour serverRecommended | AsoBeast Cloudfrom $10 a month |
|---|---|---|
| Where store requests run | Your machine | AsoBeast’s datacenter proxies |
| Who sees your keyword list | You | AsoBeast, under its privacy policy |
| Cost | Your hosting bill | $10 or $99 a month |
| Apps and keyword markets | Unlimited | 5 and 1,000, or 50 and 10,000 |
| Rate limits | None | Per plan |
| AI calls | Unlimited on your own OpenAI key, unless you set a cap | 200 or 2,000 a month |
| Upgrades and backups | You | AsoBeast |
| Features | Every feature | Every feature |
| Licence | AGPL-3.0 | Same code, AGPL-3.0 |
Questions
Docker Engine with the Compose plugin on linux/amd64 or linux/arm64, roughly 2 GB of free memory, 5 GB of disk and outbound HTTPS. Only port 3001 is published. Two environment variables are required, POSTGRES_PASSWORD and AUTH_SECRET; everything else has a working default.
Yes. Rank tracking, competitors, reviews, audits, the Action Center, alerts, the AI features, the REST API and the 23-tool MCP server are all in the repository. There is no open core and no paid tier of the software.
Apps and keyword markets are unlimited and there are no rate limits; competitors stay capped at 10 per app. Store rate limits, not AsoBeast, cap daily checks: at the default limits one address covers roughly 20,000 keyword markets on the App Store or 1,800 on Google Play, and the settings page shows the request budget before you add a market.
You can run, study, modify and redistribute AsoBeast for free, including for commercial use. If you run a modified version as a network service, the licence asks you to offer that modified source to its users. Running an unmodified copy for your own apps or your clients’ apps has no such obligation.
Images are published to GHCR with version, minor, major and latest tags. Pull, restart, done; the 1.x line keeps a compatibility promise. Backups and restore are documented under Operations in the docs. On the hosted service both are done for you.
No, unless you turn it on. There is no telemetry, and nothing leaves the machine until you configure an integration such as webhooks, email, OpenAI assistance, Apple Ads popularity, a store status check, an egress proxy or offsite backups. Unless you configure an egress proxy, every store request runs from the machine hosting AsoBeast.
Both directions work through the exports and the import flow; a one-click migration is not offered today. Apps move by store link, and keyword lists export as CSV and paste back in, up to 200 phrases at a time. Ranking history does not transfer.
The documentation at docs.asobeast.com covers installation, concepts, guides, operations and the API. Bugs and feature requests go to GitHub issues. Security reports go through SECURITY.md in the repository, never a public issue.
Clone it, run it, and keep every keyword you have ever tracked.