CloudBeaver AWS

What do you like best about the product?

I really like the multi-data and data exploration capabilities of DBeaver. With this single tool, I can manage SQL Server, PostgreSQL, and MongoDB. It makes SQL and query writing easy, provides the facility to easily store tables, schemes, and relationships. Data filtering, sorting, and searching can be done very effectively. Export and import features are very useful during data analysis. The most valuable thing is that you don't have to switch between different tools repeatedly for data-based validation and distribution, which makes data verification or issue investigation during QA much faster and easier.

What do you dislike about the product?

Yes, overall DBeaver has been quite good, but there are some areas where improvement is needed, such as when working with very large datasets or complex queries, the performance sometimes feels slow. For beginners, the interface can be a bit complex because there are a lot of options and features available. Resource consumption also feels quite high, especially during large performances.

What problems is the product solving and how is that benefiting you?

I use DBeaver for data validation services, which makes it easy to manage different databases with a single tool. It reduces troubleshooting time for QA and development teams and makes managing complex queries easier.

I have been using CloudBeaver AWS for around 5 to 6 months.

My main use case for CloudBeaver AWS is managing and monitoring multiple databases from a single web interface. As an embedded and IoT focused developer, I mostly use it to check the device logs, validate MQTT related data stored in the database, run SQL queries for debugging, and monitor real-time system data during testing and development. It is especially useful when working remotely because I can access everything through the browser without installing heavy database tools locally.

Recently, I used CloudBeaver AWS while testing an IoT fuel station controller system connected through an MQTT and RabbitMQ. One issue we faced was that pump status updates from one device were not reaching the back-end correctly. Using CloudBeaver AWS, I connected directly to the AWS hosted PostgreSQL database and monitored the incoming records in real-time. I ran SQL queries to compare the time when MQTT messages were received from the device, RabbitMQ processed the data, and the final database entry was stored in the system. That helped me quickly identify that the message ID mapping for tank status and pump status was incorrect in the consumer logic. Instead of debugging through logs alone, I could instantly verify whether the live data was getting inserted correctly into the database tables. It saved a lot of time because I did not need separate database client tools or server access. Everything was accessible from the browser itself.

One of the best features CloudBeaver AWS offers is that it combines database management, monitoring, and collaboration into a single browser-based interface. The features I find most useful are web-based access so I can connect to the database from anywhere without installing separate database clients, and support for multiple databases. It works with PostgreSQL, MySQL, SQL Server, and others from one dashboard. Additionally, real-time query execution is particularly helpful for checking live system data and troubleshooting issues quickly.

The ability to connect from anywhere has improved collaboration and a lot of our workflows because the whole team could access the same database environment directly through the browser, even while working remotely or from different locations. Earlier, each developer had separate local database tools and configuration, which sometimes caused version mismatches or access issues. With CloudBeaver AWS, everyone works from a centralized setup, so debugging and monitoring become much more consistent.

I really liked the UI. It is clean, lightweight, and easy to navigate, even when handling multiple databases and large tables. The dashboard feels much simpler compared to many traditional database tools, which reduced the learning curve for new team members. I also appreciated how smoothly it integrates with cloud-hosted environments and different database engines. Since our system involves IoT devices, MQTT service, back-end APIs, and database monitoring together, having a centralized browser-based database tool helps keep the workflow organized.

CloudBeaver AWS has positively impacted my organization mainly by improving debugging speed, team collaboration, and operational efficiency. One major benefit we noticed was reduced troubleshooting time. Earlier, when there was an issue with IoT device communication or back-end data flow, different teams had to rely on separate tools, exported logs, or direct server access. But after using CloudBeaver AWS, developers and testers could instantly verify live database entries from a shared interface, which helped us identify issues much faster.

CloudBeaver AWS already covers most core database management needs very well, but a few improvements could make it even better for teams working with real-time systems and cloud monitoring. One thing I would like to see is a more advanced real-time monitoring dashboard built directly into the platform. Right now, it is great for querying and checking live data, but having customizable live widgets for alert panels for database active, failed queries, or IoT event streams would be really useful.

From the UI side, the interface is clean already, but advanced filtering and dashboard customization options could improve the experience further for enterprise-scale monitoring environments.

I have been working in my current field for 1.5 years.

