Atlas EULA limitations

[wandering-tales]

I have read the Atlas EULA document in the Atlas documentation, but I cannot understand whether I am free to use the tool within the license term with respect to the following scenario.

I would like to embed the non-community edition binary in a Docker image of a closed-source microservice I maintain at my company. The tool would be exclusively used to:

• apply migrations at container startup in any environment (e.g. local, CI, cloud)
• generate migrations on demand in a local development environment

Would any the above items match any of the prohibited use cases?

I suppose that for such simple usage scenario I may also use the community version, but this inquiry of mine is just to clarify things.

[a8m]

Hey @wandering-tales,

In principle, the Atlas EULA allows using the Atlas binary in internal services. The typical use case, where you use Atlas to run migrations and manage databases owned by your own company is covered.

However, products that provide functionality powered by Atlas to their clients, such as managed migrations or schema management (inspection, diffing, etc), require a license for this, as they are essentially reselling Atlas.

Please note that this isn't legal advice. If you are still unsure whether your case is covered, please consult our team at hello at ariga.io