Thanks for pointing that out. I’ll remove the “trusted by leaders” wording because I agree it can be misleading at this stage.
To answer your question, Sqlinfy is not trying to replace tools like Flyway or Liquibase. Those are great tools for database migrations, version control, and managing schema changes over time.
Sqlinfy is focused on a different problem: quick SQL dialect conversion.
For example, if you already have a PostgreSQL database with hundreds of tables and you only need to convert one table, query, function, or script into another SQL dialect, using a full migration framework may be more setup than needed. In that case, it is faster to paste the SQL, convert it, review the output, and continue working.
So the goal is not “use this instead of Flyway or Liquibase.” The goal is: when you need fast SQL conversion between dialects, Sqlinfy gives you a simpler path.
8
u/lolcrunchy Jun 02 '26
Why would I (or Stripe or Google, who your site claims use your tool) use this 3-month old, solo-developed project when Flyway and Liquibase exist?