What is AsoBeast?
AsoBeast is an App Store Optimization (ASO) tool and keyword rank tracker for the Apple App Store and Google Play. It imports a listing, tracks keyword rankings daily to a depth of 200, watches competitors, reviews and metadata, and turns that history into a prioritized queue of ASO work. This repository is the free, open source edition that you run on your own server, and the hosted service at asobeast.com runs the same code.
Every store request runs on the machine hosting AsoBeast as an ordinary public search or page request, so Apple and Google see each tracked phrase the way they see any search. You sign up with no ASO vendor, buy no API key, and share your keyword list with nobody. Beyond those store requests, your data stays in your deployment unless you explicitly enable an outbound integration such as webhook alerts, email, OpenAI assistance, Apple Ads search popularity or store status updates.
Who is AsoBeast for?
AsoBeast is built for people who ship apps and want their ASO data to stay theirs: indie developers, small studios and agencies tracking a handful of apps across several storefronts. It fits if you want ASO tracking without a per keyword subscription, need the data on your own infrastructure, or want to query your ASO history from an agent or a script instead of a dashboard. It collects from the public store endpoints at a deliberately modest rate, so it suits a portfolio measured in apps rather than hundreds. See who AsoBeast is for.
Why AsoBeast?
- No accounts, no vendor API keys. AsoBeast collects from the public store endpoints at a deliberately modest rate. You need Docker and nothing else.
- Your keyword list stays yours. It lives in your database and is never sent to an ASO vendor, so no competitor intelligence product assembles it from your searches. The stores only ever see one search at a time.
- Both stores as one tracking entity. One app row tracks keywords across many storefronts, so
usanddeare markets on the same listing rather than two subscriptions. - Every score shows its evidence. Popularity and difficulty carry their source, calculation version, capture date and confidence, so you can argue with a number instead of trusting it.
- Deterministic recommendations. Fifteen rules turn stored history into an explainable work queue. AI is optional garnish that can summarize an action, never invent or reorder one.
- AGPL-3.0, no open core. Every feature the hosted service runs is in this repository.
Features
A guide for each of these lives in the documentation.
Quick start
One-click deploy
Runs the published images on Railway with PostgreSQL and Redis, and generates every secret for you. See deploy on Railway.
Docker Compose
You need Docker with Compose, roughly 2 GB of memory and 5 GB of disk.
git clone https://github.com/AsoBeast/asobeast.git
cd asobeast
printf 'POSTGRES_PASSWORD=%s\nAUTH_SECRET=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
chmod 600 .env
docker compose up --build -d --wait
Open http://localhost:3001 and create the owner account. Registration closes automatically once it exists. Safari does not keep the session cookie over plain HTTP, so use Chrome or Firefox for a local evaluation, or see signing in returns to the sign in form. Import a store URL and keyword tracking starts immediately.
Prefer published images to a build? docker-compose.pull.yml runs the same stack from GHCR without a clone:
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 --wait
Full walkthrough: quickstart. Image tags, pinning and upgrades: run a published release.
Connect an AI agent
Every instance serves a Model Context Protocol endpoint. Create a personal API token on the settings page, then point Claude Code at it:
claude mcp add --transport http asobeast https://your-host/api/backend/mcp --header "Authorization: Bearer asob_…"
Ask it which keywords dropped this week, which competitor entered the top 10 or what the Action Center wants done first. Configuration for Claude Desktop, Cursor, VS Code, Gemini CLI, Windsurf and the local stdio server is in set up the MCP server, and MCP recipes has prompts to start from.
How AsoBeast compares
A hosted AsoBeast is a separate product built from this same repository. Self-hosted installations get every feature.
Tech stack
pnpm and Turborepo, TypeScript strict throughout, NestJS, Prisma, PostgreSQL 18, BullMQ, Redis 8, Next.js with Tailwind, Docker Compose.
Contributor setup, architecture and the module map: local development and how AsoBeast works.
Configuration
Every environment variable, with defaults and what each one changes, is documented in the configuration reference. apps/api/.env.example and apps/web/.env.example are the authoritative lists in the repository.
A default installation needs two variables, POSTGRES_PASSWORD and AUTH_SECRET. Everything else has a working default.
FAQ
What is App Store Optimization?
App Store Optimization is the practice of improving how an app ranks and converts in App Store and Google Play search. It covers keyword targeting in indexed metadata fields, competitor positioning, ratings and reviews, and category performance.
Does AsoBeast need an App Store Connect or Google Play Console account?
No. AsoBeast reads public store data, so you can track any app including your competitors. It never asks for store credentials or an ASO vendor API key.
Which app stores does AsoBeast support?
Both the Apple App Store and Google Play. Apple indexes a title, a subtitle and a private 100 character keyword field. Google Play indexes a title, an 80 character short description and a long description, so subtitle and keyword field stay Apple only concepts. See stores.
How often does it check rankings?
Once a day by default, on a UTC cron you control. Rank checks capture position to a depth of 200, and a position of null means checked and not found within that depth rather than zero. See positions.
Can I track more than one country?
Yes. An app is imported once, and keyword tracking carries its own storefront, so one listing can track keywords in many markets at once. Each added market multiplies daily store requests, and the settings page shows a budget card that estimates the fan-out. See countries and markets.
Is any of my data sent anywhere?
Only the store requests themselves, which send each tracked phrase to the App Store or Google Play as an ordinary search, from your own address or through a proxy provider if you configure one. Beyond those, webhook alerts, SMTP email, OpenAI assistance, Apple Ads search popularity and the store status poll are the only outbound integrations, and each is off until configured. There is no telemetry. See what leaves your deployment.
Can I connect AsoBeast to Claude or another AI agent?
Yes. AsoBeast ships a Model Context Protocol server with 36 read tools, available as a local stdio process or as a remote endpoint on your instance. Every connection needs a personal API token and reads by default. Five more tools that change keywords, competitors and actions are listed only to a token you give the write scope. See MCP.
Is AsoBeast really free?
The software is, entirely. It is AGPL-3.0 with no open core and no feature held back for a commercial edition, so a self-hosted installation has everything. A hosted service built from this same repository is charged for the hosting it uses, never for features. If you run a modified version as a network service, the AGPL asks you to offer that modified source to its users.
Documentation
Limitations
Worth knowing before you rely on it:
- Scores are store-specific estimates. Popularity and difficulty come from different public evidence on each store, so the numbers are not comparable across stores and are not a substitute for first-party acquisition data.
- Scrapers can break. AsoBeast reads public endpoints. When a store changes one, a parser can fail. Failures fail the job, which BullMQ retries with backoff, and never take down request handling.
- Store rate limits cap capacity before hardware does. The public endpoints tolerate only modest request rates per address, which is what limits how many keyword markets one instance can track. See capacity and limits.
- Operations are yours. Backups, TLS, secret rotation, monitoring and upgrades are the operator's responsibility. Verify a restore before you rely on a backup.
Roadmap
The 1.x line is current, and the changelog names the latest release. What remains open:
- A per-user permission model finer than owner and member, and one account in several workspaces.
- Better popularity calibration using licensed or first-party acquisition data.
- Per-market reviews, category ranks and ratings history. Listings and their screenshot captions are already captured and switched per market.
- More MCP write tools behind the same opt-in, one reversible change at a time.
Release policy and the 1.x compatibility promise: upgrade and roll back.
Contributing
Pull requests are welcome. Read CONTRIBUTING.md first for the commit conventions, the compatibility promise and how the test suites are run. Bugs, questions and feature requests go to GitHub issues. Security reports go through SECURITY.md, never a public issue.
License
This repository's source code is available under the AGPL-3.0 license.