Platform
ScaiWave ScaiGrid ScaiCore ScaiBot ScaiDrive ScaiKey Models Tools & Services
Solutions
Organisations Developers Internet Service Providers Managed Service Providers AI-in-a-Box
Resources
Support Documentation Blog Downloads
Company
About Research Careers Investment Opportunities Contact
Log in

CLI

Two binaries. proxility is the workstation CLI that talks to the control plane; proxility-connector is the service that runs inside a network.

proxility#

teratermmacro
1
2
3
proxility login                         authenticate via ScaiKey
proxility realm use <tenant>/<realm>    set the working realm
proxility whoami                        show identity and roles

Connectors#

teratermmacro
1
2
3
4
5
proxility connector create <name> [--description TEXT]
proxility connector list
proxility connector show <name>
proxility connector revoke <name>
proxility edge ranges                   current edge prefixes for allow-lists

Services#

teratermmacro
1
2
3
4
proxility service create <name> --connector A[,B] --target HOST:PORT --protocol tcp|udp
proxility service list
proxility service show <name>
proxility service delete <name>

Policy#

teratermmacro
1
2
3
4
5
6
7
proxility policy allow --from SELECTOR --to SERVICE --ports LIST
                       [--expires DATE] [--description TEXT]
proxility policy list [--expiring-within 30d]
proxility policy delete <rule-id>
proxility policy show --format yaml
proxility policy apply <file> [--dry-run]
proxility policy history

Decision log#

text
1
2
proxility log tail [--follow]
proxility log query --verdict deny --since 24h

proxility-connector#

Runs as a system service. The commands you use directly:

scdoc
1
2
3
4
proxility-connector enrol --token ptk_...     one-time enrolment
proxility-connector status                    sessions, certificate expiry, transport
proxility-connector renew                     force certificate renewal
proxility-connector test <service>            resolve and connect, printing each step

test is the first thing to reach for when something does not work — it prints resolution, policy verdict, handshake and target connection as separate steps, so the failing one is obvious. See Troubleshooting.

Exit codes#

Code Meaning
0 Success
1 Usage or validation error
2 Authentication or authorisation failure
3 Denied by policy
4 Control plane unreachable

--dry-run on policy apply exits 0 when the file matches the live rule set and non-zero when it would change anything, which makes it usable as a CI drift check.

Updated 2026-11-08 18:08:05 View source (.md) rev 2