STELR
Live Demo · Insurance Claims Scenario
Browser demo, not the production stack. This demo uses browser Web Crypto ECDSA P-256, not production AWS KMS signing, and calls Claude directly as a stand-in for the Bedrock production path. It shows the sign, verify, and trust graph flow. It does not prove production KMS signing, metering, or trial behavior. See the security page for the production scope.
Scenario

Acme Insurance - AI Claims Assistant

A customer messages Acme's AI claims assistant about claim #48213. The assistant's response will be generated live, by a real model, then signed the moment it's created.

Customer: "Hi, I'm following up on claim #48213 for water damage to my kitchen ceiling. Can you tell me the status?"
Independent verification

Verify a signed record

Play the role of someone who wasn't in the room, a regulator, an auditor, opposing counsel. Pick a signed record, then verify it. Try editing a word in the text and verifying again.

Tip: change one word above, then click Verify again, watch what happens.
Evidence trail

Trust Graph

The timeline an auditor or compliance officer would actually be handed, per signed artifact.

This demo uses genuine Web Crypto (ECDSA P-256) signing and verification, real signatures, real tamper detection, running in your browser. Generation calls Claude directly, one of the models available via AWS Bedrock, as a live stand-in. The production version signs with AWS KMS-backed keys and invokes models directly through Bedrock, same mechanism, enterprise key management underneath.