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

Claris FileMaker vs InfluxDB comparison

Why PeerSpot?
 

Comparison Buyer's Guide

Executive Summary

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

Claris FileMaker
Ranking in Non-Relational Databases
3rd
Average Rating
7.6
Number of Reviews
5
Ranking in other categories
No ranking in other categories
InfluxDB
Ranking in Non-Relational Databases
1st
Average Rating
8.0
Reviews Sentiment
6.5
Number of Reviews
20
Ranking in other categories
Open Source Databases (7th), Network Monitoring Software (14th), IT Infrastructure Monitoring (12th), NoSQL Databases (6th)
 

Mindshare comparison

As of October 2026, in the Non-Relational Databases category, the mindshare of Claris FileMaker is 6.3%, up from 4.5% compared to the previous year. The mindshare of InfluxDB is 6.6%, down from 7.8% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Non-Relational Databases Mindshare Distribution
ProductMindshare (%)
InfluxDB6.6%
Claris FileMaker6.3%
Other87.1%
Non-Relational Databases
 

Featured Reviews

it_user1540227 - PeerSpot reviewer
Computer Manager at a university with 10,001+ employees
User-friendly, very stable, reasonable price, integrates well, and has all sorts of capabilities
They're always improving it, and I have been quite pleased with their improvements. There is some organizational stuff that I'd like to see done differently. They should make a structure so that you can have the data in one file and the app, the scripts, and the program in another file. I would like to be able to easily share scripts between different databases. I write stuff, and some of the functions are shared across different databases. So, I have to copy them from one database to another. I wouldn't mind an infrastructure where I had a file, and on loading the program, this file is loaded with the functions that I had written. I can then call them from any database that I happen to be using. Currently, you have a database open that has all of its data pieces and program pieces, and then you open another database that has got all of its data pieces and program pieces. Nothing is shared between them. When I write a complex function and I want to use it in two or three different databases, I have to copy it to each one of them and also remember where all it is used. It would be good if it has a little bit different organizational structure so that you could put your shared stuff in one place, and it loads the stuff. It is just an architectural difference. I've sent this requirement to them, but I doubt if that's going to happen. It is a huge system, and making changes for a single individual doesn't happen that quickly.
Mugeesh Husain - PeerSpot reviewer
Team Lead, Software at Energybox
Time series data has been managed efficiently for IoT sensors but reporting still needs improvement
How InfluxDB can be improved is relevant since for Energy Box, we face certain issues. We have customers worldwide, including the United States, United Kingdom, and Europe, but when we expanded to China two years ago, they indicated that they do not support the cloud version there. Our application is built on the cloud, which required us to create a separate application for Azure China, which was painful for us. The second issue involves frequent version changes. For example, we started with version one, transitioned to version two, and I heard they are considering InfluxDB version three, reverting to earlier practices. InfluxDB should improve without completely changing its approach. Now we have to redo our work for InfluxDB version three. Regarding needed improvements, the documentation is sufficient, but pricing presents a challenge. InfluxDB has standard pricing, which is acceptable for large companies. However, for startups in our position, they should provide special discounts so everyone can utilize it. The pricing should adapt as companies grow, which is a reasonable expectation.

Quotes from Members

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

Pros

"I love this product; I have been using it for 30 years, and it has got lots of capabilities, so don't sell it short because it can do a lot more than you might think it can."
"I have found its resilience to attack most valuable; it's really difficult to attack the software and it's really stable as well."
"It is a great starter to commence with in the world of database management, even if you have limited development knowledge and is a sure bet for professional and long term expansion."
"FileMaker is much easier, it's a pretty good tool and there's a lot of support and there's a lot of people out there that know how to use it."
"The database is the most useful aspect of the solution; it's a good application that's easy to use."
"The cross-platform Mac and Windows feature is most valuable. I can do all sorts of stuff with this tool. It has got all sorts of automation capabilities. I have used some of them, but I have barely scratched the surface of what it can do on automation. It is user-friendly, and it integrates well with other products. There are other third-party options that you can buy or in some cases, download for free to even extend it further. I use one or two of those."
"The platform operates very quickly. It is easy to configure, connect, and query and integrates seamlessly with Grafana."
"Prior to InfluxDB usage, real-time data was not visualized and monitored, and after the introduction of InfluxDB in the entire framework, the organization is benefiting a lot in terms of monitoring and understanding performance data in real-time."
"As a time series database, it is very powerful and lightweight, and it can deal with heavy workloads very easily."
"In our case, it started with a necessity to fill the gap that we had in monitoring. We had very reactive monitoring without trend analysis and without some advanced features. We were able to implement them by using a time series database. We are able to have all the data from applications, logs, and systems, and we can use a simple query language to correlate all the data and make things happen, especially with monitoring. We could more proactively monitor our systems and our players' trends."
"The most valuable features of InfluxDB are the documentation and performance, and the good plugins metrics in the ecosystem."
"InfluxDB reduced my time to show data without any interruption, also reducing the number of people needed to manage the project; it is very good to have InfluxDB in my project."
"Because of reduced downtime, we benefit greatly from receiving alerts in advance."
"InfluxDB's best feature is that it's a cloud offering. Other good features include its time-series DB, fast time-bulk queries, and window operations."
 

