Production routing
The site needs a MayaUPS address or form endpoint before production launch.
CONTACT
Contact the MayaUPS team.
Use this page for download support, security or accessibility routing, and public-sector review questions. The production contact endpoint is still required before the form can accept a message.
[[TODO: publish a MayaUPS contact address or production form endpoint]]
Download and site-key support
The download flow is designed around verified email, a one-time code, and a site key used for battery-replacement alerts. Until the live backend and installer URLs are supplied, the public form can demonstrate the API contract but must not pretend to unlock a production binary.
Procurement and conformity questions
Reviewers can use this channel for questions about EN-CA / FR-CA language support, WCAG 2.1 AA and SGQRI 008 alignment, Quebec Law 25 placeholders, local data residency, security.txt, the CycloneDX SBOM, and the public Cloudflare / mayaups.com deployment posture.
Operational fit discussions
MayaUPS is relevant when a site needs multi-vendor network or direct-attach monitoring, RFC-1628 decoding, battery service-life forecasting, grouped email or webhook alerts, CSV onboarding, maintenance planning, and safety-gated shutdown. It is not a hosted SaaS offer.
Before launch
The production contact path should confirm the receiving address, spam protection, consent handling, notification routing, and privacy linkage before mayaups.com is treated as a live support channel.