Don't trust us. Run the check yourself.

Use one command to check that Morse's run the open-source code Morse published on GitHub.

$ npx @askmorse/verify

$ npx @askmorse/verify api.trymorse.aiChecking the enclaves api.trymorse.ai lists Attestation  2 enclaves, each signed by AWS Nitro (root 641a0321…8f79bb5b)             key 8f6198f0b59e34cf, signed 6 min ago             key 0032c6519a4b546d, signed 8 min ago             PCR0 4fccf46baafd…ef6e1606             PCR1 3b4a7e1b5f13…a0974d03             PCR2 de079dd37c0b…1c4d4f35Allowed      on Morse's signed list of prod images, not revoked             list 290, logged 48 min ago at Rekor entry 3714441255             https://search.sigstore.dev/?logIndex=3714441255Source       v2026.11.4-pins-23c1570, commit 696ab5a852e0 on main of             github.com/trymorse/morse-enclave, names these PCRsRebuild      not run. These PCRs are the ones Morse's CI wrote in that commit.             Run with --rebuild to build it here and compare (Docker, ~2 min).TLS          api.trymorse.ai's TLS key 7589dd8f4f792416 (issuer Amazon RSA 2048             M04) is in no attestation document, so TLS ends before the enclave.             Morse's relay can read requests on it unless they're sealed. Passed. The enclaves api.trymorse.ai lists run v2026.11.4-pins-23c1570 ofgithub.com/trymorse/morse-enclave, as published (not rebuilt here).Pin this release in CI: --release 696ab5a852e09f3ab11e49156f3892e02796db5a

Prove what code Morse's enclaves run. Check the four steps that tie each enclave's software to a commit on GitHub.

Read the check's code Read the enclave's code

Check AWS's signature. AWS's hardware signs each enclave's , which holds the of the enclave's and the enclave's . Morse can't forge AWS's signature.

Check Morse's signed list. Morse's CI signs a list of the images Morse's enclaves may run, and 's public log records every list.

Read the image's code on GitHub. A commit to Morse's open-source enclave names the image's measurement, so you know which code the image runs.

Rebuild the image yourself. Each release is a , so you can build the commit on your machine with ‑‑rebuild and compare the measurement with the one AWS signed.

Run the check in your CI. If Morse's enclaves ever run an image that isn't on Morse's signed list, the check fails and your deploy stops.

See the enclave's releases

Don't trust us. Run the check yourself.

Prove what code Morse's enclaves run. Check the four steps that tie each enclave's software to a commit on GitHub.

Check AWS's signature. AWS's hardware signs each enclave's attestation, which holds the measurement of the enclave's image and the enclave's public key. Morse can't forge AWS's signature.

Check Morse's signed list. Morse's CI signs a list of the images Morse's enclaves may run, and Sigstore's public log records every list.

Read the image's code on GitHub. A commit to Morse's open-source enclave names the image's measurement, so you know which code the image runs.

Rebuild the image yourself. Each release is a reproducible build, so you can build the commit on your machine with ‑‑rebuild and compare the measurement with the one AWS signed.

Run the check in your CI. If Morse's enclaves ever run an image that isn't on Morse's signed list, the check fails and your deploy stops.

Run the check yourself, any time.

Check AWS's signature. AWS's hardware signs each enclave's , which holds the of the enclave's and the enclave's . Morse can't forge AWS's signature.

Check Morse's signed list. Morse's CI signs a list of the images Morse's enclaves may run, and 's public log records every list.

Rebuild the image yourself. Each release is a , so you can build the commit on your machine with ‑‑rebuild and compare the measurement with the one AWS signed.