Now live on AWS Marketplace

Cryptographic Provenance for Generative AI

What SSL/TLS did for the internet, STELR does for AI-generated content. Sign, verify, and prove the origin of AI outputs routed through the STELR /generate API, for text and agent actions via Amazon Bedrock, with a chain of custody your compliance team can stand behind.

The demo is a browser demo, not the KMS production stack. See the demo page disclaimer and the security page.

Prompt
Model
Output
Signed
Verified
Live
On AWS Marketplace, available now
KMS-backed
Every artifact signed with AWS KMS
Bedrock-ready
Built to work with models you already run
The problem

Every enterprise deploying AI is asking the same question.

Was this AI-generated. Which model made it. Was it modified after the fact. Can it hold up in an audit, months later. Today, almost nothing answers that.

Why now

AI governance is no longer optional.

The EU AI Act, emerging U.S. state regulations, and enterprise customers writing AI-output provenance into their own contracts are turning "can you prove this was AI-generated, by which model, and that it hasn't been altered?" from a hypothetical into an audit requirement. STELR gives your security, compliance, and AI governance teams a cryptographically verifiable answer - not a policy document, a signed proof.

“The signature that makes AI content and agent actions provable - to someone who wasn't in the room.”

Provenance  ·  Non-repudiation  ·  Independent Verification
Deploy with confidence

Runs 100% inside your own AWS account.

Your content, the signing keys, and the provenance ledger never leave your AWS account - STELR's own infrastructure never receives, processes, or stores it. What crosses the boundary is limited to a public verification key, billing metrics reported through AWS Marketplace, and, only if you opt in, a fixed set of content-free error telemetry. Nothing else.

Available on AWS Marketplace

Procure through AWS Marketplace under AWS Marketplace terms. Your own review requirements still apply.

Your VPC, your data

Deployed as a per-customer CloudFormation stack entirely within your own AWS account and VPC. See how tenant isolation works.

Trust signal, not just sales channel

AWS Marketplace listing signals the security review, compliance baseline, and billing integration your procurement team already trusts.

Capabilities

Four products. One trust layer.

STELR Provenance

The core trust platform. Cryptographic identity for every AI-generated artifact.

STELR Verify

Verification APIs that confirm origin, integrity, and authorship on demand.

STELR Trust Graph

An evidence and chain-of-custody record, retained for 2,555 days in your own AWS account under Object Lock Compliance mode.

STELR Policy

Compliance and governance enforcement, mapped to the regulation already arriving.

How it works

Three steps to a provable artifact.

  1. 1
    Sign

    Every output routed through the STELR /generate API is cryptographically signed at creation through STELR Provenance.

  2. 2
    Verify

    Confirm origin and integrity anytime through the STELR Verify API.

  3. 3
    Prove

    Pull audit-ready evidence from the STELR Trust Graph, months or years later.

Built on AWS: API Gateway, Lambda, DynamoDB, and KMS.
Quickstart (cURL)
# Sign a generation with STELR (runs inside your own AWS account)
curl -X POST "https://your-api-id.execute-api.us-east-1.amazonaws.com/customer/generate" \
  -H "X-API-Key: <your-api-key>" \
  -H "Content-Type: application/json" \
  -d '{"prompt":"Your prompt here","max_tokens":200}'

# Verify a signed artifact
curl -X POST "https://your-api-id.execute-api.us-east-1.amazonaws.com/customer/verify/{content_id}" \
  -H "X-API-Key: <your-api-key>" \
  -H "Content-Type: application/json" \
  -d '{"content":"<exact output text>"}'
          
Try it yourself, live demo →

Built for enterprise from day one.

100% in your AWS account · Per-customer stack in your account · API-first · AWS KMS-backed signing · Immutable provenance ledger · Live on AWS Marketplace

Built toward the standards enterprises already answer to.

STELR embeds audit-ready provenance and authenticity signals directly into your AI workflows. A signature verifies specific content in the exact form it was signed. It does not survive arbitrary edits, paraphrasing, translation, or reformatting, and an AI-generated determination is not a legal or forensic finding. See Terms, section 4.

EU AI Act Article 50 (in force) SOC 2 (in progress) GDPR (designed to support, scope not yet stated) NYDFS 500.13 (designed to support, scope not yet stated)

Built for the industries where AI output provenance isn't a nice-to-have: financial services audit trails, healthcare AI-assisted documentation, legal AI-drafted work product, and government AI transparency mandates.

FAQ

Frequently asked questions.

What is STELR?

STELR is the trust and provenance layer for enterprise AI. It cryptographically signs AI-generated content at creation, and lets you verify its origin and integrity at any point afterward.

What's the difference between Provenance, Verify, Trust Graph, and Policy?

Provenance signs content at creation. Verify confirms origin and integrity on demand. Trust Graph stores the resulting evidence as an immutable, queryable record. Policy maps all of it to the compliance frameworks you already answer to.

How secure is STELR?

Signing runs on AWS KMS with asymmetric keys. Each customer deploys a per-customer stack in their own AWS account, and the API is API-first from the ground up, with a growing set of enterprise controls as we onboard design partners. See the security page for scope and limits.

How is STELR different from PureVector?

STELR is provenance, not detection. It signs AI outputs at creation so origin and integrity can be verified later. It does not detect whether existing content was AI generated.

Is STELR available today?

Yes. STELR is live on AWS Marketplace today, with AWS Bedrock integration built. Reach out and we'll help you get started.

Build AI your enterprise can prove.