CloudBeaver AWS has not experienced any stability issues.

CloudBeaver AWS's scalability is quite good, especially for teams working in a cloud-based environment.

Customer support is good.

Before adopting CloudBeaver AWS, we mainly relied on a mix of traditional desktop database tools like DBeaver and other standalone SQL clients, depending on the database type and team preference. Those tools worked well individually, but the challenge was that every developer had separate local configurations, different client versions, and different access methods. During remote collaboration or troubleshooting sessions, that sometimes created delays and inconsistencies. We switched to CloudBeaver AWS mainly because we wanted a centralized, browser-based solution, easier remote access, simpler team collaboration, and more consistent database management across the organization.

We adopted CloudBeaver AWS through the AWS ecosystem, and using the AWS Marketplace made the deployment and setup process much smoother.

We did not require an implementation team.

We saw a positive return on investment after implementing CloudBeaver AWS. The biggest impact was in time savings and operational efficiency rather than reducing headcount. A few measurable improvements we noticed were around 30 to 40% faster troubleshooting for database and back-end-related issues, significantly reduced setup time for new developers and testers, and fewer delays caused by access or environment configuration problems. For example, before using CloudBeaver AWS, debugging an IoT communication issue could take one to two hours, but after using CloudBeaver AWS, it took around 20 to 30 minutes using the shared browser-based interface.

Before selecting CloudBeaver AWS, we evaluated a few other database management solutions, including DBeaver, PGAdmin, and some other traditional desktop-based SQL clients commonly used for PostgreSQL and MySQL environments. We also looked at a few cloud-native database management approaches provided within AWS services.

CloudBeaver AWS should be evaluated not just as a database query tool but as a collaboration and operational efficiency platform for cloud environments. If a team works remotely, manages multiple databases, or frequently handles debugging and monitoring tasks, the browser-based, centralized approach can save a significant amount of time and reduce complexity. It is especially recommended for cloud-native teams, DevOps and back-end engineers, IoT and real-time system monitoring, and organizations that want easier database access and management across the team. I would rate my overall experience with CloudBeaver AWS a 10.

Public Cloud

Amazon Web Services (AWS)

What do you like best about the product?

What I like best about DBeaver is how easy it makes working with multiple databases in one place. Instead of switching between different tools, everything is available in a single interface, which really improves daily workflow.

The UI is clean and practical, and once you get used to it, navigating through tables, queries, and schemas feels straightforward. It is not flashy, but it is efficient, which is what matters most for database work.

Integration support is another strong point. It works with a wide range of databases, so it fits well into different projects without needing extra tools. This flexibility saves a lot of setup time.

Performance is generally solid even when working with large datasets. Query execution and browsing data feels smooth in most cases, which helps when working under time pressure.

From a pricing and ROI perspective, the free version already offers a lot of value. It covers most daily needs without requiring an upgrade, which makes it a cost effective choice for individuals and teams.

Support and onboarding are decent, and while it is not heavily guided, the tool is intuitive enough that most things can be figured out quickly with basic experience.

What do you dislike about the product?

One thing I do not like about DBeaver is that the interface can feel a bit cluttered at times. There are many options and panels available, which is powerful, but it can also make it harder to quickly find what you need, especially for new users.

Another challenge is performance when working with very large datasets. It generally works well, but in some cases scrolling through big tables or running heavy queries can feel slower compared to lighter tools, which can affect productivity a bit during peak work.

The onboarding experience could also be smoother. While the tool is flexible, it does not always guide new users through advanced features, so there is a bit of trial and error involved in the beginning.

From an integration perspective, it supports many databases, which is great, but setting up certain connections sometimes requires extra configuration steps that are not immediately obvious.

Overall, it is a very capable tool, but a bit more simplicity in the UI and improved performance consistency would make the experience even better.

What problems is the product solving and how is that benefiting you?

Before using DBeaver, working with different databases meant switching between multiple tools depending on the system. It slowed things down and made it harder to keep a consistent workflow across projects.

With DBeaver, everything is now in one place. It supports multiple database types in a single interface, so it is much easier to run queries, compare data, and manage schemas without constantly changing tools. This has saved a noticeable amount of time during daily work, especially when handling multiple environments at once.

