AgriSentry
Current local date · --:--Your current location
Back to overview

Licensing safeguards

Every dependency and dataset needs permission to ship.

AgriSentry separates open-source software, public data terms, original educational visuals and provider contracts. “Free to test” is never treated as “free for commercial use.”

Audited

Application dependencies

Direct production and development packages declare MIT, Apache-2.0 or ISC-compatible licences. The release audit fails when a direct package is missing or uses a non-allowlisted licence.

View source repository
Pilot use

Weather data

Open-Meteo data is CC BY 4.0. Its free endpoint is for non-commercial use; a saleable deployment must use an appropriate commercial plan or a reviewed self-hosted open-source deployment.

Open-Meteo terms
Open replacement

Location and maps

The support map now uses OpenStreetMap instead of a proprietary map embed, with contributor attribution under the ODbL. High-volume production geocoding must use a policy-compliant or self-hosted service.

OpenStreetMap licence
Original visual

Disease imagery

The shipped pictorial plate was created for AgriSentry and is illustrative. External training images are blocked from release until source, licence, attribution and permitted-use records are complete.

Open dataset candidate
Metadata retrieval

IITA research catalogue

The top-tier assistant searches IITA CKAN metadata. Search results are references, not automatic training inputs; each dataset licence, consent boundary, scientific quality and redistribution permission require separate review.

IITA data catalogue
Access required

NiMet data

NiMet data and API use remain disabled until the operator receives an official endpoint, token and applicable data-use terms. AgriSentry does not scrape or invent a replacement feed.

Request NiMet data access
Model pending

Machine-learning runtime

A production model may use TensorFlow (Apache-2.0) or PyTorch (BSD-3-Clause). Model code, weights and every training dataset must pass separate licence and field-validation review.

TensorFlow licence
Adapter-based

Provider portability

Weather, SMS, email and authority delivery sit behind HTTP adapters. Credentials stay server-side so an operator can replace a provider without exposing keys to farmer browsers.

Review system controls

Commercial release gate

No unlicensed model, image or API enters production.

  1. 1. Record provenanceSource URL, owner, version and retrieval date.
  2. 2. Verify permissionLicence, attribution, commercial-use and redistribution terms.
  3. 3. Validate safetyLocal field performance, bias, failure modes and human review.
  4. 4. Preserve evidenceAudit result, notices, source snapshot and approval owner.