Need a hand? We're on GitHub.

Yes, fully free — no ads, no in-app purchases, no premium tier. The app is MIT-licensed and the source is on GitHub. There are no plans to monetize it.

No. There is no developer-operated backend. The app talks directly from your phone to the Argo CD server URL you configure. Nothing transits any third-party servers.

See the Privacy Policy for the full breakdown.

Open the app, tap Add Server, and enter the URL of your Argo CD server (for example https://cd.apps.example.com). The app supports OIDC/PKCE for SSO sign-in or username/password as a fallback.

Your server must be reachable from the device — that may mean being on a corporate VPN, a Tailscale net, or having the Argo CD endpoint exposed to the internet behind your existing auth.

Sign in via browser (easiest). On the login screen, tap Sign in via browser. The app opens your Argo CD login page in an in-app browser, so you sign in exactly the way you do on the web — Dex, an external OIDC provider, or a custom login page. This needs no server-side setup: no redirect URI to register, no cliClientID to set.

The dedicated SSO Login button uses a native OIDC/PKCE flow instead — slightly smoother, but it requires a one-time redirect-URI registration, depending on how Argo CD authenticates:

Dex (built-in). Argo CD hardcodes the argo-cd-cli Dex static client with only http://localhost redirect URIs. This list is regenerated on every Dex restart and cannot be overridden via argocd-cm. The patch below wraps the Dex container command with a background watcher that re-injects argocd://auth/callback every time Argo CD regenerates the config:

kubectl patch deployment argocd-dex-server -n <argocd-namespace> --type=strategic -p '{
  "spec": {
    "template": {
      "spec": {
        "containers": [{
          "name": "dex",
          "command": [
            "/bin/sh", "-c",
            "(LAST=\"\"; while true; do M=$(stat -c %Y /tmp/dex.yaml 2>/dev/null); if [ \"$M\" != \"$LAST\" ]; then LAST=$M; grep -q \"argocd://auth/callback\" /tmp/dex.yaml 2>/dev/null || sed -i \"s|  - http://localhost:8085/auth/callback|  - http://localhost:8085/auth/callback\\n  - argocd://auth/callback|\" /tmp/dex.yaml; fi; sleep 0.2; done) & exec /shared/argocd-dex rundex"
          ]
        }]
      }
    }
  }
}'

exec keeps argocd-dex rundex as PID 1 so it receives Kubernetes signals correctly. The patcher runs in the background and wins the race against Dex startup because it watches for file modification and reacts in under 200 ms.

External OIDC provider. If you use an external OIDC provider configured via oidcConfig in argocd-cm, two changes are needed:

1. Add argocd://auth/callback to the allowed redirect URIs in your provider's application settings.
2. Set cliClientID in argocd-cm to the client ID that has this redirect URI registered.

No changes to the Dex deployment are required in this configuration.

Yes — tap Sign in via browser on the login screen. If your Argo CD sits behind a proxy or gateway that intercepts requests and redirects to its own login page — for example oauth2-proxy, an Envoy/Ingress auth gateway, or a corporate SSO portal — the in-app browser completes that flow and carries the session through to the API.

This is the only sign-in option that works in that setup: the native SSO Login and username/password flows never reach Argo CD's own login, so they can't get past the proxy. No changes to your Argo CD are needed.

The app targets the public Argo CD HTTP API and works with any reasonably recent version (2.x and later). If something breaks against a specific version, please file an issue with the version number and steps to reproduce.

iOS only trusts certificates signed by a CA in the system trust store. To use a self-signed cert, install the root CA on your device as a trusted profile (Settings → General → VPN & Device Management → Certificate Trust). Beyond that, the app uses standard URLSession validation.

ArgoCD Mobile is an independent, community-built client for the Argo CD project. Argo CD is a trademark of its respective owners.

Pull requests are welcome. The app is built with React Native. Browse open issues labeled good-first-issue, or open a discussion first if you want to scope a larger change.