1. The service
migready analyzes supported migration changes and publishes checks on GitHub. SQL migrations are analyzed directly, while supported framework extraction runs in your GitHub Actions environment. The service identifies supported risks; a passing check does not guarantee safe deployment, availability, or data integrity. Review findings alongside testing, backups, production conditions, and deployment plans.
2. Your account and repositories
Use a GitHub account you are authorized to use, and install the app only on repositories you are authorized to connect. Workspace owners control coverage, billing access, notification settings, and retention. Protect your account and review changes to extraction workflows and dependencies. Do not give extraction jobs production credentials.
3. Plans, trials, and usage
The free trial covers one enabled repository and 50 analysis attempts for 14 days. Its clock begins after the first completed analysis containing migrations. Starter is USD 29 per month for 10 enabled repositories and 500 analyses; Growth is USD 69 per month for 20 enabled repositories and 2,000 analyses. Enterprise pricing and limits are agreed separately. These are shared workspace allowances, not allowances per repository.
An attempt counts when analysis starts. Waiting for extraction and changes without matching migrations do not count. Delivery retries and automatic recovery do not count the same attempt twice. A manually requested rerun is a new attempt. Engine crashes automatically credit the affected attempt. Contact support for other service failures that consumed allowance without a usable result. Limits pause further analysis; the service does not automatically charge overages.
4. Billing and cancellation
Paid subscriptions, when enabled, renew monthly through Stripe at the price shown in Checkout. The current beta does not accept live payments. Any sandbox checkout is labeled and creates no real charge. Applicable taxes and any proration are shown before confirmation. You can manage payment details and cancel through the billing portal. A scheduled cancellation normally preserves access until its displayed end date. Downgrading may require disabling repositories that exceed the new allowance. Unpaid subscriptions may lose analysis access.
Refund requests and billing corrections are reviewed through support. These draft terms do not limit mandatory consumer rights. Final refund, tax, and jurisdiction provisions will be published before paid launch.
5. Acceptable use and ownership
You retain ownership of your code and migration data. You permit the processing needed to provide checks, maintain your account, and deliver service notifications. Do not use the service to attack systems, bypass access controls or limits, or process content you are not authorized to share. We may restrict abusive usage or suspend access to protect the service and other customers.
6. Retention and third parties
Our privacy policy describes zero retention, optional report history, and the records retained by GitHub, Stripe, Resend, and our hosting provider. Zero retention applies to analysis data held by this service; it does not remove results from GitHub. Availability depends in part on those providers.
7. Availability and changes
The beta has no contractual uptime guarantee. We may maintain or update the service and its supported rules. Material changes to pricing or policies will be communicated before they take effect. Review critical migrations independently. Enterprise support or availability commitments apply only when separately agreed.
8. Contact
For support, account closure, or questions about these terms, contact the migready operator on GitHub. The operator's registered identity and governing-law details remain pending for this beta draft.