WordPress suite
What you install on every client site
Modules that do the work no client should have to do: consent to cookies for real, tidy the dashboard, keep track of what changed. Each one installs on its own. Each one has a free version that is enough for a site
What WordPress offers
Files and search
Editing comfort
Safeguards
Licence active Until 12 March 2027
The suite
One panel, modules you switch on one by one
Twelve modules today. Each will have its page, its documentation and its own release pace
A suite, not twelve plugins
What changes when it is all held in one place
Twelve different jobs, twelve plugins to do them. The work itself does not change — it is everything around it that costs: the licences to keep track of, the updates that do not talk to each other, the settings scattered across twelve menus, and a client who has to learn twelve interfaces to run a single site
Multiple plugins
- Licences
- Twelve renewals, twelve accounts, twelve invoices
- Settings
- Every plugin puts its menu wherever it likes
- Updates
- Twelve to follow, and nothing that guarantees they get along
- Code loaded
- Whatever the author decided, used or not
- The client
- Twelve ways of writing, twelve ways of naming the same thing
- When it breaks
- Twelve people to talk to, twelve response times
nexya
- Licences
- One licence, one date, one invoice
- Settings
- One panel, with the modules inside it
- Updates
- One, tested with the others before it ships
- Code loaded
- None at all while the module is off
- The client
- One vocabulary, written for them
- When it breaks
- One address
In numbers
What the gap costs, once spread over a year
Les deux colonnes ci-dessus disent la nature du problème. Les deux mesures qui suivent en donnent l’ordre de grandeur, sur des hypothèses volontairement basses — elles sont détaillées sous les graphiques.
1 licence
to renew, instead of twelve
1 plugin
to follow at every update
0 lines of code
loaded by a module that is off
- 12 h 5 sites
- 24 h 10 sites
- 48 h 20 sites
- 72 h 30 sites
- 120 h 50 sites
Le travail que font les modules ne change pas. Ce qui change, c’est le nombre de fois qu’il faut y revenir : une extension à vérifier au lieu de sept, à chaque cycle, sur chaque site.
Le gain ne se voit pas sur un site. Il se voit sur un parc, et il grandit avec lui.
Sur un site neuf, chaque extension demande son installation, sa clé, ses réglages, et l’accord avec les autres. Un panneau unique remplace ces gestes par un seul : allumer ce dont le site a besoin.
C’est le seul chiffre de cette page qui se mesure au chronomètre plutôt qu’à l’année.
Estimates, assumptions included: 2 minutes of checking per plugin and 6 minutes of setup, for 7 plugins instead of one. Licence renewals are not counted.
Free and Pro
The free version does real work
A free module that is useless is not free, it is a demo
Every module has a free version that is enough to run a site: the banner consents and blocks, the log records, the 404s are tracked. Nothing is crippled to the point of being unusable.
Pro adds what you need when you run twenty sites rather than one: replay an action, import three hundred redirects, scan a whole site. It is the same plugin — you unlock, you do not reinstall
Where it comes from
Written in an agency, for its own sites
nexya did not come out of a market study. These are the modules an agency installed on every site it delivered, written because the existing plugins did too much, or not enough, or asked the client to understand WordPress.
They ran in production for years before being sold
The stance fits in one sentence: a client should never have to know what a role, an HTTP header or a 301 redirect is for their site to be right.
Anything the agency can decide once, it decides. What is left is written in the client’s language, not the code’s
Soon
The first modules arrive this autumn
The free versions will ship on wordpress.org, the pro licences through Freemius. Write to us to be told, or to say what you are missing
Write to nexya