Two of us. One keeps bees.
WeBeeS is a small thing built by two people who got tired of standing at a hive trying to remember what was in it last time. There's no office, no marketing department, and no venture capital — just a beekeeper who writes code, a developer who's heard a great deal about bees, and a fairly specific problem we wanted solved.
Who's actually behind this
No support team, no sales team. If you write to WeBeeS, one of these two answers you.
Anton Jorov Antonov
Beekeeping Expertise
Technical Skills
Anton keeps the bees. Eight seasons of hive management, colony health, treatment protocols and the particular frustration of trying to write anything down with sticky gloves on. He has also been writing software for twenty-five years. Most of what WeBeeS does exists because Anton wanted it at a hive one afternoon and it wasn't there.
Boris Hristov Hristov
Professional Experience
Technical Specialties
Boris has spent twenty years building mobile applications for healthcare, fintech and enterprise. He's the reason WeBeeS behaves itself in bad light, on one bar of signal and on a phone you're holding in a gloved hand. He doesn't keep bees. He has heard a great deal about them.
It started with colonies we shouldn't have lost
Every beekeeper has the moment. You're at hive three, suited up, smoker going, and you can't remember whether this was the one with the poor brood pattern or whether that was hive five. The notebook is in the car. Or at home. Or it got rained on in March and the pages have gone.
For us the turning point was watching colonies decline for want of information we'd actually had. Noticed at the time, written down somewhere, and then lost. That isn't a knowledge problem. It's a memory problem, and memory problems are what software is good at.
So we built the thing we wanted: something that hands your own notes back to you before you lift the lid. Every feature in WeBeeS comes from a specific afternoon in an apiary where one of us wished it existed.
Three things you can hold us to
Built with gloves on
Every screen gets used at a hive before it ships — in the rain, in poor light, by someone holding a smoker. If it doesn't work in that state, it doesn't go out.
You email us, we answer
There's no support desk to get through. When you write in, you're writing to the two people who built it — occasionally from an apiary, which may explain the typos.
No roadmap we can't keep
We're not going to publish a five-year plan. Ask for something small and sensible and it's usually in within a few weeks. Ask for something large and we'll tell you honestly whether it's likely.
Our core values shape everything we do, from product development to customer support.
Practical Solutions
We build tools that work in the real world - with gloves on, in all weather conditions, and designed for the actual workflow of working beekeepers.
Community Focus
Built for the beekeeping community, by the beekeeping community, fostering knowledge sharing and collective success.
Continuous Innovation
We're constantly evolving our platform based on user feedback and the latest developments in both beekeeping science and software technology.
Your records are yours
Fair question to ask of a two-person company: what happens to a season's worth of records if we disappear?
You can export everything, whenever you like, in a format you can open without us. Your treatment and medicine records leave with you. We'd rather put that plainly on this page than have you discover you needed it in year four.
What WeBeeS isn't
WeBeeS won't make you a better beekeeper. Your bees and your seasons will do that.
It won't tell you what's wrong with a colony — you will, and it'll remember that you said so. And it isn't for everyone. If you've got three hives and a notebook system that works, keep the notebook.
It's for the point where you've got more colonies than you can hold in your head, and you'd rather spend your time in the apiary than reconstructing what happened three weeks ago.