SST-Citadel
Organizational credentials. Viewer / Editor / Admin on a Vendors collection. Versions and an activity log. First-host SKU.
Citadel →Applications
A short description of each application. First host is still Citadel. The rest attach after that box is standing, or stay with SST. No public price list.
White-glove on a box you hold, or SST-hosted where the placement allows it. Merlon is on-prem only.
Organizational credentials. Viewer / Editor / Admin on a Vendors collection. Versions and an activity log. First-host SKU.
Citadel →Mark, PAdES-B sign, and validate PDFs. Saves into the mailbox you already have — OneDrive or Drive. Not a Signet content cloud.
Distill living infrastructure into a capture pack and a replay pack. Coverage is a score, not a guarantee.
On-prem to Azure / GCP / AWS crossing. Preflight, operator-gated migrate, post-validate. Does not flip DNS.
Perimeter appliance. nftables. Guard / Watch / Seal. Not DPI. Not TLS intercept. Dedicated box.
Isolated AI access. Entra + MFA. Separate engines for Excel, boards, financials, general help, and IT fix. Zero data sharing across them.
Remote assist. Host plus agents. Shared database is the remaining SPOF — we write that in the quote.
Staff attach to your nodes — HO, plant, staging VPC. Not a consumer privacy VPN. Signaling stays with SST.
Not customer installs. How we issue grants and refuse to become a public file drop.
Short-notice deployer. Rehearsal first. Customers do not install Hermes.
Authorized black / grey / white-box work. Control plane stays with SST.
Mints, validates, revokes grants. Not sold. Customers never install it.