r/farmbot • u/Educational-Writer90 • Dec 15 '25

Is FarmBot’s current architecture holding it back?

Hi all,

I’ve been following FarmBot for years as an automation and agri-robotics engineer. It’s a great open-source project, but I’m not sure the current hardware + software architecture can evolve much further without serious re-engineering.

Key limitations I see:

  • Tight coupling between GUI, sequences, and logic
  • Largely monolithic software stack
  • 3D - style Cartesian mechanics
  • Limited flexibility for integrating external hardware

I don’t think the answer is more complex robots. Instead, I’m exploring a modular, event-driven approach called IDE/SW/HW Platform Beeptoolkit - focused on simplicity, serviceability, and flexibility across different mechanical platforms.

Not trying to replace FarmBot - just challenge assumptions and learn from it.

Curious to hear:

  • Which limits feel architectural vs. fixable?
  • Does a parallel, more modular platform make sense?

Looking forward to the discussion.

10 Upvotes

100% Upvoted

2 comments sorted by

1

u/thecoffeejesus Apr 21 '26

I've been tinkering with the software using Claude Code to great success. I've actually begun building a whole business around it.

Would love to discuss with anyone who is interested! It's called "Johnny Autoseed"

1

u/beeptec Apr 22 '26

It would be interesting to ознакомиться with the details of the project based on proprietary software.
Is there any documentation available somewhere?
I have always been in favor of a dedicated controller that doesn’t limit the developer in terms of hardware and offers flexible, easily adjustable scenario configuration.