Search Oryxen

Search tools, jump to categories, and open key destinations

All alternatives

Recorded alternatives

Alternatives to db-migrator.go

Every candidate below sits in Developer Tools. What ends up on this page is decided entirely by a recorded score — not by bidding, not by editor taste. Review both records, check current vendor terms, then decide.

#1 Developer ToolsUnknown

grimoire — alternative #1 to db-migrator.go

Grimoire is a database access layer and validation for golang. (Support: MySQL, PostgreSQL and SQLite3).

GitHub source
Tool profile
#2 Developer ToolsUnknown

filess.io — alternative #2 to db-migrator.go

filess.io is a platform where you can create two databases with up to 10 MB per database of the following DBMS for free: MySQL, MariaDB, Mon...

Catalogue source
Tool profile
#3 Developer ToolsUnknown

godfish — alternative #3 to db-migrator.go

Database migration manager, works with native query language. Support for cassandra, mysql, postgres, sqlite3.

GitHub source
Tool profile
#4 Developer ToolsFree

libschema — alternative #4 to db-migrator.go

Define your migrations separately in each library. Migrations for open source libraries. MySQL & PostgreSQL.

GitHub source
Tool profile
#5 Developer ToolsUnknown

OtterTune — alternative #5 to db-migrator.go

OtterTune is a database tuning tool that optimizes performance and reduces costs for PostgreSQL and MySQL databases. [Free Trial]

Catalogue source
Tool profile
#6 Developer ToolsUnknown

skeema — alternative #6 to db-migrator.go

Pure-SQL schema management system for MySQL, with support for sharding and external online schema change tools.

GitHub source
Tool profile
#7 Developer ToolsUnknown

toasty — alternative #7 to db-migrator.go

[toasty] - A cozy, easy ORM for Rust supporting SQL (SQLite, PostgreSQL, MySQL) and DynamoDB with derive macros, type-safe queries, and data...

GitHub source
Tool profile
#8 Developer ToolsUnknown

XORM — alternative #8 to db-migrator.go

Simple and powerful ORM for Go. (Support: MySQL, MyMysql, PostgreSQL, Tidb, SQLite3, MsSql and Oracle).

Catalogue source
Tool profile

Questions about this page

How were these alternatives selected?

Each candidate is a live catalogue record in the same primary category, picked by a deterministic score that Oryxen records in its catalogue: how many meaningful words the two listings share, whether their pricing classes oppose (a paid product against a free one), whether both are open source, and whether either record is featured. The same catalogue state always produces the same list — no randomness, no manual ranking.

Are these alternatives ranked by payment?

No. Rows are ordered only by the recorded score, highest first, with alphabetical ties — payment never influences the order, nothing here is paid placement, and Oryxen charges no listing or placement fee.

Always verify current terms with db-migrator.go directly — Oryxen records pricing classes, not live quotes.