anand-92/droidproxy — A native macOS menu bar app that proxies Claude/Codex/Gemini subscriptions for use with Factory Droi…

Description and use

**Brief Summary**
DroidProxy is a native mac‑OS menu‑bar utility that acts as a local proxy for Claude, Codex, and Gemini subscription APIs, enabling seamless use of these models from the Factory Droid CLI. The project is actively maintained (last update 2026‑05‑12) and automatically incorporates new model releases, making it a convenient bridge between AI model services and developer tooling.

**Value Proposition**

• **Fast‑track AI‑enabled monetisation** – By exposing a simple proxy layer, DroidProxy lets teams plug in billing, payment‑service‑provider (PSP), or checkout flows without writing custom integration code for each model.
• **Unified access point** – Developers can switch between Claude, Codex, and Gemini with a single CLI configuration, reducing context‑switching and simplifying CI/CD pipelines that rely on AI‑generated content.
• **Low‑friction experimentation** – The menu‑bar UI gives immediate visual feedback on request routing and authentication, accelerating prototyping of payment‑related use cases (e.g., usage‑based pricing, subscription validation).

**Practical Adoption Path**

1. **Evaluate the API surface** – Clone the repo, run the provided Docker/CLI script, and test the proxy against a sandbox subscription key for each model.
2. **Integrate with Factory Droid CLI** – Point the CLI’s --proxy flag (or environment variable) to the local http://localhost:<port> endpoint that DroidProxy exposes.
3. **Add billing logic** – Insert your PSP SDK (Stripe, PayPal, etc.) in the proxy’s request‑intercept hook (the project ships with a small HTML‑based UI but the core is a thin Node/Express layer that can be extended in any language).
4. **Validate and monitor** – Use the menu‑bar status indicators and the built‑in logs to confirm that billing events fire correctly before promoting the setup to staging.

**Production Readiness**

• **Maturity** – Medium. The codebase is small (HTML front‑end, thin server), has 77 ★ and recent commits, but it lacks extensive automated tests and formal security audits.
• **Dependencies** – Minimal (standard macOS frameworks + Node/Express). Still, verify that the underlying Node version and any third‑party PSP SDKs are pinned and kept up‑to‑date.
• **Maintenance** – Active maintainer (last update today), but the project’s long‑term sustainability depends on continued contributions; consider forking and adding CI checks if you plan a production rollout.
• **Risk mitigation** – Perform a license review (MIT‑like default, but confirm), run a security scan on the proxy server, and add health‑check endpoints before exposing it to external traffic.

In short, DroidProxy offers a quick way to embed AI model calls into billing or checkout workflows, with a straightforward integration path for developers familiar with the Factory Droid CLI. It is suitable for prototypes or internal tools, and can be hardened for production with modest additional testing, security hardening, and maintenance planning.

Problem

anand-92/droidproxy helps integrate monetization, billing, or PSP flows faster.

Outcome

Medium: useful for prototypes or internal workflows, with dependency and maintenance checks before production.

Workflow

• integrate billing or checkout
• evaluate PSP flows
• automate payment operations

Evidence

A native macOS menu bar app that proxies Claude/Codex/Gemini subscriptions for use with Factory Droid CLI. Always updated with new model releases!

Source