Terms of service

What the service does

module.monster turns a description of what your shop should do into a PrestaShop module. You scope it in a conversation with an agent; when you approve the spec, the module is written, tested on a live PrestaShop installation, translated, documented and packaged as a zip. That is the whole of it. You install the zip yourself, in your own time: nobody here is given access to your shop, and nothing is done to your shop on your behalf.

The service is run by the operator of this site, reachable at [email protected]. Creating an account, or using the service at all, means you accept what is on this page. If you do not accept it, do not create one.

Your account

You need an account to have anything built. What is expected of it:

• One account belongs to one person. Do not share your sign-in — anyone holding it can spend your build credits, read your conversations and download your modules.
• Use an email address you control. It identifies the account and it is the address support answers, so a request about the account is only acted on when it comes from that address.
• Choose a password you do not use anywhere else and keep it to yourself. It is stored only as a bcrypt hash, so nobody here can read it back to you — and the portal has no password reset today, so a lost password is a support matter rather than a link you can request.
• An account created with the Google button has no password at all. Keep signing in with Google for it: there is no way in the portal to add a password to that account afterwards.
• What happens through your account is your responsibility — the descriptions submitted, the images uploaded and the credits spent.

Build credits

A build credit is the unit of work here. Credits are granted on request, not given automatically at signup. Exactly what spends one:

• Talking to the agent is free. Describing an idea, changing your mind, rewriting it from scratch or walking away costs nothing, however long the conversation runs.
• Approving the spec spends exactly one credit. It is taken the instant you approve, before anything reaches the build pipeline, so two approvals arriving together can never spend the same last credit twice.
• If that handover then fails — the agent is still finishing a reply, the spec cannot be written up, or the release itself errors — the credit goes straight back onto your balance in the same request, and nothing has been built.
• Once the module has reached the build pipeline the credit is spent. If the build later fails, or is flagged as needing attention, the software does not put the credit back by itself; write to [email protected] and a person looks at it.
• Every approval spends one, whether it is your second module or a changed version of one you already have.
• At zero, approving is refused and nothing is built. Brainstorming still works.

Your balance is on your account page, and the portal tells you what is left the moment an approval goes through.

Credits are not money. The portal has no payment page, never asks for a card and stores none — credits are granted to an account, which is why this page quotes no price for them. Nothing in the software expires a credit either: a balance sits on the account until it is spent.

What you get

When a build finishes, the module's page offers a zip: an ordinary, versioned PrestaShop module you install yourself from your own back office. Inside it is readable PHP, the translations you asked for, an illustrated guide for each of those languages, and the licence text. The module does not call home and does not need module.monster to keep working.

The zip exists only once the build has finished; until then the module's page shows where it has got to. Builds do fail — a step that keeps coming back wrong is retried, and then the module is flagged for attention rather than shipping something broken. These terms set no delivery time and no availability commitment, because the software makes neither.

What is built is the spec you approved. The conversation beforehand is where the shape of the module is settled, so read it before you approve: approving is what releases it, and the conversation closes at that point.

Who owns the module

The zip is yours — to use, to change, to install on as many of your own shops as you like, and to hand to your own developer. The precise position is whatever the packaging step writes into the files, and this is what it writes:

The copyright line in the header names the author configured for this factory rather than your shop. It is the licence grant sitting beside it in the same header that gives you your rights over the code. If this page and a delivered package ever disagree, the file you were given is what governs it.

Two things are deliberately not claimed here. Nothing stops you reselling or redistributing the module — the commercial licence permits that. And nothing promises a module built for you is unique: two similar briefs can produce two similar modules, and neither of you is owed exclusivity.

What you may not ask for

The agents build what they are asked to build, so these limits are yours to respect:

• Ask only for modules that are lawful where you and your shop are, and that you have the right to have built. Nothing whose purpose is to defraud, to spam, to break into another system, or to handle other people's data in a way they have not agreed to.
• Upload only images you have the right to upload. A reference screenshot is stored on the server and passed to the agent, so do not attach anything that is somebody else's confidential material.
• Stay inside the limits the portal sets: an idea is up to 2000 characters and an attached image up to 5 MB. Sign-in and sign-up are rate limited — do not work around that, and do not drive the portal or the chat with a script.
• Your modules and conversations are scoped to your account. Do not attempt to reach anyone else's, or to sign in as anyone but yourself.
• Do not attack the service, the container it builds and tests in, or the shops it tests on — and do not use a build as a way to get code onto that infrastructure for any purpose other than the module you asked for.
• Use the conversation for scoping a module. It is there to design PrestaShop modules, and that is what it will answer about.

Beta, and provided as it is

module.monster is in beta, and the badge beside the name says so on every page. Features change, steps are added and removed, and something that behaved one way last week may behave differently this week. The service is provided as it is, with no warranty of any kind: not that a build will succeed, not that a module suits your particular shop, and not that the service is available when you want it.

The code is written by AI agents and tested by them on a real PrestaShop installation, which catches a great deal and cannot catch everything. Treat what you are given the way you would treat any third-party module: read it, install it on a test shop first, take a backup, and satisfy yourself it does what you need before it goes anywhere near a live shop and real orders. You are the one installing it, so you are the one answerable for what it does there.

So far as the law where you are allows it, the operator is not liable for loss arising from using the service or a module built by it. Where that law gives you rights that cannot be signed away — and in several of the countries this service is offered in, it does — those rights stand, and nothing on this page cuts them down.

Suspension, and stopping

An account carries an active flag. If it is cleared — for a breach of the section above, or because the account is being used to harm the service or somebody else — sign-in is refused from that moment, and a session already open ends the next time it makes a request. That on its own deletes nothing.

You can stop using the service whenever you like: there is nothing to cancel and no notice to give. Delete account, on the account page, closes it for good — it is refused while a build is still running, so let that finish first. Writing to [email protected] does the same by hand, and the privacy notice sets out what is kept afterwards.

Suspension does not reach into what has already been built. A module delivered to you carries its licence inside the files, and closing or suspending an account does not take that back.

Changes to these terms

This page is part of the software and changes when the software changes — that is the point of writing it from the code rather than from a template. Last updated 15 August 2026.

There is no change notice to subscribe to: the portal has no way to send you email, so the date above is the record. Using the service after a change means the version on this page is the one that applies. If a change is one you cannot live with, stop using the service and write to [email protected] about your account.