MFT feature · Security & vault

Credentials and keys that never leave the vault.

Passwords, SSH keys and certificates are stored encrypted and shared between connectors without ever being shown again.

Book a demo How it works

how it works

How phaf protects your connections

Secrets are encrypted at rest with a master key that stays on your server.

Define a connection once and reuse it in many flows — rotate it in one place.

Keep certificates in one store and get an alert before they expire.

Four roles decide who administers, who edits flows and who only views — with two-factor authentication.

Logins and every change are recorded with who, when and from which IP — and can go to your SIEM.

phaf runs on your servers or private cloud. Data does not pass through us.

How it works

Add a secret once in the vault — it is encrypted immediately.

Connectors point to the secret, never to the clear value.

Review access and changes in the activity log.

Bring a real file, message or API. We build the flow with you in the demo.