Windows 11 core and offline operation
FARLIVA centers on a Windows 11 desktop application. Core work such as journals, inventory, and documents is designed not to require a continuous internet or cloud connection.
FULL FEATURE DIRECTORY
FARLIVA is designing and developing a wide range of capabilities to bring farm management together in one software system.
This page shares capabilities currently in development, already designed, planned for implementation, or considered for future phases.
Filter by category
87items shown
FARLIVA centers on a Windows 11 desktop application. Core work such as journals, inventory, and documents is designed not to require a continuous internet or cloud connection.
Writes go through authorized APIs without exposing the database directly to the internet. Planned controls include farm isolation, change history, logical deletion, and rejection of unauthorized writes.
Record dates, fields, crops, work, pesticides, fertilizer, machinery, people, and notes, with related photos and videos.
Manage field names, areas, and planting history, and create candidate boundaries, areas, and perimeters from field GPS points. GeoJSON exchange is also planned.
Open relevant records from QR or NFC markers and map drains, outlets, water points, rocks, wet areas, and boundary markers with GPS and photos.
Safely export selected field GPS, planting, protection, fertilizer, yield, soil, and media data, and import the prior manager's period as read-only history.
Record subsurface drains, outlets, manholes, open drains, and pumps with location, depth, provenance, and accuracy. Machinery interference is evaluated deterministically, and missing information produces an indeterminate result—not a safety guarantee.
Register any number of houses, divide them into zones, beds, ridges, and rows, and review ventilation, irrigation, climate, work, and harvest history.
Collect readings from supported external temperature and humidity sensors and link them to house and nursery histories.
Show supported RTSP and ONVIF cameras in house details through a local gateway or secure remote path. Recording, events, and notifications are planned as phased extensions.
Register crops and varieties with regional and production-pattern guidance plus source tracking. A simplified home-garden journal that hides business features is also planned.
Copy prior planting and schedules as candidates for the next year and compare dates, costs, yields, and other results.
Use area, row and plant spacing, row count, germination, and reserve rates to calculate seed, plant, and tray needs and compare transplant settings.
Calculate field-level application plans and reserve inventory without reducing on-hand stock at planning time. After work is confirmed, reconcile actuals and show them in field history.
Forecast nursery lots, usable plants, multi-field allocation, transplant settings, maturity, grades, losses, and containers. Forecast versions are retained, with pessimistic, standard, and optimistic scenarios compared against actuals.
Keep multiple sensor and manual readings by role and show daily environment, GDD, leaf stage, transplant preparation, and ventilation candidates. Missing or conflicting readings remain visible, and candidates are not auto-confirmed.
Calculate plant and tray needs from field and transplanter settings, compare tramline implications for single-sided, double-sided, and drone spraying, and model house tray placement in both directions without direct machine control.
Connect morning, afternoon, and all-day plans with rain alternatives, fields, machinery, people, and staffing needs.
Record attendance, breaks, departure, and approvals, with role-limited clock terminals and manager mobile access. Estimate labor cost by task and field from actual time.
Save reviewable templates for machinery, settings, products, dilution, water, staffing, and cautions used in work such as crop protection.
Track purchases, use, movements, balances, locations, cost, and machine compatibility, with fuel linked to per-machine consumption.
Locate stock in warehouses, racks, and zones and reconcile book and physical quantities. Record approved returns, theft, loss, leakage, damage, and write-offs, while supporting tax-exempt diesel purchase, storage, machine use, monthly totals, and reporting material.
Keep tractor and implement specifications and manuals together, with oil changes, repairs, costs, and next-service dates per machine.
Organize purchases, serial information, warranties, and repairs for machinery, tools, facilities, and houses.
Register machinery, vehicles, trailers, forklifts, and facilities and review inspections, insurance, consumables, fuel, and ownership cost per asset, with transfer support for the next owner.
Extract manufacturer and model candidates from plates or photos and import catalog specifications only after review. Before an implement purchase, compare hitch, PTO, power, hydraulics, electrical, and other requirements with evidence and explicit missing information.
Manage plates, serials, registration marks, inspection certificates, warranties, and other multi-page photo or PDF sets with history. OCR and AI output never becomes canonical before review, and sensitive documents are not auto-published.
Estimate yield and revenue across scenarios using plant count, average weight, losses, containers, price, and cost, including break-even and per-area work cost.
Manage products, customers, receivables, and payments; create invoices, delivery notes, receipts, and compact sales slips. Agricultural bookkeeping imports, duplicate checks, and cost analysis are also planned.
Record field, variety, grade, weight, box count, and destination, then connect confirmed quantities to product inventory and sales.
Trace a harvest from field and date through containers or lots, sorting, and shipping destination.
Extract contact candidates from card images, link them to customers or suppliers, and support layout and printing for the user's own cards.
Calculate product amounts and treatable area from dilution, field size, water rate, tanks, speed, boom width, and nozzle output. This does not independently authorize pesticide use.
Check how many tanks or fields existing stock can cover, purchase shortages, user-confirmed mix-order notes, time until rain, and temperature, humidity, and wind conditions.
Calculate total amount, bag count, applied nutrients, and shortages from rates, area, bag size, nutrient percentages, planned use, and actual use.
Use rights-reviewed, sourced fertilizer composition catalogs and official rule packs for deterministic soil-based candidates. External prices are excluded, residue, disease, and next-crop risks stay separate, and missing information prevents definitive recommendations.
Estimate capacity, finish time, and fuel from width and speed, while managing source-separated tire-pressure profiles, service intervals, part cost, staffing, labor, and daylight.
Calculate VPD, dew point, GDD, photo comparisons, GPS distance and area, drainage, materials, house covering, irrigation, pumps, electricity, storage loss, and farm units, including reverse-solving modes.
Organize many calculators with search and favorites, pass reviewed results into journals, plans, inventory, or purchasing, and preserve inputs, formulas, and source versions for reproducibility.
Compare photos from the same field, house, or location by year and date to review growth changes.
Place photo-pin candidates on fields from EXIF and GPS and filter by date, crop, or class. Photos without GPS can be placed manually, and automatic field linking remains a review candidate.
Import images, PDFs, and text, structure OCR output as review candidates, preserve originals and sources, and avoid overwriting master data before confirmation.
Support structured questions and answers, variety pages, regional and production-pattern data, collaborative edits, and reliability labels, with review and history before publication.
Record crop growth, soil, mowing and weeds, diseases, and pests with fields, GPS, photos, and dates, with links back and forth to the main farm journal.
Search life stages, symptoms, damage, timing, and similar candidates while showing sources, review dates, and reliability. Protection information is reference-only, does not independently authorize pesticide use, and optional AI only suggests candidates.
A learning tool for crop exterior, cross-sections, healthy structure, disease changes, and pest damage through diagrams and comparisons, initially planned for onions.
AI is off by default and uses user-configured providers and securely stored keys. Users can preview and exclude data before sending, and suggestions remain drafts.
Planned capabilities include local AI, usage limits, natural-language calculator input, journal drafts, field summaries, maintenance organization, management explanations, reference search, and mobile assistance. AI actions require permission checks and human approval and are audited.
Register aircraft, cameras, sensors, batteries, flights, waypoints, media, and telemetry. Keep source imagery and logs separate from derived results with hashes, provenance, and parser versions.
Layer GeoTIFF, COG, aerial imagery, GPS observations, and work tracks; compare dates; calculate versioned indices such as NDVI; and manage thermal, elevation, point-cloud, and annotation data. AI analysis remains optional candidate generation.
Import and analyze GNSS and guidance equipment, AB lines, positioning quality, tracks, overlap or gaps, and prescription or result maps. Initial scope is read, import, and analyze—not direct machine control.
A smartphone field experience is planned through a supported Self-host Hub for viewing, media, GPS, and field notes. It is not the same application as the Windows edition.
Send field photos, videos, and GPS points, lines, or areas, then review them in Windows before linking them to journals and fields. Year-over-year field issue comparison is also planned.
On a user-owned Self-host Hub, workers handle assigned work, attendance, and simple journals, while authorized managers handle machinery, documents, tires, and maintenance. Offline writes remain pending until Windows revalidates them, and conflicts are never silently overwritten.
Farm data is based on local PC storage, with optional sync to user-managed targets such as NAS, LAN storage, or self-hosted servers. Core local work is designed to continue if a sync target is unavailable.
Protect incoming changes in the Windows canonical store without turning remote deletions into immediate permanent deletion. Keep versioned backups on external media or NAS and queue smartphone uploads while offline.
Keep Windows local data canonical while optionally syncing to reviewed cloud storage, NAS, WebDAV, S3-compatible, LAN, or self-hosted targets. FARLIVA-operated farm-data storage is not required.
Verify update signatures and hashes, back up the application and database first, and use a separate recovery application if the main program cannot start.
Package errors and recent actions for diagnosis, including AI-friendly reports, while removing or masking passwords, API keys, and personal information.
Let users create recovery points on demand and restore the whole system, settings, or selected features from a separate FARLIVA Recovery application, preserving the current state first when possible.
Arrange weather, market, schedule, alert, worker, and sensor cards with user-controlled size, position, and transparency.
Bring today's plans, alerts, inventory, maintenance, and people into one farm overview.
Manage feature identity, dependencies, and permissions with clear toggles. Turning a feature off preserves history, while beginner presets and per-user or per-device layouts can be restored safely.
Visualize feature integrations as edges with requirement level, state, start date, history, provenance, and conflict checks. Updates with missing manifests, migrations, rollback, or permissions are not applied.
Distinguish whether each feature idea originated with the FARLIVA developer or AI, retaining the first proposal date and later design assistance or refinement history without rewriting origin.
Create farm sites using static-first HTML, CSS, and minimal JavaScript, then publish to supported managed hosting. Product data uses public snapshots separated from internal inventory.
A Windows wizard for installing the Self-host Hub and online capabilities on supported managed servers, with preflight checks, plan preview, signature verification, backup, deployment, smoke tests, and scoped rollback.
Cover sales, exchange, or donation of machinery, parts, and materials; buyer appraisals; repair and overseas sourcing contacts; and farmer-to-farmer work requests.
A planned flow for dealers to manage used-equipment status, price, media, service, and warranty, and for farmers to request estimates, transport, trade-ins, and inspections.
A future concept for verified secondhand dealers, with zero platform transaction fees and no payment custody. It would analyze the service's own completed and unsuccessful listings without exposing personal data.
Manage dealer rates, availability, delivery conditions, reservation state, and before/after evidence, while linking rented equipment to the farmer's journal as a temporary asset.
Handle family journals, media, audio, anniversaries, timelines, pets, albums, search, and print in a private area separate from farm permissions. It is off by default, excluded from farm transfers by default, and AI summaries remain optional.
A future concept for comparing yield and material-cost distributions using only anonymous aggregates that users explicitly agree to share.
Farm data remains private by default; only fields explicitly approved by the user become anonymization candidates. Contribution quality is separated from currency and fixed exchange rates.
A future concept separates optional donations or ad viewing from normal use. Any future AGRI distribution assumes self-custodied wallets; FARLIVA would not broker exchanges or hold user assets.
Visualize the amount, age, and verification state of accumulated records without equating them to monetary value, and version AGRI purpose and safety policies.
If real distribution begins in the future, users could export distribution dates, amounts, transaction hashes, and related information.
A dormant foundation for external-wallet ownership proofs and future entitlements, fully off initially. It freezes a baseline so existing features cannot later become AGRI-gated and never asks users to enter wallet seeds or passwords into FARLIVA.
Separate brand settings from farm data and manage web, API, update, and other locations through logical endpoints, with connection diagnostics, history, rollback, and records that do not depend on absolute URLs.
The official site uses farliva.com, while a minimal Control Plane is limited to cloud.farliva.com and does not host a farm Data Plane. Update history, releases, brand copy, and future host migration are managed separately and versioned.
Use Japanese as the authoritative default while supporting English and future locale packs. Preserve original text, separate language from unit preferences, and review safety-critical translations.
Preserve the original installation date and days of use across updates. Future genuine-copy checks are designed around device signatures and online or offline challenge-response without requiring a name, email, or farm account.
Package disaster or accident evidence and make repair history, manuals, and emergency contacts searchable. Also record machinery lending, purchase history, and daily handovers.
Explain where to enter data, what it means, what happens, outputs, integrations, and common mistakes for every stable feature, using actual test UI and annotated image guides reachable from each field.
An always-on foundation that prevents unsupported guessing, filling, or assertion. It distinguishes confirmed, derived, unverified, unknown, conflicting, indeterminate, and stale information and exposes provenance for important results.
Publishing is off by default, and only farmer-selected profile fields such as name, region, crops, images, and links go to /farms. Internal farm IDs, field GPS, inventory, journals, and other operational data are excluded.
Search or create homemade liquid fertilizer, fermented material, and similar recipes by ingredients, steps, purpose, and source. Creator claims, evidence, and legal status stay separate; AI does not invent missing quantities, and individual results do not become general efficacy guarantees.
No features match this search and category. Try a different search term or filter.