Query execution and data browsing are also more efficient now. Tasks that used to take extra steps or tool switching can be done directly in one workspace, which has improved overall productivity and reduced friction in development and analysis work.

It has also helped reduce dependency on multiple paid tools since the free version already covers most use cases. Overall, it has simplified database management and made day to day work more organized and faster.

What do you like best about the product?

It worked well when connecting to different types of databases, and I found the setup straightforward overall.

What do you dislike about the product?

It’s not very straightforward to use, and it isn’t as easy as its competitors.

What problems is the product solving and how is that benefiting you?

Connecting to MySQL databases from Linux without having to rely on the command line.

What do you like best about the product?

Ease of connecting to a variety of RDMS systems.

What do you dislike about the product?

Nothing in particular to point out at the moment; so far, it meets all my requirements.

What problems is the product solving and how is that benefiting you?

Managing, connecting to, and querying RDBMS databases, including on-premises systems and cloud-hosted MySQL databases in particular.

My main use case for CloudBeaver AWS is web-based database access that I can utilize for my entire distributed teams for training and modeling machine learning use cases. For any centralized database management, such as all connections, credentials, and configurations that we need to manage, I can do it perfectly inside CloudBeaver whenever we are using AWS cloud for any model instances or model training on SageMaker. I utilize S3 and EC2 instances for uploading data, but whenever I use CloudBeaver, I can run higher power queries as well, such as whatever it supports in MySQL, PostgreSQL, or MongoDB. All that kind of multi-database support is available inside CloudBeaver AWS. There is easy governance and we can utilize all kinds of local tools as well and easily deployable on EC2 instances or if you want to do it on Kubernetes pods scale then EKS can be utilized as well. Even there are lots of RBAC policies available as well, such as Role-Based Access Control where who can access which databases can be configured and it is very friendly in collaboration.

Whenever I utilize my whole use cases for project delivery in my setup of AI architecture or if any data that I want to look out for in AWS RDS, I will jump into CloudBeaver on EC2 and then will look out for the browser. My whole teams or any groups or any collaboration analytics can be identified and then I can have a Python notebook on top of it for model training. Basically I can connect my database to CloudBeaver tool and can perform all kinds of feature engineering via SQL. I can export my whole data for machine learning model training, and I can get the insights as well. That is the main use case I am trying to set up for CloudBeaver tool in AWS for database extraction process.

My team collaborates within CloudBeaver AWS by utilizing the collaboration option to work out. In the specific organization scenario, if I am having multiple tables or if I want to join the SQL use cases, then I can make some kind of collaboration and I can connect the database to CloudBeaver, do some feature engineering, and model training will be done. Whenever I want to collaborate with my team, I will identify the role-based accesses for all the features and I can give the permissions as well to that whole database and I can make the tracking as well on top of it of how it is getting utilized, how heavy workflows are integrated, and what kind of training setups are done as well. My accesses can be controlled. My role-based access control can be very smooth in CloudBeaver as well here in AWS and it can be very suitable for any machine learning tasks or any data science-related activities.

The best features CloudBeaver AWS offers are basically very good for SQL access on AWS. From any RDS, I can collaborate or access any databases and then can jump out towards modeling and can store the models as well. SQL exploration is very smooth. I am getting IAM roles access perfectly. Static credentials can now be changed into IAM accesses and role-based access controls are available as well, secured enough, and perfect enough. Browser-specific database is available so I can control it with any read-write permissions and any queries can be heavily managed as well. Workflow can be added and it can be perfectly managed altogether. All things can be connected, external database or if you have any data warehouses, then also inside CloudBeaver, I can access all these kinds of things. I can make connections to RDS or external databases or any warehouses. All things can be easily configured. I can run my SQL in the browser. I can save the queries. I can run the joins or aggregations that I need to comply on. All of these things is very smooth in CloudBeaver.

The feature that has made the biggest difference for my day-to-day work is browser-based database control, which is very easier in terms of how practical scenarios work. Role-based accesses can be easily assigned as well. Those use cases are very useful for any project delivery. Let me go through one of the project requirements or use cases that I have taken out inside CloudBeaver and how it tailored the whole prospect to understand this thing. The use case is that I am working out with a healthcare-based project where the doctor needs to maintain the kidney reports of the patient. When doctors log into CloudBeaver, the browser-based database, and they will query the patient data. They can get the high-risk patients directly by filtering the patients and can export the reports and share the insights directly. This is how it is very important to identify that just by taking out some kind of clicks, I can get out the whole report and insight and it can be shared as well. It is on the cloud of AWS that is again an achievement. That is where it made the biggest differences.

