More than a tracker
AquaFarm is explicitly trying to become the farmer’s daily control system. The internal docs repeatedly position it as a Farm OS, where the product should tell an operator what matters today and what action comes next.
Back to selected work
Case study
AquaFarm is a Farm OS for catfish operations, built to turn daily farm events into clearer control, better planning, and stronger operational memory.
The codebase goes far beyond logbook software. It combines batch and tank control, feed and harvest workflows, financial visibility, alerting, reporting, billing, staff access, and owner-facing ops monitoring inside one multi-tenant SaaS product.
Visit live project
Category: AgriTech
Project snapshot
72
app files across dashboard pages, auth, API routes, billing flows, alerts, reports, and cron endpoints
15
data models covering batches, tanks, logs, financials, feed inventory, alerts, billing events, cron runs, and audit history
28
core library files for auth, plans, reports, billing reconciliation, feed logic, alerts, audit, and transactions
3
subscription tiers implemented for free, pro, and commercial farm operations
What NEXGEN built
A daily operating system for aquaculture, with SaaS controls and reliability layers baked in.
Daily farm operations workspace for batches, tanks, feeding logs, mortality tracking, water quality, tank movements, harvest, and feed inventory.
Planning and execution layer spanning dashboard action prompts, calendar milestones, playbook guidance, and reports designed to support operational decisions.
Commercial and business tooling for financial entries, revenue visibility, CSV export, subscription billing, reconciliation, and plan-based access control.
Reliability and observability layer with alert evaluation, outbound notification dispatch, cron run logging, ops monitoring, audit logs, and bounded internal maintenance jobs.
Multi-tenant SaaS model for farm owners and staff, including commercial-only controls for staff seats, audit visibility, and owner-facing ops surfaces.
Product framing
The strongest idea in AquaFarm is turning farm reality into coordinated action, not isolated records.
The internal docs are unusually clear about the product ambition: the dashboard should become the first place a farmer checks every morning, and the system should hold the operational truth of the farm.
Built around real farm routines
The strongest product quality is how closely the modules map to actual catfish workflow: stocking, allocation, feeding, mortality, water checks, harvest timing, feed runway, and cycle review.
Operational truth plus SaaS controls
The repo combines domain workflows with multi-tenant SaaS mechanics like plan limits, billing, reconciliation, staff seats, audit logs, and owner-only ops visibility. That makes it a product business, not only a farm management tool.
Signals are treated as actions
Alerts, dashboard prompts, milestone tracking, cron-backed evaluations, and ops monitoring show a clear effort to turn farm events into guided responses rather than passive reporting.
Architecture
One SaaS workspace connecting farm operations, subscription controls, and operational observability.
Single Next.js App Router product with dashboard pages, auth pages, marketing pages, and route-handler APIs living in one cohesive workspace
MongoDB and Mongoose model layer for farm records, planning data, financials, billing events, alerts, audits, and cron observability
NextAuth credentials-based access with tenant scoping for owners and staff, plus middleware gating for tier restrictions and commercial-only modules
Runtime controls layered on top through Paystack billing, Upstash-backed rate limiting, protected internal cron routes, alert dispatch, and ops health monitoring
Technology stack
Next.js 14
React 18
MongoDB
Mongoose
NextAuth
JWT Sessions
Paystack
Upstash Redis
Recharts
Tailwind CSS
Framer Motion
Radix UI
What stands out
AquaFarm stands out because it treats operational guidance as the product. Billing, alerts, reports, and staff controls matter, but they are all in service of one goal: helping the farm run better every day.
System breakdown
The repo shows a product that is trying to become the trusted memory and command layer of the farm.
Farm operations engine
The core domain handles batches, tanks, daily logs, tank movements, feed inventory, mortality, water-quality entries, and harvest records, with validators and atomic write helpers for higher-risk flows.
Command center and alerts
AquaFarm’s dashboard, alerts page, alert rules, and dispatch system are designed to surface what needs attention across operations, health, planning, business risk, and cron reliability.
Commercial and billing layer
Plan entitlements, Paystack checkout and verification, webhooks, billing status, cancellation, reconciliation, and owner-only operational pages show a serious SaaS backbone behind the domain product.
Ops and trust surfaces
The platform includes cron monitoring, audit logs, staff settings, alert incident models, and commercial owner gating, which help operators trust the system as a durable source of operational memory.
Repo evidence
The implementation consistently supports the Farm OS direction.
The README defines AquaFarm as a production-capable aquafarm management and planning SaaS, with core domain coverage across operations, planning, billing, team controls, and ops visibility.
The internal Farm OS document says the goal is for farmers to open AquaFarm first every morning to know what matters today, and it explicitly describes the product as moving beyond a tracker into a command center.
The app route tree includes dashboard modules for feeding, mortality, batches, tanks, feed inventory, harvest, water quality, reports, alerts, calendar, playbook, billing, staff, audit, and ops monitoring.
The architecture docs show protected cron endpoints, alert evaluation and dispatch, tenant scoping for owners and staff, atomic write guards for critical workflows, and owner-facing cron health APIs.