Northgate Labs

Satellite insights for agriculture

See crop and flood risk, field by field.

Northgate Labs is developing clear, field-by-field summaries of crop conditions and possible flood impacts using open satellite observations.

The goal is to help insurers, agricultural lenders and public agencies decide where to look closer and what needs attention.

Planned coverage: cotton, wheat, rice, maize and soybean; regions chosen with pilot partners

The problem

It is hard to see what is happening on every farm.

When teams need to assess many farms, local visits and reports can take time. Satellite images may offer a wider view, but they need careful interpretation before they can help guide a decision.

  1. 01

    Checking damage one field at a time is slow

    After a flood or dry spell, insurers may need to inspect many farms before they can understand the scale of damage. Travel and access can delay those checks.

    A satellite view can help teams decide where an in-person visit matters most.

  2. 02

    Lenders have little information about field conditions

    A loan team may know the borrower but have limited information about what is happening on the land during a growing season.

    Regular field-level observations could add context to portfolio reviews.

  3. 03

    Large-area assessments are hard to coordinate

    Public agencies and relief teams need to understand which areas may be affected, while field access and local reports are still catching up.

    A broad satellite-based view can help teams prioritize follow-up checks.

How it works

A simple path from satellite image to field insight.

This is the process the product is designed to follow, explained without technical steps or unverified performance claims.

  1. Step 01

    Use regularly updated satellite observations

    We start with open satellite images from sources such as Sentinel-2 and Landsat, which record the same places repeatedly over time.

    The images are free to access; processing them still takes computing resources.

  2. Step 02

    Focus on the fields and usable observations

    Field boundary data and observations are supplied by a partner, and observations are checked for visibility before they are summarized.

    Unclear observations should be treated cautiously, not as certain results.

  3. Step 03

    Turn observations into a field report

    The planned product will summarize signs of crop stress and possible flood impact for each field, together with the observation date and an indication of uncertainty.

    These estimates are decision support, not a replacement for field checks.

  4. Step 04

    Give teams information they can act on

    The intended product will make summaries available through a simple dashboard and, for teams that need it, a connection to their own software.

    Pilot requirements will help determine the first delivery format.

What the product is designed to provide

A field report people can understand.

The aim is to turn satellite observations into a short summary: what may be happening, how much of a field could be affected, and when the image was captured.

Intended report format

What a field report will contain

This is the format we are designing with pilot partners. It shows what each report will cover; no values are shown because no pilot results have been published yet.

Crop condition
A summary of signs that crops may be under stress, based on visible changes in the satellite images.
Change over time
How visible crop growth appears to change between usable observations during the season.
Possible flood impact
An estimate of how much of a selected field may be covered by water.
Estimated affected area
A preliminary estimate to help teams prioritize follow-up, not a confirmed insurance loss.
How clear the evidence is
A note about the quality of the observation, including factors such as cloud cover.
Observation date
When the satellite image was captured, so you can see how recent the information is.

Reports are intended to be dated and presented with their limitations, so a team can decide whether to investigate further.

Who it may help

One shared view of field conditions.

Different teams ask different questions. Northgate Labs gives them a common, dated starting point for those conversations.

Crop insurers

See where a claim may need attention

The question

Use satellite-based information to help prioritize which reported losses need an in-person review.

The intended information

A field-level summary of crop condition, possible water coverage and image date.

The information is intended to support, not replace, an adjuster’s assessment.

Agricultural lenders

Follow field conditions during a loan

The question

Add context about crop conditions when reviewing agricultural loans and portfolios.

The intended information

A dated summary of visible crop changes for the fields in a portfolio.

Teams provide the field locations they want included in an evaluation.

NGOs and public agencies

Understand possible impact across an area

The question

Build an early overview of areas that may need attention after a flood or dry spell.

The intended information

Area-level summaries of possible water coverage and crop condition.

Use the overview to guide local checks and response planning.

