Native CLI Client
Use onepam ssh, onepam psql, and onepam mysql from your terminal. The CLI authenticates via OAuth2 Device Code Flow with full audit trail.
What You Get
Secure Access From Your Terminal
OAuth2 Device Code Flow for terminal-based authentication
Use onepam psql, onepam mysql, and other database subcommands from your terminal
Token caching in ~/.onepam/ for session persistence
Resource listing with type, status, and host information
Automatic token refresh and expiration management
Works with all plans — Solo through Enterprise
Lightweight single binary with zero dependencies
Config management for multi-environment setups
Compatible with CI/CD pipelines and automation scripts
CLI Workflow
Device Code Authentication
Deploy in Under 5 Minutes
Three Steps to Secure Access
1. Sign Up With SSO
Connect your identity provider — Okta, Azure AD, Google Workspace, or any SAML/OIDC provider. Your team logs in with existing credentials.
2. Add Your Resources
Register servers, databases, Kubernetes clusters, and web apps. Define who can access what with role-based policies.
3. Access Securely
Your team accesses resources through the browser — identity-verified, session-recorded, and audit-logged. No VPN, no exposed ports.
Try Native CLI Client — Free for 14 Days
From signup to your first secure session in under 5 minutes. No infrastructure changes, no credit card, no sales call.