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

LLM Gateway vs Redgate Flyway 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

LLM Gateway
Ranking in AWS Marketplace
17th
Average Rating
8.4
Number of Reviews
6
Ranking in other categories
No ranking in other categories
Redgate Flyway
Ranking in AWS Marketplace
20th
Average Rating
7.6
Number of Reviews
6
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of October 2026, in the AWS Marketplace category, the mindshare of LLM Gateway is 0.2%, down from 0.6% compared to the previous year. The mindshare of Redgate Flyway is 0.2%, down from 0.3% compared to the previous year. It is calculated based on PeerSpot user engagement data.
AWS Marketplace Mindshare Distribution
ProductMindshare (%)
LLM Gateway0.2%
Redgate Flyway0.2%
Other99.6%
AWS Marketplace
 

Featured Reviews

Akashkhurana Hirana - PeerSpot reviewer
Senior Software Engineer 2 at Porch
Centralized AI routing has strengthened data security and simplified multi-model workflows
The best features LLM Gateway offers include multi-provider AI access and the ability to access around 200 plus models available in the market. We just need to pass our key and set up this one, and it can access all the available models. Apart from this, it automatically routes the request based on context if we set it in LLM Gateway. Another feature is the automatic failover functionality where if something goes wrong, it redirects the request to another model. LLM Gateway also provides usage analytics with a dashboard where we can check the current usage of each model and see how many requests are going to each model. It persists data for around 30 days, so we can review usage over the last month. LLM Gateway can be self-hosted as well, which is beneficial for large companies with security concerns. I find multi-provider access and failover to be the most valuable features day-to-day. Multi-provider access integrates all available models, acting as a router between the application and LLM Gateway. If my application is using four different models, I only need to call LLM Gateway, which manages everything. We also do not need to share sensitive API keys, as the developer can directly call LLM Gateway, which handles everything seamlessly. The failover feature automatically redirects requests if something goes wrong in one model, and it is incredibly easy to configure. It does not take more than a minute to set up. One positive impact of LLM Gateway on my organization is reducing security risk. If we give API keys to everyone, they can misuse them outside the organization. However, we no longer share API keys, as users just need to call our LLM Gateway, and the API keys remain secret and contained within our on-premises setup. Security-wise, it has significantly reduced our organization's risk.
Hassan F - PeerSpot reviewer
Full Stack Developer at DPL
Automated database releases have reduced errors and now save a full day of deployment effort
The best features that Redgate Flyway offers, if I had to pick a few that really stand out, would be multi-environment support. On the migrations tab, I do not need to go to an environment and change settings or anything. I simply change the branches of the environment and it shows me what is available and what has been run on a certain environment. The environment feature is very user-friendly and helpful, so I would keep it at the top of my list. The feature of changing branches on the migrations tab is very helpful. An example of how Redgate Flyway specifically helped with discrepancies is that previously we did not have any tool recording database changes. We work on an Agile Scrum pattern, so we have to do deployments frequently, within every two to three weeks or sometimes four weeks. Previously, we had code repositories for front-end and back-end, but for the database side, we did not have any repository. We were not saving database-related changes in any GitHub or AWS CodeCommit repositories. Every time, we have a Jira board where developers update their scripts. For example, if I work on a ticket and update a stored procedure, I must mention the stored procedure on the ticket. When deployment time arrives, the release manager must pull out or scan all the tickets and extract the objects. For example, if we deploy 10 Jira tickets from a sprint in the next release, we must go through all 10 tickets and see the post-deployments of their tickets. Then we extracted the objects from the development environment, deployed on stage, and then deployed on production. In this scenario, many objects and discrepancies occurred. Sometimes a developer or the release manager would forget the object to take to production. Now, after using Redgate Flyway, I have restricted access as the release manager of my team. I manage the release for my team and have restricted developer access to environments other than the development environment. If developers want to take anything to the next environment such as demo, staging, or production, they must make a script. When they create a script, it is in our record. Now, after using Redgate Flyway, we do not need to scan all the tickets on Jira or see the post-deployments of each ticket. We simply view the Redgate Flyway script showing what has been run from this to this version, and what pending deployments need to be run on production. In this way, it has helped tremendously. I can share that the migrations tab and branch changing helped my team in a specific situation during our second last sprint. Two developers were working on the same object, and one change needed to be deployed on stage while another change needed to be deployed on the demo environment, which is our QA level. Our QA and demo are the same environment, and then we have stage and production. We have three environments other than development. Previously, without Redgate Flyway, what could have happened is that we would take the stored procedure from demo if we needed to deploy it on stage and take it directly to stage. This was our previous practice where we would go to the database explorer, take the stored procedure, and move it to the next environment with the ticket. Now with Redgate Flyway, we have different versions of that stored procedure. We simply took the version of the stored procedure that needed to be on stage, and the second version that needed to be on the QA level remained there. Redgate Flyway helped in this case, and we have many cases.

Quotes from Members

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

Pros

