Quickstart
Run asobeast with Docker Compose and import your first app in about five minutes.
How asobeast works
The daily pipeline, the queue, the provider layer and where every number comes from.
API reference
Every endpoint, generated from the API’s own OpenAPI document.
MCP server
Point Claude Code or Claude Desktop at your instance and ask it about your positions.
What does asobeast do?
Tracks two live stores
Tracks two live stores
Import Apple App Store and Google Play URLs, capture the first metadata snapshot, refresh on demand and review field level changes. See App Store and Google Play for the differences that matter.
Monitors keywords per market
Monitors keywords per market
One app is a single tracking entity. Keyword tracking carries its own country, so one app tracks keywords across many storefronts. See Countries and markets.
Scores keywords transparently
Scores keywords transparently
Traffic and difficulty carry their evidence source, calculation version, capture date and confidence. See Traffic, difficulty and opportunity.
Produces an explainable work queue
Produces an explainable work queue
Eight deterministic rules run over stored history and return recommendations with a priority, an estimated impact and the exact numbers behind them. See Work the Action Center.
Who is asobeast for?
asobeast is built for people who ship apps and want their ASO data to stay theirs. It fits if any of the following is true.- You want ASO tracking without a per keyword subscription.
- You need the data on your own infrastructure for policy or privacy reasons.
- You want to query your own ASO history from an agent or a script instead of a dashboard.
- You track a handful of apps across several storefronts and want one place to see them.
Where should you go next?
Install
Docker Compose, published images or a development environment.
Guides
One guide per surface, from importing an app to sending alerts.
Configuration
Every environment variable with its default and its effect.