Beekeeper Studio is a cross-platform SQL editor and database manager available for Linux, Mac, and Windows. Beekeeper Studio is GPL licensed so it is free (libre) and free (gratis).
-
Beekeeper Studio Community Edition - This repository. This is the open source version of Beekeeper Studio. It is a full featured database management client that is totally free and open source.
-
Beekeeper Studio Ultimate Edition - A commercial version of Beekeeper Studio with extra features and provided with a business-friendly commercial license.
👉 Compare Beekeeper Studio Editions
Top feature: It's smooth 🍫, fast 🏎, and you'll actually enjoy using it 🥰
- Truly cross-platform: Windows, MacOS, and Linux
- Autocomplete SQL query editor with syntax highlighting
- Tabbed interface, so you can multitask
- Sort and filter table data to find just what you need
- Sensible keyboard-shortcuts
- Save queries for later
- Query run-history, so you can find that one query you got working 3 days ago
- Default dark theme
One of our frustrations with other open-source SQL editors and database managers is that they take a 'kitchen sink' approach to features, adding so many features that the UI becomes cluttered and hard to navigate. We wanted a good looking, open source SQL workbench that's powerful, but also easy to use. We couldn't find one, so we created Beekeeper Studio!
Beekeeper Studio supports connecting to the following databases:
- SQLite
- MySQL
- MariaDB
- Postgres
- CockroachDB
- SQL Server
- Amazon Redshift
Download the latest release from our website
Check out docs.beekeeperstudio.io for user guides, FAQs, troubleshooting tips, and more.
Beekeeper Studio Community Edition (the code in this repository) is licensed under the GPLv3 license.
Beekeeper Studio Ultimate Edition contains extra features and is licensed under a commercial end user agreement (EULA).
Beekeeper Studio's trademarks (words marks and logos) are not open source. See our trademark guidelines for more information.
Trademarks can be complicated with open source projects, so we have adapted a set of standard guidelines for using our trademarks that are common to many open source projects.
If you are just using the Beekeeper Studio app, and you are not forking or distributing Beekeeper Studio code in any way, these probably don't apply to you.
👉 Beekeeper Studio Trademark Guidelines
We love any community engagement. Even if you're complaining because you don't like something about the app!
-
Building an inclusive and welcoming community is important to us, so please follow our code of conduct as you engage with the project.
-
By contributing to the project you agree to the terms of our contributor guidelines.
We have you covered, read our guide to contributing in 10 minutes without coding.
Want to write some code and improve Beekeeper Studio? Getting set-up is easy on Mac, Linux, or Windows.
# First: Install NodeJS 12 or 14, NPM, and Yarn
# ...
# 1. Fork the Beekeeper Studio Repo (click fork button at top right of this screen)
# 2. Check out your fork:
git clone [email protected]:<your-username>/beekeeper-studio.git beekeeper-studio
cd beekeeper-studio/
yarn install # installs dependencies
# Now you can start the app:
yarn run electron:serve ## the app will now startThis repo is now a monorepo, we have several places with code, but only really a couple of important entry points.
All app code lives in apps/studio, some shared code lives in shared/src. This is shared with other apps.
Beekeeper Studio has two entry points:
background.js- this is the electron-side code that controls native things like showing windows.main.js- this is the entry point for the Vue.js app. You can follow the Vue component breadcrumbs fromApp.vueto find the screen you need.
Generally we have two 'screens':
- ConnectionInterface - connecting to a DB
- CoreInterface - interacting with a database
- Push your changes to your repository and open a Pull Request from our github page (this page)
- Make sure to write some notes about what your change does! A gif is always welcome for visual changes.
- Up the version number in package.json
- Replace
build/release-notes.mdwith the latest release notes. Follow the format that is there.
- run
git log <last-tag>..HEAD --oneline | grep 'Merge pull'to find PRs merged
- Commit
- Push to master
- Create a tag
git tag v<version>. It must start with a 'v' git push origin <tagname>
- Now wait for the build/publish action to complete on Github
- Push the new release live
- Go to the new 'draft' release on the releases tab of github, edit the notes, publish
- Log into snapcraft.io, drag the uploaded release into the 'stable' channel for each architecture.
This should also publish the latest docs
Post Release:
- Copy release notes to a blog post, post on website
- Tweet link
- Share on LinkedIn
- Send to mailing list on SendInBlue
Beekeeper Studio wouldn't exist without Sqlectron-core, the core database libraries from the Sqlectron project. Beekeeper Studio started as an experimental fork of that repository. A big thanks to @maxcnunes and the rest of the Sqlectron community.