Start with a practical FermaStat pilot

A pilot lets your brewery validate monitoring, alerts, and optional control on real equipment before scaling across the cellar.

Who it’s for

  • Breweries that want visibility before full automation
  • Breweries concerned about overnight chiller or glycol failure
  • Breweries still manually checking tanks on a schedule
  • Breweries that want remote alerts when they are off-site
  • Breweries considering control but not ready for a full industrial automation system

What a pilot can include

  • Fermentation tank monitoring
  • Glycol chiller and freezer/fridge monitoring
  • Smart temperature alerts
  • Cloud dashboard access for your team
  • Optional controlled device on configured hardware
  • Hardware and software recommendations based on your cellar

Pilot process

  1. 1

    Brewery equipment review

    Share your tanks, chillers, cold storage, and any control points you want to explore.

  2. 2

    Recommended device map

    We recommend what to monitor first—and where control may make sense later.

  3. 3

    Hardware and software estimate

    You receive a practical monthly and hardware estimate based on your pilot scope.

  4. 4

    Installation and onboarding

    Installation is quoted per site based on travel distance and cellar conditions.

  5. 5

    Review data and next steps

    After the pilot runs, review alerts, logs, and whether to expand monitoring or control.

Information needed to request a pilot

To recommend a practical starter setup, the pilot request form asks for:

  • Contact name, email, phone, brewery name, and location
  • Fermentation and brite tank counts
  • Glycol/chiller setup description
  • Monitoring goals and optional control goals
  • Current pain point and timeline

Request a FermaStat pilot

Tell us about your brewery, tanks, chillers, freezers, and control needs. We’ll recommend a practical starter setup—no obligation.