Going to Production
When your pilot is complete and you're ready to deploy DPP Kit for real-world use, here's what changes.
Production Checklist
Before switching to production mode, ensure:
- DID is configured — Your organization has a working DID
- Facility records created — All relevant facilities have DFRs
- Credential content finalized — You've iterated on your credential structure in pilot mode and are satisfied with the content
- Team access configured — All team members have appropriate access levels
- Identifiers planned — Decide whether to use auto-generated identifiers or bring your own GS1-assigned GTINs/GLNs
- Evidence files ready — Any PDFs, photos, or documents to attach to credentials are uploaded
What Changes in Production
| Aspect | Pilot | Production |
|---|---|---|
| Identifiers | Re-used on re-issue | New identifier per issuance |
| Resolver entries | Overwritten | Accumulated |
| Mode banner | Shown | Hidden |
| Credential tagging | issued_in_mode: pilot | issued_in_mode: production |
Domain and Branding
For production deployment:
- Custom domain — Your DID will use your production domain (e.g.,
did:web:credentials.acme.com:org:acme) - HTTPS required —
did:webrequires HTTPS for DID Document resolution - DNS configuration — Point your domain to the DPP Kit infrastructure
Data Migration
Pilot credentials can coexist with production credentials. You don't need to delete pilot data — it's tagged with issued_in_mode: pilot so it's clearly distinguishable.
When you're ready:
- Upgrade your organization tier to Production
- Switch the organization mode to Production
- Begin issuing production credentials
tip
Consider running a brief parallel period where you issue both pilot and production credentials to validate the transition before fully committing.