Aujas Automated Code Signing Platform
aujas.com
- Windows
- macOS
- Linux
- Web
- Self-hosted
What Aujas Automated Code Signing Platform is
Aujas Automated Code Signing Platform, also called CodeSign, manages software signing requests across build and release workflows. Its workflow engine routes approvals for projects, builds, and certificates, and records approvals and file-signing activity. Teams can submit work through a command-line interface, including parallel submissions, or integrate signing into a DevOps pipeline. The platform manages certificates and keys stored in an HSM or secure keystore; access is limited to approved requests from authorized users and machines.
Listed signing options include basic, GPG, hash, force, append, MAGE, and WHQL signing. A malware scanner can inspect files before signing. Supported certificates include self-signed, standard code-signing certificates from any CA, and Extended Validation certificates. Aujas lists more than 50 supported file types, with plugins to add types. Supported targets include Windows and Linux files, Java and Android packages, Docker images, Apple application and package formats, Debian and RPM packages, Helm charts, and driver files. Deployment options include a customer data center, public cloud, and managed cloud hosting. Pricing is available on request.
Who it suits
CodeSign suits DevOps and release teams that need signing approvals and audit records integrated into build processes. It also fits organizations managing signing keys in an HSM or secure keystore.
Good to know, and what to watch
- Routes signing requests through role-based approvals
- Records file-signing activity
- Supports HSM or secure-keystore key storage
- CLI and DevOps pipeline integration
- More than 50 file types supported
- Paid product with pricing on request
- Deployment requires choosing among listed hosting options
Plans
Every plan and pricePay-as-use signing-based licenses
Pricing on request
The verdict
CodeSign brings signing approvals, key management, and activity records into software release workflows. Teams should confirm the deployment model and supported file types for their environment.
What the maker publishes
- Access control
- It supports enterprise directory authentication, machine verification using public-key cryptography, role-based access, and user self-service. source
- Audit records
- The platform records approvals and signing activity for auditability and visibility. source
- Audit trails
- It records approvals and signing actions, with records of each file-signing activity. source
- Build and release
- The leaflet says CodeSign integrates with software build and release systems to automate signing and supports concurrent signing of multiple files. source
- Certificate support
- The leaflet lists standard, Extended Validation, and self-signed certificates. source
- Certificate types
- Supported certificate types listed include self-signed, standard code-signing certificates from any CA, and Extended Validation certificates. source
- Demo
- Aujas offers a scheduled demo covering the platform’s features, capabilities, architecture, and application flow. source
- Deployment
- The datasheet lists on-premises deployment in a customer data center, public cloud, and managed cloud hosting. source
- Deployment example
- A case study describes a SaaS deployment with CloudHSM integration and automated cloud-infrastructure monitoring and alerting. source
- Development integration
- The platform offers CLI integration for parallel file-signing submissions and can be incorporated into a DevOps pipeline. source
- File type coverage
- Aujas’s case study says the platform supports more than 50 file types and can add file types through plugins. source
- File types
- The leaflet says CodeSign supports over 50 file types and can add new types through plugins. source
- Integrations
- The datasheet describes integration with corporate directories, SAML identity providers, command-line interfaces, and HSM key stores. source
- Intended users
- Aujas describes CodeSign as DevOps-ready and says it can be integrated into DevOps pipelines and build and release workflows. source
- Intended users
- Aujas describes CodeSign as purpose-built to protect enterprises against risks from unsigned code and help build customer and stakeholder trust. source
- Key protection
- Signing keys are managed in an HSM or secure keystore, and access is allowed through CodeSign for approved requests from authorized users and machines. source
- Keys and certificates
- CodeSign manages certificates and signing keys, which can be stored in an HSM or secure keystore. source
- Large file limit in case study
- A customer requirement in the case study specifies signing files up to 5 GB. source
- Malware scanning
- The leaflet describes an enterprise-grade malware scanner that inspects files before signing. source
- Operating systems
- Aujas’s case study lists support for Windows, Linux, and macOS platforms. source
- Pricing model
- Aujas describes CodeSign pricing as pay-as-use with signing-based licensing, but does not publish a price on the pages opened. source
- Purpose
- Aujas CodeSign is an automated code-signing solution designed to manage and scale signing processes. source
- Purpose
- CodeSign is a secure, automated, DevOps-ready solution for ensuring software application integrity, protecting signing keys, and helping combat malware. source
- Signing modes
- The datasheet lists hash signing and remote signing with a pluggable malware scanner. source
Checked against the maker's pages on 8 Oct 2026.