Could portable identity become infrastructure people would use?
I used product data and focused community experiments to move Disco from an overly broad consumer proposition towards organisation- and API-backed credential issuance.
- Credentials analysed
- 167,737
- Issuer identifiers
- 837
- North-star measure
- 2×
Non-self-issued credentials
Unique issuers in the analysed dataset
Total credential issuance within four months
- 1Broad consumer product
- 2In-community tests
- 3Organisation issuance
- 4Developer platform
Product analysis · 2022–2023. The dataset excludes self-issued credentials so the product shift could be evaluated through organisation and partner activity.
Could issuance work without brittle third-party storage?
Testing showed that removing the required storage login improved completion without damaging adoption. That evidence supported a more reliable profile and issuance architecture.
- Required dependency
- Removed
- Profile model
- DID:WEB
- Issuance model
- API
Third-party storage no longer blocked completion
A simpler, domain-backed identity foundation
Backed by organisations rather than one consumer app
- 1Map the drop-off
- 2Remove required login
- 3Migrate profiles
- 4Open organisation API
Product and architecture migration · 2022–2023. Completion improved without an observed loss in adoption; no unsupported causal percentage is claimed.

What changed following the architecture and API migration?
Across equal 53-day comparison windows, issuance, issuer participation, and recipient reach all increased. Campaigns, events, and interface-driven issuance also contributed.
- Credential issuance
- 10.6×
- Active issuers
- +49%
- Recipient reach
- 4,246%
Across equal 53-day windows
New issuers increased 67%
391 → 16,993 unique recipients
- 153 days before
- 2Architecture + API migration
- 353 days after
- 4Like-for-like comparison
Non-self-issued credential activity across equal-length windows. These increases followed the migration; they are not attributed to the migration alone.