We have a technical stance, and we are not going to hide it behind the phrase "we will do whatever you ask."

There are tasks that we know how to perform, but deliberately do not offer, because we consider them a bad solution for the long-term life of the project.

• Why we don't develop new sites on MODX — if a project starts from scratch, it makes no sense to build legacy and future dependence on a narrow ecosystem into it yourself.
• Why we don't rewrite a MODX site completely from scratch — a running business does not have to risk everything on one big release if the system can be migrated gradually and with rollback capabilities.

These are not limitations of our competence. On the contrary: we know MODX well enough to understand where it is still reasonable to support it, and where it is better not to create a new problem for ourselves.

This section establishes the boundaries of our technical policy — what we fundamentally do not sell and why.