Cons

"Multimedia data management is not really developed in FileMaker."
"They're always improving it, and I have been quite pleased with their improvements. There is some organizational stuff that I'd like to see done differently. They should make a structure so that you can have the data in one file and the app, the scripts, and the program in another file. I would like to be able to easily share scripts between different databases. I write stuff, and some of the functions are shared across different databases. So, I have to copy them from one database to another. I wouldn't mind an infrastructure where I had a file, and on loading the program, this file is loaded with the functions that I had written. I can then call them from any database that I happen to be using. Currently, you have a database open that has all of its data pieces and program pieces, and then you open another database that has got all of its data pieces and program pieces. Nothing is shared between them. When I write a complex function and I want to use it in two or three different databases, I have to copy it to each one of them and also remember where all it is used. It would be good if it has a little bit different organizational structure so that you could put your shared stuff in one place, and it loads the stuff. It is just an architectural difference. I've sent this requirement to them, but I doubt if that's going to happen. It is a huge system, and making changes for a single individual doesn't happen that quickly."
"The UE is not very up-to-date. It looks like something that was created in the 90s. In that sense, the user experience is lacking."
"It has some limits in terms of scalability. FileMaker is good for small and medium-sized companies. When data grows, in the case of a bigger corporation, it will be difficult to scale it."
"FileMaker has some convoluted pricing."
"Customer Service: We work from Asia and support is particular poor."
"There is some organizational stuff that I'd like to see done differently."
"InfluxDB cannot be used for high-cardinality data. It's also difficult and time-consuming to write queries, and there are some issues with bulk API."
"Customer support is fair enough but can be improved."
"However, I do wish the documentation and community resources around Flux were more extensive and beginner-friendly."
"InfluxDB is generally stable, but we've encountered issues with the configuration file in our ticket stack. For instance, a mistake in one of the metrics out of a hundred KPIs can disrupt data collection for all KPIs. This happens because the agent stops working if there's an issue with any configuration part. To address this, it is essential to ensure that all configurations are part of the agent's EXE file when provided. This makes it easier to package the agent for server installation and ensures all KPIs are available from the server. Additionally, the agent cannot encrypt and decrypt passwords for authentication, which can be problematic when monitoring URLs or requiring authentication tokens. This requires additional scripting and can prolong service restart times."
"One area for improvement is the querying language. InfluxDB deprecated FluxQL, which was intuitive since developers are already familiar with standard querying."
"InfluxDB can improve by including new metrics on other technologies. They had some changes recently to pool data from endpoints but the functionality is not good enough in the industry."
"I chose an 8 out of 10 because there is room for improvement, such as regarding backups and enhanced security through other types of authentication or encrypted data in TLS."
"Sometimes, when we write too much data within a minute, the data count becomes excessive, reaching perhaps 100,000 or 500,000 data points, and InfluxDB gives a timeout exception, which we must handle in our application."
 

Pricing and Cost Advice

"Its price is pretty reasonable. I am at a university. We get educational discount pricing from most of the major vendors."
"The tool is an open-source product."
"InfluxDB is open-source, but there are additional costs for scaling."
"We are using the open-source version of InfluxDB."
report
Use our free recommendation engine to learn which Non-Relational Databases solutions are best for your needs.
915,341 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Comms Service Provider
17%
Outsourcing Company
17%
Manufacturing Company
12%
Construction Company
12%
Comms Service Provider
12%
Manufacturing Company
10%
Financial Services Firm
10%
Outsourcing Company
9%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
By reviewers
Company SizeCount
Small Business9
Midsize Enterprise5
Large Enterprise9
 

Questions from the Community

Ask a question
Earn 20 points
What needs improvement with InfluxDB?
If the dashboarding facility can be improved in terms of the visualization parameters and the amount of support available from the community, as well as having smarter alerts to send those alerts t...
What is your primary use case for InfluxDB?
My main use case for InfluxDB is to inject all my performance data and visualize it as a data source into Grafana. My data comes from JMeter from a plugin, which is inserting data to InfluxDB, and ...
What advice do you have for others considering InfluxDB?
It is good to start with InfluxDB to stabilize your data, visualize your data, and have the data stored on a time-series basis. I would recommend everyone to get into InfluxDB and start using it. T...
 

Comparisons

 

Overview

 

Sample Customers

VUHL, Reynolds Services Inc., Market Refrigeration Specialists, Sea Breeze Farm, Jordan Lindblad, Henry Schein Dental
ebay, AXA, Mozilla, DiDi, LeTV, Siminars, Cognito, ProcessOut, Recommend, CATS, Smarsh, Row 44, Clustree, Bleemeo
Find out what your peers are saying about Claris FileMaker vs. InfluxDB and other solutions. Updated: September 2026.
915,341 professionals have used our research since 2012.