Simulate.farm

Request early access

Run complex models without touching the complexity.

Simulate.farm is an early-access platform layer for working with complex agricultural models, starting with RuFaS. It helps users describe scenarios, prepare model workflows, connect systems, and make outputs easier to interpret.

RuFaS is the model. Simulate.farm is the layer that makes complex models usable, integrable, and connected.

Request early accessSee how it works

Complex workflows slow down simulation.

Direct model workflows can be slow to start and hard to scale across teams. Technical setup, data formatting, model configuration, and output interpretation can each become bottlenecks before useful scenario analysis begins.

Starting with a serious model: RuFaS

RuFaS is a comprehensive, process-based, whole-farm dairy model designed to represent biological, environmental, and management interactions across farm systems. Its value comes from its depth: detailed inputs, rich outputs, and flexibility across many scenarios.

That same depth creates a high learning curve. Direct use can require Python, GitHub, local setup, input preparation, and navigation across thousands of input and output variables.

RuFaS is well documented, but it is large and technically demanding. RuFaS is available as open-source software for teams who want direct technical control.

Simulate.farm layered architecture

Most of the complexity stays below the surface. Users describe what they want; Simulate.farm coordinates the model, data, APIs, semantic search, and workflow steps.

Layered architecture, starting with RuFaS

Starting with RuFaS. Designed to connect models, data, and tools. Simulate.farm is being built as a usability layer, an integration layer, a semantic layer, and a conversational workflow layer so organizations can move faster from question to insight.

More than an interface

Simulate.farm starts by making RuFaS easier to access, but the broader architecture is a connected workflow layer. APIs, semantic search, and conversational interaction make it possible to connect models, datasets, farm systems, and external tools through a common interface.

Use RuFaS directly

For technical users who want full control through the open-source model.

Use Simulate.farm as the solution

A guided environment for setting up scenarios, running simulations, filtering outputs, and interpreting results.

Use Simulate.farm as an augmentation layer

Connect existing tools and systems to simulation capabilities without replacing current workflows.

Use Simulate.farm as a hub

Coordinate data, models, and software systems through APIs, semantic mapping, and conversational workflows.

Semantic map preview

Inspect the RuFaS semantic layer

To make the semantic layer inspectable, we created an interactive 3D map of RuFaS input variables, output variables, and input files. Each point represents a model item embedded by meaning, clustered with DBSCAN, and visualized through UMAP, PCA, and t-SNE.

Explore the RuFaS semantic map →

Conversational workflow preview

Describe what you want → Simulate.farm handles the complexity. Conversational workflows are being developed so users can define scenarios, inspect assumptions, and interpret outputs in plain language while preserving structured model runs underneath.

A hub for models, data, and tools

The long-term vision is for Simulate.farm to act as a central coordination layer for agricultural modeling workflows. RuFaS is the first major model in this ecosystem, but the same architecture can support connections between other models, datasets, farm management systems, nutrition tools, and decision-support platforms.

  • Connect farm data sources to simulation models
  • Translate between different schemas and formats
  • Use semantic search to identify relevant variables and concepts
  • Let users describe workflows in plain language
  • Coordinate tools through APIs and structured actions
  • Support model-to-model and tool-to-tool interoperability

Trust and design principles

Security is treated as core infrastructure.
User data ownership is a design principle.
Runs should be reproducible and inspectable.
Configurations and outputs should be traceable.
APIs are planned to support controlled integration with external systems.
Simulate.farm is being designed with APIs so external systems can connect to simulation workflows.

Request early access

We are opening Simulate.farm gradually to partners, collaborators, and early users working with agricultural models, farm data, and simulation workflows.

Moo! I'm Bessie. How do I know you're human? Please guide me to the barn stall 🐮.

Drag me!

🌿 Pasture patch

Soft grass + clover

🏠 Barn door

Warm stable entrance

Verification required before submitting.

Simulate.farm

© 2026 Pasalica