Skip to content
All articles

Under the hood: the engineering behind Pagick

November 7, 2026 · 2 min read

Under the hood: the engineering behind Pagick

What you do not see

A site that works is mostly a site where nothing strange happens. That calm is built in choices the user never sees: how the code is organised, how data is separated, how an update is deployed. Here are a few of those choices.

Every site is kept apart

Pagick hosts many sites on the same platform, and none must be able to see or touch another’s data. Data, files, caches and background jobs all carry the identity of the site they belong to. And when that identity is missing, the system refuses to act rather than guess.

Limits are checked where they matter

Hiding a button is not enough to enforce a plan: you would only need to be curious. Limits (number of accounts, forms, languages, available modules) are checked on the server, at the time of the action, with a clear answer saying which limit was reached and what would lift it.

Downgrading destroys nothing

If you move to a lower plan, your content is neither deleted nor hidden. You can still read it, edit it and delete it; you are only prevented from creating more beyond the limit. Your data is never used as leverage.

Credits that are not lost

An example of care in the detail: assisted-translation credits are reserved before the model is called, then given back if the call fails. You do not pay for a translation that never arrived, and nobody can exceed their quota by firing a thousand requests at once.

A deployment that can roll back

Each new version is first started next to the old one and tested, then switched over without downtime; if something is wrong, going back to the previous version is automatic. The code is organised in layers with rules enforced by tools, and backed by automated tests that run on every change.

A concrete example

You reach your plan’s language limit and try to add one more. Pagick does not crash and loses nothing: it refuses cleanly, tells you which limit was reached and which plan would allow it. Your existing content stays intact, editable and published.

Key takeaways

Sites kept apart, server-side checks, downgrades without loss, credits returned on failure, deployment with automatic rollback, layered code and automated tests: this quiet work is what lets Pagick stay reliable.

A project in mind?

A question? Let's talk.