Transparent Session Proxy - Use Cases

See It In Action

Watch the Transparent Proxy

Your tools. Your workflow. CoreLink underneath.

corelink-client-agent

$ cat ~/.corelink/agent.json

{ "targets": [

{"alias": "prod-db.internal", "protocol": "postgres", "local_port": 15432},

{"alias": "staging-ssh.internal", "protocol": "ssh", "local_port": 12222}

]}

$ corelink-client-agent

[proxy] prod-db.internal -> 127.0.0.1:15432 (postgres)

[proxy] staging-ssh.internal -> 127.0.0.1:12222 (ssh)

[ok] Hosts file written to ~/.corelink/hosts

$ psql -h 127.0.0.1 -p 15432 -U app

[session] JIT credentials provisioned (TTL: 1h)

[session] Connected to prod-db via CoreLink (session: d4a8f1)

Three steps. Zero workflow changes.

The client agent runs on high ports -- no root, no TUN/TAP, no VPN client.

Install Agent

Download the CoreLink client agent for your platform. It runs as a userspace binary -- no elevated permissions, no kernel modules, no VPN configuration.

Configure Targets

Define your targets in a simple JSON config. Each target maps an alias to a local port. The agent generates a hosts file entry so your tools use the alias directly.

Connect Transparently

Use psql, ssh, or any native client as normal. The proxy intercepts the connection, provisions JIT credentials with a configurable TTL, and routes through an authenticated CoreLink session.

Transparent to Your Tools. Enforced by the Platform.

The proxy runs on high ports -- no root, no kernel changes, no TUN/TAP devices.

Your Client

Native Tools

psql ssh mysql rdp

Client Agent

TCP Proxy

High-port listener, no root required, session caching with TTL

Platform

JIT Credentials

TTL-scoped credentials provisioned per connection, session recorded

Target

Any Protocol

SSH RDP Postgres MySQL

Client agent runs on

Linux

macOS

Windows

Connect to Any Target Without Changing Your Workflow