There is a fashion for hiding a simple publication behind five rented services. One paints the page, one holds the text, one sends the mail, one decides who may log in, and a sixth one charges you when the fifth one blinks. Sometimes that is justified. Often it is a way to avoid deciding.
Frontpage keeps the decision small. The pages are rendered on the server. The issues and stories live in a database file on the same host as the site. Letters and subscriptions are stored there too, and a copy is mailed to the studio. Editors sign in with Google, and only the accounts on the desk list get through. The public forms ask Google’s checkbox to turn away the obvious scripts.
That is not romantic. It is explainable. A future editor can open a story, change a sentence, and publish it without learning a new dialect. A future maintainer can find the letter someone sent last Tuesday. If the host is the same host as the rest of the studio’s sites, the deploy is the same gesture those sites already use.
Choose a larger stack when the work demands it. Do not choose it because a magazine feels like it ought to be complicated. Readers can tell the difference between complicated and cared for. They stay for the second one.