addroid-oss

AdDroid OSS is a self-hosted console for managing Meta (Facebook and Instagram) advertising campaigns using a workflow borrowed from software development. The README is written in Japanese. The core idea is that instead of making ad changes directly in Meta's dashboard, you store your ad configurations as YAML files in a Git repository, and all changes go through a GitHub Pull Request review before they are applied to Meta's systems. An AI component generates proposed ads or improvement suggestions, but a human must approve each change by merging the Pull Request before anything is sent to Meta.

The system runs entirely on your local machine at a private address, requiring no public domain, no SSL certificate, and no tunnel service. All connections to external services, including GitHub, Meta, Slack, and the AI provider, are outbound from the application. A background job system handles scheduled tasks such as pulling performance reports, monitoring budgets, and generating improvement suggestions automatically.

The main way to interact with AdDroid is through a chat command where you describe what you want in plain language, and the tool translates that into a Pull Request against your ad configuration repository. There is also a web interface at localhost port 3000, a command-line interface, and optional Slack integration that lets you activate campaigns via a slash command.

Setup requires Node.js, Git, GitHub CLI, and PostgreSQL 16 or later. The initialization command walks through diagnosing and installing missing dependencies step by step. It encrypts secrets locally and never stores your Meta Access Token in plain text. Platform support covers macOS 13 and later, mainstream Linux distributions, and Windows via WSL2. Windows native without WSL2 is not supported due to file permission and process management requirements.

Using AdDroid with a real Meta advertising account requires obtaining a Meta Access Token through a Meta Developer App. The setup documentation includes a detailed walkthrough for creating a Business App, configuring a System User, assigning the right advertising assets, and generating a token with the correct permissions. The application's core health checks pass without the token, but applying or activating any actual ad campaign requires it.