Cloud & Security
Signed Contracts
Ensuring contract integrity and security.
In a standard REST environment, the "Contract" (documentation) is often disconnected from the "Execution." Axiom Core fixes this by treating the contract as a Signed Binary Artifact.
How Signing Works
- Local Build: When you run
axiom build, the CLI generates the contract IR (Intermediate Representation). - Cloud Upload: If your project is linked and you are logged in, the IR is sent to the Axiom Hub.
- Signature Generation: The Hub signs the contract using a Private Key stored securely in our backend.
- Artifact Creation: A
.axiomfile is produced, containing the IR and the cryptographic signature.
The Value of Signing
Preventing Man-in-the-Middle Attacks
If an attacker intercepts your .axiom file and tries to add a malicious endpoint or modify a model's validation rules, the signature will become invalid. The client-side runtime will detect this and refuse to load the contract.
- Immutable Deployments: Once a contract is signed and released, you have a guarantee that the mobile app is behaving exactly as intended at the moment of the build.
- Version Enforcement: You can ensure that old versions of your app only communicate with contracts that match their specific version signatures.