No more typing reviews! Try our Samantha, our new voice AI agent.

1NCE vs ClickHouse comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Nov 23, 2025

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

1NCE
Average Rating
7.0
Number of Reviews
1
Ranking in other categories
IoT Connectivity (9th)
ClickHouse
Average Rating
8.6
Reviews Sentiment
6.8
Number of Reviews
21
Ranking in other categories
Open Source Databases (3rd), Vector Databases (7th)
 

Mindshare comparison

1NCE and ClickHouse aren’t in the same category and serve different purposes. 1NCE is designed for IoT Connectivity and holds a mindshare of 2.9%.
ClickHouse, on the other hand, focuses on Open Source Databases, holds 6.4% mindshare, up 4.4% since last year.
IoT Connectivity Mindshare Distribution
ProductMindshare (%)
1NCE2.9%
AWS IoT Core22.4%
EMQX11.8%
Other62.900000000000006%
IoT Connectivity
Open Source Databases Mindshare Distribution
ProductMindshare (%)
ClickHouse6.4%
PostgreSQL13.1%
MySQL11.4%
Other69.1%
Open Source Databases
 

Featured Reviews

Mahesh Konda - PeerSpot reviewer
Solution Architect at Synechron
Centralized device connectivity has improved operations but monitoring integrations still need work
The best features of 1NCE that I can recollect would be the connectivity management model of an operational architecture from an operational architecture standpoint. Because I have been working as a solution architect for over five to six years, having a centralized management visibility for IoT connected devices across distributed deployments is very useful. Regarding centralized management, the capability helped in giving the operations and engineering teams the ability to monitor and check the connectivity status, outages, device activity, and all that. That is one better use case. Instead of coordinating with different providers, the visibility and monitoring is key for any infrastructure. Provisioning through one platform is one of the best use cases. From an architecture perspective, having consolidated visibility also made it easier to track the behavior and maintain consistency of the distribution deployments. I would repeat that what is primarily important is about the deployments, visibility, and the engineering teams in one place. That is something good with the best use case of the application. Instead of coordinating with different providers or handling fragmented visibility, the team could manage provisioning, troubleshooting, and monitoring more efficiently through one platform.
reviewer2785038 - PeerSpot reviewer
Senior Data Engineer at a transportation company with 501-1,000 employees
Data observability has enabled real‑time analytics and cost savings but needs smoother inserts and cleanup
ClickHouse could be improved concerning data insertion, especially given the high amount of data handled. Constant efforts are made to optimize the features on its own, but with merges and inserts, only a single insert query can be performed allowing for the input of only 100,000 rows per second. It would be beneficial to insert more data and have configurations that are less user-operated. Ideally, ClickHouse would optimize itself to handle these processes automatically, reducing the need to contact the ClickHouse support team for infrastructure optimization. Additionally, delays are experienced when trying to delete databases with corrupt data, taking too much time and causing major outages, which necessitate contacting multiple teams across continents for resolution. The community surrounding ClickHouse also seems limited, providing a reliance on documentation, and there is a scarcity of developers working with ClickHouse, which hinders growth. If ClickHouse were more user-friendly and technically feasible, it would likely see greater expansion in usage.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"Instead of coordinating with different providers, the visibility and monitoring is key for any infrastructure, and provisioning through one platform is one of the best use cases."
"The tool's most valuable feature is a database. It supports portal APIs and offers good flexibility."
"ClickHouse is open source with no vendor lock-in, providing excellent freedom to choose any vendor without restrictions."
"ClickHouse is much faster than traditional databases like MySQL and MongoDB. Its column-row searching strategy makes it very efficient. With ClickHouse, we can manage multiple databases, automatically insert data from other databases and delete data as needed. It supports real-time query performance, allowing simultaneous data insertion and retrieval. ClickHouse has improved significantly over the past two years, adding more functions and queries, as well as top functionality."
"The main feature of ClickHouse is the optimizer because we had too many records to deduplicate, and the optimizer took this task by itself."
"We faced a challenge with deploying ClickHouse onto Kubernetes. Recently, we've been using ClickHouse Cloud, and the main issue is the high cost of the cloud service. The pricing isn't very competitive, especially for startups. I would instead buy a server and self-host if I have enough disk space. Besides that, ClickHouse has done very well, with clear goals and effective execution."
"The tool is column-based and infinitely scalable."
"With ClickHouse, since data is stored in a columnar way, we get aggregation functions that are much faster than transactional databases, such as SQL Server, and the cost efficiency is also much reduced compared to Cosmos DB since we use it on-premises, the cost is nearly cut, which is very useful for us."
"ClickHouse provides responses within a few seconds, typically two to three seconds, which is impressive."
 

