The Delivery Pipeline

The Blueprint Delivery System (BDS) manages the complete customer lifecycle from form submission to ZIP bundle. This page documents the pipeline for engineers troubleshooting delivery experience.

End-to-end flow

1. Form submission — customer completes the blueprint request form at hopr.co/lane7-blueprints, selecting blueprint and license type (trial or commercial)
2. Email verification — BDS sends a verification link to the submitted address; customer clicks to confirm
3. Export control screening — BDS checks the customer against the Treasury Consolidated Screening List (CSL); customers on the list receive a rejection email
4. KYC (commercial only) — commercial license requests require Know Your Customer business verification before payment; trial licenses skip this step
5. Stripe payment (commercial only) — customer completes payment via Stripe for the committed WoSP unit minimum
6. License issuance — BDS creates or activates the customer's license record
7. Credential injection — BDS writes HOPR_LICENSE, HOPR_KEY, CHIPS_ALGORITHM, HOPR_API_TOKEN, and .dockerconfigjson into each pod's 02-secrets.yaml
8. ZIP bundle generation — BDS assembles the complete blueprint ZIP with all manifests, app code, scripts, and pre-filled secrets
9. Delivery email — customer receives a download link for the ZIP bundle

License status and email routing

Status	Meaning	Email sent
none	New customer, verification pending	Email verification link
trial-active	Trial license issued	Bundle-ready email with download link (immediate)
paid-active	Commercial license active	Bundle-ready email with download link (immediate)
trial-expired	30-day trial period ended	Trial conversion email with Stripe link
paid-expired	Annual subscription ended	Subscription renewal email with Stripe link

One license, all blueprints

A single Hopr license covers all blueprints. Once your license is active (trial-active or paid-active), you can request and download any catalog blueprint without repeating the KYC or payment flow.

What's in the ZIP

Each delivered ZIP contains:

• Pod directories (one per pod): 01-namespace.yaml, 02-secrets.yaml (credentials filled), 03-deployment.yaml, app/app.py, app/Dockerfile
• deploy.sh, teardown.sh
• pinhole-setup.sh (boundary-pod blueprints only)
• blueprint.yaml — machine-readable blueprint metadata
• README.md — deployment instructions for the specific blueprint
• EULA.md — license agreement

If something goes wrong

Common delivery issues and their resolution:

Symptom	Cause	Action
No verification email	Spam filter or wrong address	Check spam; contact support with your submission email
Download link expired	Links expire after 48 hours	Re-request the blueprint from the catalog page
02-secrets.yaml has empty credentials	Delivery error	Contact support with your Customer ID
Export control rejection	Name or address matches CSL	Contact export@hopr.co

Contact support at support@hopr.co and include your Customer ID (visible in the delivery email) for fastest resolution.