Company
Built by the people who had the problem.
Arcenkey began as an internal tool at ICP, a systems integrator that runs device management, large-scale deployment, and custom software for local government and large commercial clients.
Origins
We built the tool we wanted to buy.
We had the same backup jobs, integration scripts, and in-house applications everyone has, with the same passwords in the same config files. The platforms on the market were built for someone with a bigger team and a different estate. So we wrote the tool we wanted: one command to store, one to read, a hardware device behind every secret, and nothing new to operate.
It has been in production across the infrastructure ICP manages since 2022. In 2026 we rebuilt the trust model so the HSM credential lives on a single server instead of every host, then added failover, a secondary server mode, cross-host sync, scoped tokens, a dashboard, and an API, and gave the product its own name. Everything on this site is shipped and in use, not planned.
Where it stands
The facts a technical reviewer will ask for.
- In production
- Client in daily use since 2022. Current single-server trust model since 2026, with a dozen releases since.
- Codebase
- About 18,000 lines: a Bash client and tooling, and a Go server with a small, fully vendored dependency set.
- Tests
- Over 160 automated tests across the client suite and the server's unit tests.
- Interfaces
- Command-line tool, REST API with an OpenAPI specification, web dashboard, Prometheus metrics, Windows wrapper, Java and Tomcat guidance.
- Documentation
- Installation guides for the server and client roles, a user guide, man pages, and the API specification.
- Hardware
- YubiHSM 2, with hot-standby devices and a second server with its own device for active-active service.
- Platforms
- Red Hat Enterprise Linux 10 in production; Rocky and Alma Linux 8 through 10. Windows through the SSH wrapper. Additional Linux distributions planned.
- Third-party code
- Apache-2.0, MIT, and BSD licensed components only, with local changes marked and a notices file that ships with the product.
- Ownership
- Wholly owned by ICP. Available only under a direct agreement with ICP. Not offered as a hosted service.
What comes next
Taking it further is a different kind of work.
ICP builds software for its clients and for itself, and runs it. Arcenkey exists because we needed it, and it has earned its keep many times over on the infrastructure we manage. Carrying it to a general release is a different undertaking: an independent assessment, directory integration, a support organization standing behind every installation. Those are things a larger company already has.
So we hold it carefully. It runs under direct agreement with ICP and nowhere else. There is no download, no trial, and no sales desk, and we have not split it into the pieces that would be easy to sell, because a product like this is only worth having whole. Whoever takes it further will take all of it: the code, the documentation, the operating practice, and the name, together.
Reaching us
There is no form.
Conversations about Arcenkey begin with an introduction to ICP, not a sales inquiry.