Verifying a deployment

An important feature of Marblerun is providing the ability to verifying the confidentiality and integrity of the whole application on the client-side. To that end, we provide a simple REST-API that clients can use before interacting with the application.

Establishing trust

The first step is to establish trust with the whole microservice mesh. Therefore, Marblerun exposes the /quote endpoint that returns a quote and a root certificate for the whole mesh. Verifying the quote can be done manually, but to ease the process we provide the Edgeless Remote Attestation tools (era) for this purpose:

# If you have EdgelessRT installed
go install
# Or use the binary release
wget -O .local/bin/era
# Run era
era -c coordinator-era.json -h $MARBLERUN -o marblerun.crt

era requires the Coordinator’s UniqueID and SignerID (or MRENCLAVE and MRSIGNER in SGX terms) to verify the quote. In production, these would be generated when building Coordinator and distributed to your clients. For testing, we have published a Coordinator image at You can pull the corresponding coordinator-era.json file from our release page:


After successful verification, you’ll have the trusted root certificate marblerun.crt to use with your application.

Verifing the Manifest

Establishing trust with the service mesh allows you to verify the deployed Manifest in the second step. To that end, Marblerun exposes the endpoint /manifest. Using curl you can get the Manifest’s signature aka its sha256 hash:

curl --cacert marblerun.crt "https://$MARBLERUN/manifest" | jq '.ManifestSignature' --raw-output

Compare this against your local version of the Manifest:

sha256sum manifest.json