Appearance
Package Discovery
Package Discovery checks public vendor pages for software updates and can import offline installers. It uses a browser and a configured AI model to navigate download pages. Review imported installers before deploying them.
Deployment
Configure the installation's Package Discovery service under Administration > Services, assign an Edge service and cache node, and copy its service client ID. Issue a matching enrollment token for installation.
Run the service on a dedicated host with access to vendor sites, the model provider, Edge, and Cache. Size the host for the expected concurrent browser workload.
Installation
Checkout the package discovery deployment folder from the Ordyn compose repository:
bash
if [ ! -d /opt/ordyn-compose/.git ]; then
git clone --filter=blob:none --sparse https://github.com/ordyn-project/compose.git /opt/ordyn-compose
fi
cd /opt/ordyn-compose
git sparse-checkout add package-discoveryCreate the environment file:
bash
cd /opt/ordyn-compose/package-discovery
cp .env.example .envSet these values in .env:
dotenv
ORDYN_PACKAGE_DISCOVERY_EDGE_HOST=ordyn-edge.example.com
ORDYN_PACKAGE_DISCOVERY_SERVICE_CLIENT_ID=<service-client-id>Pull and verify both service images:
bash
docker compose pull
python3 /opt/cosign-docker-verify/verify.pyContinue only when both the Package Discovery and browser-worker images verify successfully and no failed verification message appears. Issue a service-client enrollment token for the package discovery service client in Ordyn, stop any running service container, and enroll the persistent service state:
bash
docker compose stop package-discovery
printf '%s' '<enrollment-token>' | docker compose run --rm -T --no-deps package-discovery npm run enroll -- --token-stdinAfter enrollment succeeds, start the service:
bash
docker compose up -dTo renew, recover, or replace its service-client certificate, issue a new token and run forced enrollment while the service is stopped:
bash
docker compose stop package-discovery
printf '%s' '<enrollment-token>' | docker compose run --rm -T --no-deps package-discovery npm run enroll -- --token-stdin --forceRun docker compose up -d only after forced enrollment succeeds. Do not use docker compose exec for enrollment.
Package Discovery does not need public ingress or Traefik. It connects outbound to the assigned Edge service. Keep browser workers on the project network without publishing their ports.
Browser capacity
Set ORDYN_BROWSER_SLOTS in .env to the number of simultaneous browser executions the worker can run; the default is 1. Increase it only when the host has sufficient memory and CPU. Scans wait for available capacity within their execution deadline and can be cancelled while waiting.
For additional worker containers, add distinct browser-worker services using the supplied service configuration and list their internal origins in ORDYN_BROWSER_WORKERS, separated by commas. Keep them on the same Compose host and use matching application and worker image tags. Do not add additional enrolled application containers to increase browser capacity.
Model, reasoning effort, and service tier
Select an LLM connection on each discovery policy. Platform Admin configures connections; Software Manager can select them when configuring discovery.
Model, reasoning effort, and service tier inherit from the selected connection. Override individual values for a policy when needed. Optional reasoning effort and service tier can also be set to Omit, leaving the choice to the provider.
A scan keeps the connection and effective values captured when it is prepared, including through retries. Review its recorded configuration when investigating an outcome. Provider quota, authentication, and configuration errors require correcting the provider account or connection before starting another scan.
Managing discovery settings
Create discovery targets from a product's Discovery page. Use Products > Discovery to review targets across products. Starting scans requires a Package Discovery license.
To update several targets together, select them and choose Edit. You can select a connection, change LLM settings, and update Windows signature policies in the same bulk edit. Fields left unchanged retain each target's existing value.
Reviewing scans
During a scan, progress shows the current download, cache transfer, or installer analysis activity. Transfer estimates appear when enough measurements are available. A completed download still requires verification before the package can be imported. Open scan details to review the available transfer metrics.
The Download column shows whether the selected installer finished downloading, separately from the scan result. A scan can report No update without downloading, or Failed after a completed download. Unknown means the retained evidence cannot establish the download outcome. Scan details show the completion time and file size when recorded.
Review scan history for its outcome, imported package, and evidence. Cancel pending scans or abort running scans when the work should stop. History remains available after a target is deleted.
An AI agent with discovery diagnostic tools can investigate a run using its recorded settings, evidence, screenshots and logs, and propose configuration changes for review.
Windows installer signatures
Downloaded EXE and MSI files are checked for Authenticode signatures. Review the result in scan details or on the imported package's Overview tab. Expand Verification details to see the signer, certificate fingerprint, and timestamp. Verification works offline using local trust data.
By default, the result is informational. To require a passing result before importing Windows packages, enable Require valid Windows package signatures under Administration > Settings > Packages. Each target's Windows package signatures setting can inherit this choice, require a valid signature, or report only.
When a valid signature is required, unsigned files, failed verification, and unavailable results block the import. Verification supports EXE and MSI files; other Windows formats, including MSP patches, cannot pass this requirement. The result remains available in the failed scan's details.
A valid result confirms the signed content and certificate chain against the local trust data. A valid embedded timestamp can establish validity for a signing certificate that has since expired. Local trust data is updated with Ordyn releases. Signature verification is separate from malware scanning and does not establish that a package is safe to deploy.
Discovery modes
Use Discovery only to find updates without importing packages. Use Discover and import to import verified updates as packages. Both modes may download an installer to determine or verify its version.
A manual scan can override the configured mode for that run. Scheduled scans use the target's mode.
Product-level configuration
Set the vendor or direct download URL, preferred architecture, locale, and file formats for each target. Public download permalinks are supported, including links whose final filename identifies the version.
The target locale selects the installer's language. Use mui for a multilingual installer, such as Adobe Reader's All Languages (MUI) option. The website's display language is separate from the requested installer language.
The discovery URL can point to a page listing several downloads. Use the target settings to identify the intended installer.
The download timeout sets how long discovery waits for an installer download to begin. The overall scan time limit also applies to completing the download. If the selected installer request returns an HTTP error, the scan fails promptly and reports the status. Increasing the timeout does not resolve an HTTP error; review the reported status and vendor download link before retrying.
Check release information before downloading
Enable Release information in the target's version sources and set its Release information URL to the vendor's release notes page. Keep the installer page or direct download link in Discovery URL.
When release information is the preferred valid source, versions already present or older can skip the download. An unavailable or unclear release falls through to other enabled sources. Review the scan details if none establishes a version.
Choose version sources
Discovery checks enabled sources in priority order and uses the first reliable version. Checking a preferred source may require downloading the installer before trying the next source.
- Download page and links uses version evidence from the selected page, download link, or redirect destination. The link alone can provide the version; the page text does not need to mention it.
- Installer filename uses the filename supplied by the server or browser. Discovery may need to download the installer to obtain it, even when the download URL contains a version.
- Embedded product metadata reads the product version recorded inside the installer and requires downloading it.
- Release information checks the version advertised on the target's Release information URL before downloading.
Prioritize Download page and links to allow versions already present or older to skip the download when the page or link provides reliable version evidence.
If no enabled source provides a reliable version, the scan fails and its details explain why. Imports require successful installer verification and security checks.
Use the product's discovery version parsing policy when vendor filenames or version labels need normalization. For MSI/MSP variants, discovery accepts patches and prefers an MSI baseline when both formats offer the same newest version.
Scheduling
Set a cron schedule for recurring scans. Scheduled scans start after a random delay of 5–60 minutes; the default schedule is 0 2 * * *. Manual scans remain available when scheduling is disabled.
Prompt append
Add product-specific hints when the vendor uses unusual names or offers several editions. Identify the intended offline installer, architecture, or locale. Specify a required version or release line when discovery must stay within it.
Ad blocking
Ad blocking is enabled per target by default. Disable it when it interferes with a vendor's download page. Allow outbound HTTPS to easylist.to and raw.githubusercontent.com for filter updates.
Service-level configuration
Check service connectivity and certificate expiration before investigating failed scans. Follow the renewal workflow and forced enrollment command above to renew or recover its identity.
For upgrades, pause scheduling and finish or cancel outstanding scans before deploying matching Ordyn and Package Discovery releases.
Runtime Control And Local Logging
Active scans continue through temporary connection interruptions. A service restart interrupts unfinished scans. Review the scan evidence and service logs before retrying. Provider-request logs are available on the service host under /data/llm-audit by default.
Discovery memory
Successful scans help later discovery runs repeat a vendor's download flow. Review or clear product discovery memory when the vendor changes its site or discovery keeps following an unsuitable path.
Screenshots
Enable screenshot capture on a target when troubleshooting a difficult vendor page. Review the images in the scan evidence. If an installer or screenshot upload fails, the scan fails and retains its recorded evidence and successfully uploaded screenshots. Review the reported error before starting a new scan.
Duplicate handling
Discovery avoids importing a version already present for the same product, platform, and architecture. Imported packages can reuse an existing variant's installation workflow; review that workflow before rollout.
If verification finds an identical installer already stored for the same product and variant under a conflicting version, the scan fails with a version conflict. Review the reported versions and the product's discovery version parsing policy before retrying; the existing package remains unchanged.
MSP imports require an earlier MSI or MSP in the same variant and must fit its patch chain. See Packages for baseline and patch management.
Limitations
Vendor anti-bot checks, regional restrictions, consent flows, or complex pages can prevent discovery. Some products need prompt hints, cleared discovery memory, or manual package import.
Run the service on a host dedicated to Ordyn service work and review downloaded installers before broad rollout.