migrax.org valid

Migrax

Migrax generates SQL migrations from JPA/Hibernate entities and applies them, with locking, checksums, rollback scripts, linting and verification. It runs as a command line tool, a Maven or Gradle plugin, a container image, and at startup in Spring Boot, Quarkus, Micronaut and Helidon, on PostgreSQL, CockroachDB, MySQL, MariaDB, SQL Server, Oracle, H2 and SQLite.

For agents: Java CLI and Maven/Gradle plugin that generates and applies SQL migrations from JPA/Hibernate entities across many databases, with rollback scripts and linting.

sql-migrationsjpahibernateflyway-alternativeschema-migrationjava

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-26T12:49:35.185Z. Cached copy · Source on migrax.org

# Migrax

> Migrax generates SQL migrations from JPA/Hibernate entities and applies them, with locking, checksums, rollback scripts, linting and verification. It runs as a command line tool, a Maven or Gradle plugin, a container image, and at startup in Spring Boot, Quarkus, Micronaut and Helidon, on PostgreSQL, CockroachDB, MySQL, MariaDB, SQL Server, Oracle, H2 and SQLite.

Full text of every page: https://migrax.org/llms-full.txt

## Overview
- [Home](https://migrax.org/): What Migrax is, a short example, and how to get started.
- [Download](https://migrax.org/download/): Migrax needs Java 17 or newer. Download the command line tool below, then run its installer as described in Installation.

## Getting started
- [Installation](https://migrax.org/getting-started/installation/): Migrax is a command line tool. It needs Java 17 or newer; nothing else has to be installed, and no administrator rights are needed.
- [Quick start](https://migrax.org/getting-started/quickstart/): This takes about five minutes. You need a service with JPA entities, a `pom.xml` or `build.gradle`, and a database it can reach.

## Guides: Everyday use
- [How Migrax works](https://migrax.org/guides/how-it-works/): Entities are read into a schema model, compared with the snapshot, and the difference becomes a migration file with a rollback script; migrax migrate applies it to the database and records it in migrax_history.
- [Changing entities](https://migrax.org/guides/changing-entities/): The everyday loop is short:
- [Rollbacks and recovery](https://migrax.org/guides/rollbacks-and-recovery/): Every generated migration has a rollback script in `rollback/<same name>.sql`.
- [Advanced migrations](https://migrax.org/guides/advanced-migrations/): Some data changes are easier in Java than in SQL.

## Guides: Teams and CI
- [Working in a team](https://migrax.org/guides/team-workflow/): The snapshot is written with one table, column, index and key per line, so git can merge changes two people made to different tables.
- [Continuous integration](https://migrax.org/guides/ci/): Three commands make a good CI gate:
- [Comparing databases](https://migrax.org/guides/comparing-databases/): New in Migrax 0.14.0.
- [Java API and JUnit tests](https://migrax.org/guides/java-api-and-tests/): New in Migrax 0.10.0.

## Guides: Production
- [Production safety](https://migrax.org/guides/production-safety/): Migrax is built around one idea: a migration should be proven before it runs in production.
- [Zero-downtime changes](https://migrax.org/guides/zero-downtime/): New in Migrax 0.11.0.
- [Metrics and tracing](https://migrax.org/guides/observability/): New in Migrax 0.13.0.
- [Containers and Kubernetes](https://migrax.org/guides/containers-and-kubernetes/): In container platforms, migrations usually run as their own step before the new version of the application starts: a Kubernetes Job, an init container, or a deploy hook.

## Guides: Other setups
- [Several databases](https://migrax.org/guides/
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=migrax.org · GET /v1/domain/migrax.org · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for migrax.org:
1. POST https://agentwebmap.com/v1/sites/migrax.org/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://migrax.org/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/migrax.org/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/migrax.org).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.