CloudBeaver AWS has positively impacted my organization because all kinds of browser-based accesses can be made and I can have role-based use cases as well. That gives us the clarity of how the use cases can be covered together and what can be the specific criteria to understand on an organizational level and I can give the accesses towards them as well. In that regard, our organization has maintained this perfectly.

Since using CloudBeaver AWS, my organization has experienced many positive outcomes. Collaboration within the team is perfect. I can manage out what kind of work the team is doing, how the roles can be assigned as well, how their model, how their database is working on the model and we can trace it perfectly as well. That gives me the access to work out on different cardinalities as well. In that regard, I can identify how the costing of the database can be managed as well, what kind of cloud services I can utilize within this whole actionable insights as well. On top of it, whatever the machine learning model that I am building, how efficiency can be generated on the direct SQL queries and the insights can be gained as well. That will analyze my whole results. In that regard, my efficiency and accuracy of the whole approach gets increased and I will be getting out high-level scenarios as well to work out on the cloud instances.

CloudBeaver AWS can be improved because in rendering of the queries, if it is very complex or big, the responses in the browser get slowed down. Compared to DBeaver of desktop, it is noticeably very slower on the browser of AWS and heavy data engineering can be done, but it will have very slow responses configured altogether. That needs to be maintained. Even there is no connectivity of machine learning, MLflow kind of thing where Airflow or PySpark approaches can be integrated. Python pipelines can be created but the whole end-to-end machine learning pipeline gets stuck whenever we work out with DBeaver. That again is one of the issues that I would look out for to improve. Also, I need to maintain the infrastructure perfectly here. I need to manage it and need to identify the risks as well. The whole proper setup of VPCs or IAMs needs to be done. It is not a NLQ kind of thing. User queries need to be configured in manual approaches, not automated currently. It should be automated now. Debugging is very painful. That again is a vague approach here. Errors can be executed and we will not be getting out the clarity as well. During this whole approach, the logs are not perfect and intuitive and debugging is also very limited.

The user interface and documentation look good, but I would still suggest improvements.

I have been using CloudBeaver AWS for more than two years.

CloudBeaver AWS is stable.

The customer support is always top-notch. AWS itself gives me the responses that the customer support team will give me guidance. AI is also integrated for ticket generation and evaluation as well. I receive quicker responses on the pre-generated content of the query response that I am looking out for. That support is again very excellent.

I was using cloud solutions from the start of my work, but I also worked on local instances of databases such as MySQL, PostgreSQL, or MongoDB. In comparison, the cloud scenario based which directly worked with CloudBeaver and that worked fine. It is user-friendly as well. The UI is very attractive. You would not be getting bored. Also, everything is perfectly managed, analysis is available. AI integrations are now supported. SAP integrations are getting applied as well. There are many things you can try to work it out here.

My experience with pricing, setup cost, and licensing is that whenever we had to purchase the organization-level subscription for particularly CloudBeaver, first of all, it is free and open source. No licensing cost comes into picture. You just need to pay for AWS infrastructure here. The same goes with pricing and costing. It is very simpler in how we need to maintain CloudBeaver. You just need to pay the infrastructure cost of what utilizes more of your instances, such as EC2 instance, storage of EBS or RDS or anything or any network charges. If we take out any enterprise-based edition, then it starts within a suitable line but goes till very high-based versioning costing as well. That pricing is very suitable to understand how the quality and quantity of the features are inside CloudBeaver. It gives you the 14 days free trial as well for the enterprise level. To deploy CloudBeaver, it is very much easier as well. Directly your payment and costing will be integrated from AWS. Pricing can be set up on AWS infrastructure as well and we can collaborate within the teams on the setup of the production as well. Charges are higher, but it is bearable whenever we look out for the enterprise level addition, but still if it can try to reduce the market level, then it can be more achievable, more approachable as well in terms of what is the current product scenarios on different tools for database accesses as well.