"The best features LLM Gateway offers include cost optimization, multi-modal support, and authentication and authorization all in one place."
"What I appreciate most about LLM Gateway is that there is no need to maintain multiple keys."
"We have seen a positive return on investment, reducing the time required to integrate new AI models by around 40 to 50 percent, cutting troubleshooting time by about 30 percent through centralized logging and monitoring, and improving service availability with automatic failover, which has reduced operational overhead and allowed the team to focus more on delivering new features rather than maintaining integrations, resulting in a clear ROI."
"Together, we would estimate a twenty to twenty-five percent lift in engineering productivity on AI work, and from a business angle, new AI capabilities reach production about twenty-five to thirty percent faster because the plumbing is already in place."
"Since adopting LLM Gateway, the complexity of our projects has decreased, the security concerns have lessened, and I estimate it has saved us around 20-30% of our time."
"LLM Gateway is a very efficient solution for what it proposes and I believe it is a solid option if you want to use something that is self-hosted and you can customize extensively."
"Redgate Flyway has positively impacted my organization by maintaining consistency among developers."
"Redgate Flyway has impacted us very positively because we don't have to manually cover all those things."
"I have seen a return on investment with Redgate Flyway in that time was saved significantly for local development."
"Now using Redgate Flyway, we do not need to do any of this procedure, so this whole process has been eliminated, almost a day is saved, and on release day there are 99% chances that the scripts will run successfully without issues."
"Redgate Flyway streamlines the process of database migration and significantly reduces the time for data migration from twenty to twenty-five days down to five to seven days, thanks to the initial time we took for learning."
"Redgate Flyway has positively impacted my organization by enabling automated database migrations, so there are no manual updates to databases on each deployment to each environment."
 

Cons

"The single sign-on functionality being locked out for the enterprise plan is a significant downside, but it is something that can be worked around since LLM Gateway is an open-source project."
"If LLM Gateway could give us a facility or capability to create our own dashboards depending on our requirements, it would be helpful as an improvement."
"LLM Gateway is a strong platform, but there are a few areas where it could improve."
"A better interface and improved logs would enhance my experience with LLM Gateway."
"I see a few areas where LLM Gateway can be improved, including clearer cost guardrails and budget alerts that are more proactive, smoother project and workspace organization as the number of services grows, and more first-class support for prompt versioning and experiment tracking so that product teams can self-serve comparisons more easily."
"Regarding improvements, I think the pricing can be more competitive."
"Regarding the error mechanism, when we see a Redgate Flyway error in my Spring Boot application, it is very difficult to understand what went wrong."
"I cannot say that it is highly secure, but the features are good."
"Sometimes, errors with migrations can be very disappointing, as often it requires deleting everything and starting over."
"Particularly, the error handling mechanism or the force update or forced migration are things I would like to see improved; it is very hard to understand or debug exactly where this migration has failed, and I would not feel confident doing this in a production environment."
"Redgate Flyway works well for small teams but presents conflict issues with larger teams due to version control."
"I would not recommend Redgate Flyway for any Microsoft-based solutions or .NET, as it is not compatible at all based on my experience."
report
Use our free recommendation engine to learn which AWS Marketplace solutions are best for your needs.
915,341 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Construction Company
19%
Comms Service Provider
12%
Wholesaler/Distributor
7%
Financial Services Firm
7%
Construction Company
32%
Comms Service Provider
15%
Financial Services Firm
9%
Manufacturing Company
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business3
Midsize Enterprise3
Large Enterprise2
By reviewers
Company SizeCount
Small Business3
Large Enterprise4
 

Questions from the Community

What is your experience regarding pricing and costs for LLM Gateway?
My experience with pricing, setup costs, and licensing for LLM Gateway is that it is reasonable and predictable for us. The setup was light, mostly involving integration and configuration rather th...
What needs improvement with LLM Gateway?
LLM Gateway is an open-source and self-hosted solution, while OpenRouter is a SaaS solution. I think they overlap each other in some ways. OpenRouter allows you to bring your own API key, and LLM G...
What is your primary use case for LLM Gateway?
I am currently evaluating the implementation of LLM Gateway on our agency environment. I have extensive experience with LLM Gateway and Guardrails, and it has become my primary focus at work. We ar...
What is your experience regarding pricing and costs for Redgate Flyway?
My experience with pricing, setup cost, and licensing is that we have independent work with a separation of roles. We have those maintaining things concerning databases and a team that manages pric...
What needs improvement with Redgate Flyway?
I choose a rating of nine out of ten for Redgate Flyway because the only point is that sometimes it does not automatically handle the schema versioning. If we write something wrong, it just execute...
What is your primary use case for Redgate Flyway?
My main use case for Redgate Flyway is that it is a migration version control tool. I prefer Redgate Flyway because instead of manually running SQL scripts on different environments like dev, QA, a...
 

Overview

Find out what your peers are saying about LLM Gateway vs. Redgate Flyway and other solutions. Updated: September 2026.
915,341 professionals have used our research since 2012.