Why this exists
Most garden planning tools were built for beginners. They’re approachable, visually friendly, and they hit a ceiling around the time you start caring about yield comparisons across seasons. After a few years of serious gardening, you end up using the app for layout planning and a spreadsheet for everything it can’t do.
Vernal is for the gardener who has been keeping the spreadsheet. The one who tracks germination rates by variety, notes which tomato did best in which bed, and knows that soil pH in the south corner has been drifting since 2023. That gardener exists in real numbers and is badly underserved by everything currently available.
The goal isn’t to compete with GrowVeg on approachability. GrowVeg is good at what it does. The goal is to build the tool that exists past the ceiling, one that treats your garden data as something worth analyzing, not just recording.
What Vernal stands for
Vernal’s core is open source. Your garden records. Years of germination rates, harvest weights, soil amendments, planting notes are exportable in full at any time, whether you’re on the free tier or not. If you stop using Vernal, you leave with everything you put in. The paid tier adds features. It is never the price of admission to your own history.
Vernal is not trying to teach you how to garden. It assumes you already know. The design decisions that follow from that are significant: less onboarding, more data density, fewer tooltips explaining what a tomato is. The app should feel like a tool built by someone who respects what you already know, not a product trying to make gardening seem accessible to people who are already doing it.
The development process is documented in the devlog. The source code is on GitHub. Decisions get written down and explained, not just shipped. This isn’t a performance of transparency, it’s the only model that makes sense when you’re asking people to store years of records with you.
Who’s building it
Vernal is a solo project. I’m Robert, a developer and home gardener who got frustrated enough with the existing tools to decide it was easier to build a new one than to keep maintaining spreadsheets alongside an app that couldn’t keep up.
The open source commitment came first, before the features. If I’m asking gardeners to trust Vernal with data they’ve been collecting for years, the least I can do is make the code readable. Anyone can see what the app does with that data. Anyone can flag something that looks wrong. That’s not a risk, it’s the point.
Vernal is in active development. The devlog covers what’s being built, why decisions get made the way they do, and what’s coming next. If you’re the kind of person this tool is for, it’s worth reading.
Cambium
One thing Vernal makes possible over time is aggregate data. If enough gardeners are tracking germination rates and harvest yields for specific varieties in specific growing zones, that data becomes genuinely useful in aggregate, not just for individual gardens, but for the broader question of what actually works, where, and under what conditions.
Cambium is a community-contributed seed database being built inside Vernal. The idea is straightforward: shared, open data on seed variety performance across real gardens and real growing zones — not manufacturer estimates, not controlled trials, but what actually happened in someone’s raised bed in Zone 6a over four seasons. It’s early, it’s separate from the core Vernal app, and it will be documented properly when it’s closer to real. Mentioned here because it’s part of why the data model is built the way it is.