Cons

"The areas for improvement could be around analytics and reporting flexibility."
"My experience with pricing, setup cost, and licensing indicates that it is very expensive—ClickHouse is the most expensive option."
"The aggregation capability is a valuable feature. It's highly efficient, allowing us to review entire transaction histories and user activities in the market. We've tried MongoDB, Postgres, MariaDB, and BigQuery, but ClickHouse is the most cost-efficient solution for collecting data at high speeds with minimal cost. We even used ClickHouse Cloud for a month, and it proved to be a great setup, especially for startups looking to handle big data. For example, if there is a need for 2-4 terabytes of data and around 40 billion rows with reasonable computing speed and latency, ClickHouse is ideal. Regarding the real-time query performance of ClickHouse, when using an API server to query it, I achieved query results in less than twenty milliseconds in some of my experiments with one billion rows. However, it depends on the scenario since ClickHouse has limitations in handling mutations. Additionally, one of ClickHouse's strengths is its compression capability. Our experimental server has only four terabytes, and ClickHouse effectively compresses data, allowing us to store large amounts of data at high speed. This compression efficiency is a significant advantage of using ClickHouse."
"There aren't too many improvements I'd suggest for ClickHouse as it covers all my needs. There are just a few technical issues. For example, sometimes, when you want to get unique values and use certain tables, they don't work as expected. But it's not a major problem."
"Additionally, delays are experienced when trying to delete databases with corrupt data, taking too much time and causing major outages, which necessitate contacting multiple teams across continents for resolution."
"There are some areas where ClickHouse could improve. Specifically, we encountered incompatibilities with its SQL syntax when migrating queries from MySQL or SQL to ClickHouse. This difference in details made it challenging to figure out the exact issues. Additionally, we faced difficulties due to the lack of a proper Django driver for ClickHouse, unlike MySQL, which Django supports out of the box."
"We had a lot of troubles while deploying a whole cluster."
"Initially, I faced challenges integrating ClickHouse, particularly with inserting data from ActiveMQ, which caused duplicates. However, after adjusting the ClickHouse settings, the issue was resolved and there were no more duplicates."
"ClickHouse could be improved with self-hosting capabilities and better documentation for how to host it at scale."
 

Pricing and Cost Advice

Information not available
"We used the free, community version of ClickHouse."
"For pricing, if you use the self-hosted version, it would be free. Cloud services pricing would be an eight out of ten. I try to minimize costs but still have to monitor usage."
"If you have an in-house deployment on Kubernetes or something, it's going to be very cheap since you'll be managing everything."
"ClickHouse has an open-source version, which is free to use and has almost all the features."
"The tool is free."
"ClickHouse Cloud is not expensive compared to other databases, costing a few dollars per month while providing fast performance."
"The tool is open-source."
report
Use our free recommendation engine to learn which IoT Connectivity solutions are best for your needs.
899,125 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Construction Company
34%
Outsourcing Company
11%
Financial Services Firm
10%
Educational Organization
8%
Financial Services Firm
16%
Computer Software Company
13%
Outsourcing Company
9%
Comms Service Provider
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Midsize Enterprise2
Large Enterprise8
By reviewers
Company SizeCount
Small Business12
Midsize Enterprise5
Large Enterprise8
 

Questions from the Community

What needs improvement with 1NCE?
The areas for improvement could be around analytics and reporting flexibility. While the platform provides good operational visibility, having more customizable dashboards and deeper reporting capa...
What is your primary use case for 1NCE?
I have been using 1NCE for over a year and a half. Primarily, it is a solution for IoT connectivity and device communication use cases across distributed environments. My primary use case for 1NCE ...
What advice do you have for others considering 1NCE?
1NCE is a good product and I would recommend this. I would rate this review a 7.
What is your experience regarding pricing and costs for ClickHouse?
My experience with pricing, setup cost, and licensing was such that the setup costs were just my own bandwidth, while licensing and pricing were done by other members of the team so it was abstract...
What needs improvement with ClickHouse?
ClickHouse can be improved on the documentation side, and there is one small constraint that is mentioned in ClickHouse documentation, which is a partition limit of ten thousand that we hit, so if ...
What is your primary use case for ClickHouse?
My main use case for ClickHouse is data ingestion and for its OLAP properties, as we had use cases where database locks were slowing us down and because ClickHouse does not have that, we chose to u...
 

Comparisons

No data available
 

Overview