Migration from Peacae PM

Peacae PM is now Mayvor. The product has a new name and identity, while its mission continues to evolve around helping builders turn visions into reality.

Mayvor is a coined name inspired by Make Your Vision Real, pronounced MAY-vah (IPA: /ˈmeɪ.və/). The public website is mayvor.com. Wekify LLC remains the publisher.

Existing projects remain compatible

The brand change does not require renaming .peacae/, task identities, agent contract files, database tables, or PEACAE_* environment variables. These identifiers remain in place for compatibility.

1. Keep the existing project board and agent instructions in their established locations.
2. Continue using the current Desktop watcher and Cloud project link.
3. Update visible product wording in your own documentation when convenient.
4. Check sign-in and sync with your configured service before changing deployment or callback URLs.

Do not replace API hosts, desktop update feeds, authentication callbacks, or repository URLs merely because they contain the former name. Those changes require coordinated service configuration.

Website and deployment

Public metadata uses https://mayvor.com by default. Deployments can set MAYVOR_SITE_URL to their preferred public origin. Authentication and invitations continue to use the existing application URL configuration.

Redirecting the former pm.peacae.com hostname requires control of its hosting configuration and DNS. Preserve paths and query strings for public routes when setting permanent redirects; keep operational routes working until their clients and authentication configuration have been migrated.

See project setup, local-first architecture, and Cloud and sync.