These are intended use cases, not current customer deployments or validated outcomes.

AWS and the product plan

A phased plan for cloud resources where they add value.

Northgate Labs is designed around AWS in three phases. Satellite images are large, analysis needs vary over the season, and this plan will grow with what the pilot proves is needed.

Phase 1: pilot

  • Amazon S3

    Will store the open satellite imagery for each pilot region. Large images need cheap and durable object storage.

  • AWS Lambda and Amazon EventBridge

    Planned to notice when new satellite observations arrive and trigger the next processing step without a server running all day.

  • AWS Batch

    Will run the bursty image-analysis jobs. Compute scales up when observations arrive and down to zero when they do not.

  • Amazon DynamoDB and Amazon SES

    Planned intake for early-access requests, so the pilot pipeline starts from data that is already structured.

Phase 2: modelling and data

  • Amazon SageMaker

    Will host the development and evaluation of crop condition and flood impact models against field observations.

  • Amazon RDS for PostgreSQL with PostGIS

    Planned home for field boundaries and results. Geospatial queries such as "fields inside this district" fit a spatial database.

  • AWS Step Functions

    Will coordinate the multi-step processing workflow and retry tasks that fail partway.

Phase 3: delivery

  • Amazon ECS with AWS Fargate

    Will serve the report interface without managing individual servers.

  • Amazon API Gateway

    Planned front door for partner systems that request reports programmatically.

  • Amazon CloudWatch

    Planned for monitoring service health and job outcomes.

  • AWS Secrets Manager

    Planned for keeping access credentials out of code and configuration.

Why these service shapes fit

  • Large imagery storage: source satellite observations are large, cheap and durable object storage comes first.
  • Bursty batch compute: image analysis runs when new observations arrive, not continuously, so on-demand jobs fit better than always-on servers.
  • Model development: crop condition and flood impact models are built and evaluated against field observations before any results are served.
  • Geospatial queries: finding results by field or district needs a spatial database, planned as PostgreSQL with PostGIS.

Scope and timing will be tuned with pilot partners.

Roadmap

Validate the need before expanding.

This is a direction, not a dated delivery commitment. The first priority is to agree on a useful pilot and check the estimates against real field observations.

  1. Stage 01Planned

    Pilot

    Global · major field crops

    Work with pilot partners to compare satellite-based summaries with what is observed on the ground.

    • Compare crop condition summaries with field observations
    • Estimate which fields may be affected by water
    • Agree on a simple report format with pilot partners
  2. Stage 02Planned

    Expansion

    Based on pilot findings

    Expand only after the first evaluations show where the product is useful.

    • Assess additional crops and regions
    • Provide a clearer view of possible flood impact
    • Summarize conditions across larger areas
  3. Stage 03Planned

    Platform

    Longer-term goal

    Make it easier for organizations to review information and use it in their existing work.

    • A simple online way to review field reports
    • Options to share results with existing tools
    • Clear pricing and service information

The stages and features shown are proposed priorities; timing and final scope depend on partner feedback and pilot findings.

Early access

Join the pilot.

We are inviting organizations to join the pilot group. Tell us where you work and what you need to decide; we will follow up to discuss whether an evaluation is a fit.

01

Discuss a pilot

Share your use case and region so we can assess whether an early evaluation is a fit.

02

Shape the evaluation

Help define which fields, observations and comparisons would make an evaluation useful.

03

A direct conversation

Discuss product needs and practical constraints with the team building Northgate Labs.

04

Input on the roadmap

Crops, regions, outputs and pricing are decided with the pilot group before they are decided for everyone.

work address
approximate
Crops of interest
a couple of sentences
One reply from a person, no mailing list.

FAQ

Questions we get asked.

Straight answers, including the ones where the answer is not final yet.

Open satellite observations from Sentinel-2 and Landsat, plus other open datasets that are relevant to a region. All planned sources are publicly available; image clarity and availability vary by location and date.