Passpod Hub v0 · scoped pilot demo

See Sensitive Action Control before production risk.

Passpod Hub v0 is a scoped pilot demo of the hosted product direction: policy, controlled action, Trust Action Receipt, freeze/revoke, and pilot access.

No receipt, no sensitive action.

View Passpod TASK Sandbox on GitHub
Policy standard first. Receipt second. Action last. The requester requests. The user consents. The source confirms. The responsible party decides. Passpod records. DIDX verifies limited receipt state only.
AgentTrust gateway ready
Scoped key ready
Copy-ready API preview
Controlled scenario testing
No private-document custody
No EUDI certification claim

Pick a scenario path.

Start with the AgentTrust Module or an applied TrustPass scenario. Run the preview, inspect receipt state, then request pilot access for controlled testing.

Scenario library

Browse controlled scenarios for reviewer testing. Filter by suite, trust pass type, ecosystem, or developer use case.

Controlled access packages

Public demos remain open. Live testing uses scoped temporary keys, selected scenarios, expiry, revocation, and reviewer permissions.

Starter Access

One scenario, clean validation.

Test one selected scenario in preview + scoped-key mode.

  • One flagship scenario
  • Receipt/API preview
  • Short feedback loop
Partner Console

Multiple flows, shared feedback.

Test 2–3 workflows with a shared feedback loop and API path.

  • Multiple scenarios
  • Scoped keys
  • Implementation notes
TASK Console

Dedicated use-case console.

Focus on AgentTrust Module, Access Control Module, Transaction Review Module, or Trust Action Receipts.

  • Vertical-specific receipts
  • Source-strength rules
  • Partner scenario path

Operating principles

Short scenario boundaries for legal, security, and ecosystem reviewers.

Responsibility model

The requester requests. The user consents. The source confirms. The responsible party decides. Passpod records. DIDX verifies limited receipt state only.

Data boundary

No private identity documents or raw wallet credentials are collected by default. Receipt state is limited to the selected purpose and scope.

Privacy & storage

No advertising cookies, no tracking cookies. Scoped console keys use sessionStorage. Language and notice choices may be stored locally.

Developer and ecosystem links

Built for reviewer testing, API evaluation, controlled partner scenarios, and France / EUDI ecosystem readiness without overclaiming certification.

Request scoped console access

The request is prepared locally and opens an email draft to pilots@passpod.io. Backend approval, scoped keys, expiry, and revocation are handled outside the public page.

Review boundary

The requester requests. The user consents. The source confirms. The responsible party decides. Passpod records. DIDX verifies limited receipt state only.

Scoped pilot keys are temporary, revocable, and never stored in the URL. No hardcoded keys. No localStorage for scenario keys. No key in URL. No private-document custody by default. No EUDI certification claim. No France Identité approval claim. No wallet-provider status claim.
Live scenario testing is intentionally controlled: scoped keys, selected scenarios, expiry, revocation, and reviewer permissions are part of the scenario boundary.
Scoped demo access

Ready to test with your own workflow?

You can run sample Console scenarios without a key. To test with your own payloads, request a scoped demo code. Later, safe sandbox scopes can be generated automatically with expiry, rate limits, and scenario-specific permissions.