This is a separate standalone application, not a microservice of Ridid: a Vue 3 SPA front end and a FastAPI backend, each with its own repo, CI/CD pipeline, VM and domain, plus its own database (admins, audit log, invoices, pricing, referrals, OTAs). It integrates with the Ridid PMS mainly at the database level, which is precisely the coupling microservices are defined against, so I contained it deliberately: a second connection into Ridid's MySQL under a least-privilege user, SELECT on a handful of tables and UPDATE limited to two columns (the client's fee and subscription end date). Sharing the database over building a full event pipeline was a documented trade-off for a small team, and the least-privilege grant is what bounds the risk, an admin-side bug or compromise cannot corrupt live customer data. The one clean service boundary is impersonation: the panel issues a one-time code, but the redemption endpoint lives in Ridid's own backend, over a signed handoff.