Skip to content

System Integrators

OpenETR is designed to fit inside existing systems rather than replace them.

A system integrator may already have:

  • user accounts and authentication
  • KYC or onboarding controls
  • business workflows
  • document storage
  • registries or platform databases
  • APIs, queues, and audit logs
  • domain-specific rulebooks
  • legal or institutional recognition requirements

OpenETR adds a portable control-evidence layer underneath those systems.

The shortest description is:

your system keeps the workflow
OpenETR signs the control evidence
your verifier policy decides what to rely on

Where OpenETR Fits

OpenETR is useful when an electronic record needs durable evidence of lifecycle state.

That includes records that may be issued, transferred, pledged, released, presented, surrendered, redeemed, terminated, replaced, or linked to supporting evidence.

The host system remains responsible for the user-facing product. OpenETR provides the signed object-centric graph that can travel between systems.

Host application
  accounts, roles, UX, document storage, workflow, domain policy

OpenETR
  artifact digest, Anchor record, evidence records, linked evidence,
  dependency edges, verifier output

Recognition layer
  law, registry rules, institutional policy, contracts, relying-party decisions

Common Integration Questions

Question Integration Answer
Do we need to replace our application? No. OpenETR is intended to sit behind existing workflows.
Does OpenETR store the document? Not necessarily. OpenETR can identify the document by digest while the host system stores the content.
Does OpenETR perform KYC? No. KYC and account binding belong to the host system or an external provider.
Does OpenETR decide legal effect? No. It preserves evidence. Recognition belongs to law, registries, contracts, institutional policy, or verifier rulebooks.
Can events move through our API instead of Nostr? Yes, if the signed event data and graph links are preserved. Nostr is the reference wire format, not the only possible transport pattern.
Can OpenETR be invisible to end users? Yes. The host application can expose domain actions while OpenETR signs and verifies evidence behind the scenes.

Suggested Reading Path

Start with:

Then read the core OpenETR pages:

For domain-specific integration:

For deeper specification work: