About

Who we are, and why Fruitful Network Development exists.

The case for coordinated local supply, and the person building toward it.

Why we exist

Northeast Ohio was once a fresh-produce powerhouse. Today that tradition survives in passionate, dispersed pockets: Harbor Gardens, Purple Brown Farm Store, Ohio City Provisions and the East Side Market, Yellow Bird Foodshed, the CWRU farms, and others. Fruitful Network Development is taking the next step: making local agriculture equitable to work in and with again.

THE VISION

The mission, plainly

Local agriculture is undercapitalized, undercoordinated, and full of people who would still rather be there than anywhere else. The first job of Fruitful Network Development is to make their day-to-day operations a little less broken: websites that work, payments that clear, mailboxes that don't get lost. The second job, open-source operations software that small operations can share without losing ownership, is what the first job pays for.

The founder

Dylan Montgomery

Tend to the Garden You Can Touch
- Jack Kornfield

Engineer, founder of Fruitful Network Development. Background in software, agricultural-systems research, and a lot of conversations with people working in food across Northeast Ohio. The web-services side of the business pays the bills; the open-source operations software is the long arc.

UniversityThe University of Akron · Williams Honors College
HighschoolHudson High School · Honors, 4.3 GPA
MajorB.S. Computer Engineering & Applied Mathematics
MinorComputer Networking & Computer Science
ProjectInformation Technology Social Systems - the Mycite paper
ExperienceFounder & Developer, Fruitful Network Development

In his words

I'm a Computer Engineering and Applied Mathematics student at the University of Akron, with a passion for building technology that empowers local communities and small organizations to thrive. Whether through data frameworks for agricultural networks, custom hardware interfaces, or applied mathematical models, my work is driven by one goal: making complex systems accessible and useful for real people.

My projects have ranged from modular ECU dashboards to scalable ETL pipelines, but the common thread has always been bridging the gap between technical depth and practical application. I've spent the last few years exploring how open-source tools and semantic frameworks can help local agriculture operate with the same efficiency as large corporations, without sacrificing independence, transparency, or values.

I am the creator and CEO of Fruitful Network Development, a Computer Engineering Contract firm that provides server and data framework services. Currently the company's aim is to employ a newly created data framework to assist small to midsize farms and agricultural communities to compete in providing their products to US households, without changing who's in charge or how they stay individual businesses. This is being accomplished by providing the FND suite of tools that use a single source of data for both updating and informing. No subscriptions; the goal is a new model of food coordination that helps local agriculture compete on price with the alternatives currently offered, the ones that come with harmful chemicals and no return to local economies. Out-competing harmful practices in the private sector.

I like to think my most unique work skill is being able to see the potential in change and being able to bring that potential to life. Accomplishing that is always a challenge because the path is always uncertain, but the key to success is finding joy in the process. If you can do that, anything is possible.

The problem, plainly

Local food is full of data: what is being grown, where, how much, when it will be ready, what it costs to produce, what it cost to sell. The data exists. It just lives in seven file formats across forty disconnected spreadsheets, three POS exports, two newsletter inboxes, and a clipboard on a barn door.

Every existing answer to this is a platform. The producer enters their data into someone else's schema, which lives on someone else's server, which charges a subscription that grows with success. The data is no longer the producer's; it is the platform's. Most of these platforms close within five years and the data goes with them.

The other answer, file-shipping between operations, solves the wrong problem. You can't coordinate a local food system on PDF attachments. Files are snapshots. Coordination requires references that stay current, are understood the same way by every reader, and survive when any one participant changes their software.

Adjacency map - fragmented local food data sources

The approach, walked step by step

The thing FND is building is not a platform. It is a small, well-defined coordination grammar, a way of describing what a local food operation has and needs that is the same wherever it is read, plus a runtime that lets operations exchange references to each other's real-time state without giving up ownership of their data.

The grammar is self-describing. Anything written in it includes its own definitions, so a reader new to the system can interpret a message without consulting an external schema registry that may not exist next year. That part is the Mycelial Ontological Schema; the long-form is linked below.

The runtime is shape-addressed. A reference does not point at a row in a database; it points at a structure ("a Friday CSA slot for 12 customers in the 44106 zip code with the produce list still pending") and resolves to the operations that currently hold that shape. Operations come and go; the shape is stable.

The interoperability is structural rather than negotiated. Two operations do not need a bilateral integration agreement to talk; they need to speak the same grammar. The cost of joining the network is the cost of describing your own operation correctly, which you have to do anyway.

The result is that the local-food coordination layer can grow node-by-node without a central authority. The software is real today; the network it can become is being built toward one operation at a time, opt-in always.

Reinforcing loops in the coordination model

Articles

Background research, operational guides, and reference documents. Select an article to read.

Research

Northeast Ohio Agriculture History

The long-arc history of Northeast Ohio agriculture and how the region went from a national produce hub to dispersed pockets.

Companion to the About page, the long version behind THE VISION.

About

Dylan Montgomery

Articles

Research

Technology

Support

Dylan Montgomery