Migration Guide: MLange → Melange

What changed in the rebrand from MLange to Melange, and what you need to update.

ZETIC has rebranded MLange to Melange. This is a branding-only change: there are no code changes, API modifications, or breaking changes required on your end.

What Changed

The product name has been updated across all documentation, marketing materials, and the web dashboard. The underlying SDK, API surface, package names, and class names remain exactly the same.

Area	Before	After
Product name	MLange	Melange
Documentation references	"ZETIC MLange"	"ZETIC Melange"
Dashboard URL	`mlange.zetic.ai`	`melange.zetic.ai`

What Stayed the Same

Area	Value
Android package	`com.zeticai.mlange`
iOS package	`ZeticMLange`
Android class names	`ZeticMLangeModel`, `ZeticMLangeLLMModel`
iOS class names	`ZeticMLangeModel`, `ZeticMLangeLLMModel`
Gradle dependency	`com.zeticai.mlange:mlange:+`
SPM repository	`github.com/zetic-ai/ZeticMLangeiOS`

Do I Need to Change My Code?

No. All SDK package names, class names, method signatures, and dependency coordinates remain identical. Your existing code will continue to work without any modifications.

The class names retain the original MLange spelling (e.g., ZeticMLangeModel) for backward compatibility. This is intentional and will not change.

What You Might Want to Update

While no code changes are required, you may want to update references in your own documentation or comments:

Internal docs or READMEs that reference "MLange" can be updated to "Melange" for consistency.
User-facing strings in your app (e.g., "Powered by ZETIC MLange") can be updated to "Powered by ZETIC Melange."

If you encounter any documentation that still references the old "MLange" branding, the technical content remains accurate: only the product name has changed.

Summary

This rebrand is cosmetic only. No action is required from developers. All existing integrations, API keys, dashboard URLs, and SDK dependencies continue to work without modification.