terminal CLI for Google Cloud

leg

Official home page for leg, a desktop command-line app for authorized Google Cloud users.

App name: leg

Application purpose: leg helps authorized Google Cloud users list, inspect, monitor, back up, start, stop, resize, and update Google Cloud resources from their terminal.

Why Google data is requested: leg uses Google OAuth to authenticate the user, then calls Google Cloud APIs on that user's behalf only for projects and resources the user is authorized to access. leg does not provide a hosted backend service, analytics, advertising, or tracking.

~ / leg

$ leg auth login
opening browser for Google OAuth...
signed in as you@company.com

$ leg profile set project acme-prod
active project: acme-prod

$ leg vm list
NAME           ZONE            STATUS
web-1          us-central1-a    RUNNING
worker-3       europe-west1-b   RUNNING
db-replica-a   us-east1-c       STOPPED

$ leg filestore show shared-fs

OAuth verification summary

What leg is and why it requests Google access.

This public home page is visible without login and identifies the Google OAuth app named leg. It describes the app functionality, the purpose of Google data access, and the public policy links used on the OAuth consent screen.

App or brand: leg, a desktop command-line app for Google Cloud.
Functionality: leg lets authorized users inspect, monitor, back up, start, stop, resize, and update supported Google Cloud resources from their terminal.
Purpose for Google data access: leg uses Google OAuth only to authenticate the signed-in user and call Google Cloud APIs for projects and resources that user is authorized to access.
Data handling: leg runs locally, stores OAuth tokens on the user's device, and does not send Google user data to a leg-operated backend, analytics service, advertising service, or resale channel.
Public privacy policy: https://www.leg-cli.cloud/privacy.html
Public terms of service: https://www.leg-cli.cloud/terms.html

What leg covers

Built for day-to-day Google Cloud operations.

leg focuses on the resources teams touch when running production workloads. Authenticate once, switch profiles quickly, and keep operational work in the terminal.

Compute Engine
Filestore
NetApp Volumes
Backup and DR
Resource scanning
Profiles
Credential management

Google data use

leg requests Google data only to run the commands you choose.

After you sign in with Google OAuth, leg uses your authorization to call Google Cloud APIs directly from your computer. The data is used to show command output, switch profiles, and perform resource operations you request.

Account identity: leg may read your Google account email address to show which credential is signed in.
Cloud resource metadata: leg may read project, VM, Filestore, NetApp Volumes, Backup and DR, logging, monitoring, and related resource metadata for projects you can access.
Requested operations: when you run write commands, leg uses your Google authorization to start, stop, resize, back up, or update supported resources as requested.
No separate collection: leg does not send this data to a leg-operated backend, analytics service, advertising service, or resale channel.

Security and privacy

Your credentials stay on your machine.

leg is a local tool. It uses Google's OAuth flow, calls Google Cloud APIs directly on your behalf, and avoids collecting data for analytics or advertising.

Google OAuth

Authentication runs through Google's standard OAuth flow. leg never handles your Google password.

Tokens stay local

OAuth tokens and CLI configuration are stored on the user's device, not in a leg backend.

No backend service

The CLI talks to Google Cloud APIs directly for operations the authenticated user is allowed to perform.

No tracking or resale

No analytics, no advertising, and no sale or sharing of user data by leg.

Available on

macOS, Linux, and Windows.

Distributed as a single binary for the major desktop platforms, with the same focused command surface across environments.

macOS Linux Windows