A properly installed and mainted system is very accurate. We routinely see less than a 1-2% margin of error, which is the published accuracy of the underlying flow sensor.
The Kegbot app includes a built-in calibration wizard, so you can adjust the behavior depending on your system.
Absolutely. We've built many Kegbot systems and realize one size does not fit all. Most Kegbot features are optional and can be disabled.
Yes. Kegbot Server has system-wide privacy settings. The manager of a server can place it in "Members Only" mode (only authorized users can view data), or disable all public access entirely.
Simply put, we've had the best results from inline flow sensors. They work well, don't tend to require calibration, and are available relatively cheaply. Scale-based systems we've seen have been more brittle, more expensive, or both.
That said, the sensing component is mostly decoupled from the rest of the Kegbot stack. So if a better sensor becomes available, it should be simple to add support for it, without major changes in the app or server.
No. Absorbed BAC varies from person to person (and many other factors), and can only be approximated — poorly.
Responsible drinking is a job for humans, not bots.
Kegbot was started in late 2003. By 2004, the system stabilized and mail list opened up, and in 2005, Kegbot was written up in Popular Science, MAKE Magazine, and several other places.
We're pretty certain that Kegbot was the very first open source project to bring keg volume, keg access control, and the internet all together!
Not necessarily, but it is highly recommended. With purchase of a compatible Android tablet and the Kegbot Tap Conversion Kit, you will be able to monitor taps, kegs, volume, and pours. However, you will be missing many attractive features that are offered only by successfully installing and configuring Kegbot Server.
Kegbot natively supports NFC user authentication on tablets that offer NFC compatibility
The Kegbot app also allows users to choose (tap) their drinker account to assign pours, but these assignments are unauthenticated
None, currently - but plug-and-play access control is on our roadmap
Team Kegbot highly recommends purchasing one Tap Conversion Kit, installing Kegbot Server, and configuring the system to your taste. Only after successfully installing and maintaining the Kegbot ecosystem on one tap should you consider extending the Kegbot system to accommodate multiple taps.
If you're happy with the feature set, the simplest way to set up multiple taps is to purchase multiple Tap Conversion Kits - one kit per tap. Kegbot employs a many-to-many approach, in that Kegbot Server can accommodate multiple tablets, and the Kegbot app on each tablet can accommodate multiple Kegboards (via a powered USB hub).
If you find the feature set lacking for your particular needs, tell us what we're missing! We're consistently rolling out new features to accommodate our many varied customer sets.
Not currently. It is on our roadmap for future development
Yes and no. It does not work as a plug-and-play unit out-of-the-box, but you may decide to build an authentication dongle through DIY methods. A plug-and-play authentication solution is on our roadmap for future development.
Yes and no. It does not work as a plug-and-play unit out-of-the-box, but you may decide to add a temperature sensor through DIY methods. A plug-and-play temperature monitoring solution is on our roadmap for future development.
Not currently. A plug-and-play access control solution is on our roadmap for future development.
Yes, but with a number of caveats. Your hosting provider has to allow several key features like sudo access, the ability to install python packages from the command line, and the ability to serve up a wsgi application. Some VPS servers and most dedicated servers allow some form of this, but the full capabilities vary from provider to provider and we're in no position to make recommendations regarding which providers are compatible with Kegbot installation.
If your computer(s) at home are Windows or Mac machines, one route you could take is installing Linux on a virtual machine. VirtualBox is a free option. And since you're the owner/installer, you will have all the access you need to get Kegbot Server up and running.
Alternatively, you can dedicate a Raspberry Pi device to Kegbot. It's a little slow / underpowered, but it just works. Simply put together a virgin RPi and follow the Kegberry instructions.
pip is the preferred install method for the typical user. Version upgrades are fairly stable.
git is the preferred install method for developers and users who want bleeding-edge (read: sometimes unstable) updates.
Yes. Kegbot's hardware schematics, firmware, and software are all open source. However, you must be handy with a soldering iron and source your own parts. While Team Kegbot no longer officially supports/troubleshoots do-it-yourself (DIY) builds, you may find help from the community in our DIY forum.
The best way to get started is to send us a bug report
or pull request on Github.
You can also chat with Kegbot devs in
Right now, our focus is on supporting non-commercial, home/office users.
However, we're constantly working on new opportunities for Kegbot, and we do know of multiple commercially-installed Kegbot systems. For more information, contact our parent company, Bevbot LLC.
We've worked hard for our name! Especially because of misunderstandings in the past, we kindly ask that you do not use the Kegbot name without our prior written permission.
We always make an exception for free, open source projects that are designed
to work with the Kegbot system: for
If in doubt, get in touch! We're nice, and will try to respond quickly.