CloudBeaver AWS is deployed in my organization as a public cloud.

I purchased CloudBeaver AWS through the AWS marketplace.

I have seen a return on investment because time is saved on many things. As I have told, on multiple projects I have worked on CloudBeaver, but as on the doctor's example that I have given, it can generate the reports of multiple patients altogether. Queries can be slower if they get complex, but it reduces much time as well. If your quantity and size of data are very less, then you would go for a lower or free tier-based mechanism, but if it is having higher and higher based quantity of data, then you would go for some higher approaches. Your infrastructure cost will go higher, but on top of it, your results will be accurate, perfectly managed, secured, encrypted, and efficient enough to understand the quantity, also clickable. Browser-friendly responses are available so you can analyze your data. You can work out with the queries as well. All these things will try to increase the enhancement of software development or any data science development work as well.

I have not evaluated other options since I have worked out mostly on AWS. That would be my go-to option.

I totally recommend others looking into using CloudBeaver AWS to work it out. It is very smooth, but if you are a data scientist, then your end-to-end approach will not be perfectly worked. All the database approaches, if you are looking out for on cloud instance, you can directly integrate CloudBeaver to work out on your databases or any credential works as well. I would rate this product a 7 out of 10.

Public Cloud

Amazon Web Services (AWS)

What do you like best about the product?

DBeaver is great because it lets me work with almost any database in one place. The UI is clean and easy to navigate, and it makes querying and editing data straightforward. I also appreciate the handy extras like ER diagrams, export options, and SSH support, while still being free and simple to use.

What do you dislike about the product?

DBeaver can feel a bit laggy at times, and it tends to slow down even more when I’m working with large datasets.

On the plus side, setup in DBeaver has been pretty easy for me, with no issues there. The only thing I haven’t really tried yet is the AI features, so I can’t say how useful they are for real day-to-day work.

What problems is the product solving and how is that benefiting you?

DBeaver removes the hassle of juggling multiple database tools by bringing everything into one place. I can connect to different databases, run queries, and review data easily, which saves me a lot of time. It also speeds up debugging and data validation, which is especially helpful during testing, analysis, or general troubleshooting.

What do you like best about the product?

I like that it can manage multiple databases at the same time. I also like the tabbed queries, which make it easier to keep several queries open and switch between them.

What do you dislike about the product?

The UI feels cumbersome for a new user. I’m sure DBeaver can do many things that I just haven’t found yet, mainly because I find the help guides difficult to learn from. It also loses connection to my various databases, and the only way I’ve been able to restore it is by restarting the app.

What problems is the product solving and how is that benefiting you?

It lets me work across several databases at the same time. I can run multiple queries without having to open separate apps, which keeps everything in one place. The ability to copy, paste, and sort the query results is also very helpful when I’m trying to find specific pieces of data.

What do you like best about the product?

What I like most about DBeaver is how it lets me work with multiple databases in one place through a clean, intuitive UI. I regularly rely on the SQL editor, especially the auto-completion and query execution history, which make writing, troubleshooting, and debugging queries much faster. The data viewer is also very useful for quickly reviewing and analyzing table data without having to write additional queries.

I also find the connection management features valuable, since they make it easy to set up and manage database connections and switch between different environments without any hassle. Overall, DBeaver improves my workflow by keeping database testing, validation, and data analysis more efficient, organized, and straightforward.

What do you dislike about the product?

One downside is that DBeaver can feel slow or resource-heavy, especially when working with large datasets or multiple connections. Sometimes the UI becomes slightly cluttered, making navigation a bit confusing for new users. Additionally, advanced features and configurations can have a learning curve, which may take time to get used to.

What problems is the product solving and how is that benefiting you?

DBeaver solves the problem of managing and querying multiple databases from a single platform. It allows me to easily write, execute, and debug SQL queries while also providing a clear view of table data and database structure. This benefits me by saving time, reducing dependency on multiple tools, and making data validation and analysis more efficient during testing.

What do you like best about the product?

Managing the database connection is really good.

What do you dislike about the product?

The backup process could be improved significantly.

What problems is the product solving and how is that benefiting you?

It solves my issue of working with multiple databases at the same time, and it also makes searching the DB much easier.