NetSendo for agencies: one licence and instance per client

An agency can run email and SMS marketing for its clients on NetSendo, but not from one shared installation. Under the NetSendo EULA, each client is the licensee of its own instance, running in an environment the client controls, and the agency works on it as a contractor acting on the client's behalf.

Can an agency use one NetSendo installation for many clients?

Not without written permission from NetSendo. A single installation that the agency operates and into which several clients log in, or on which the agency runs campaigns for several businesses, is a hosted or managed service for third parties.

The EULA excludes this from the standard licence in several places:

• §3.5 — unless NetSendo authorises it in writing, the licence does not allow offering the software as a hosted or managed service, or giving third parties access for their independent use. Use is limited to the customer's own internal business operations.
• §6.3 c — duplicating environments to give third parties access is not permitted.
• §7.1 — no SaaS, hosting or managed services, and no operating the software primarily for the benefit of third parties.

So "one server, ten client accounts" is not a configuration choice you can make on your own, even though it is technically possible to create many lists in one installation.

Which agency model does the EULA allow?

The client is the licensee, the instance runs in an environment the client controls, and the agency works on it as the client's contractor. The EULA allows access by "employees or contractors acting on the Customer's behalf and under the Customer's control" (§4.3 c) and lists contractors and service providers among authorised users (§6.2 c).

Based on the NetSendo EULA as published on netsendo.com in October 2026. The EULA text prevails over this summary; this is not legal advice.

How do you set up NetSendo for a new client?

Give every client its own server and its own licence, set up in the client's name, and keep your agency's access as a named user account on that instance.

1. The client owns the environment

   The server or cloud account is in the client's name and on the client's billing, so the environment is "controlled by the Customer" as §6.3 a requires. You can do the work with delegated access.

2. Install NetSendo with Docker

   Follow the quick start: clone the repository, create .env and start the stack.

   git clone https://github.com/NetSendo/NetSendo.git
   cd NetSendo
   cp .env.example .env   # set a strong DB_PASSWORD
   docker compose up -d

3. The client activates the licence

   On the licence page the client chooses SILVER and activates it with an email address from its own company, so the licence is clearly the client's. See plans for what SILVER includes.

4. Connect the client's sending provider and domain

   SMTP or API sending (for example Amazon SES or Mailgun) runs on the client's account, and SPF, DKIM and DMARC are set on the client's domain. The deliverability guide for self-hosted senders walks through the records.

5. Create your agency user and document access

   Work through a personal user account rather than the client's administrator login, and write down who has access to the server, the provider account and the DNS.

6. Plan the handover

   Because everything is in the client's name, ending the engagement means removing your users and keys. The data, the domain reputation and the licence stay with the client.

What does it cost per client?

The SILVER licence is free for running NetSendo for the client's own business; the client pays for the server and the sending provider, and you bill your work as a service.

Infrastructure costs depend on list size and sending volume. For a worked comparison of SaaS prices and self-hosted costs at 10k, 50k and 100k contacts, see what it really costs to email 10k, 50k and 100k contacts. The GOLD plan is listed on the pricing page, but it cannot be purchased yet.

Can you white-label NetSendo for clients?

No. The EULA grants no white-label, rebranding or private-label rights (§3.6), and you may not present NetSendo as your own product or offer it under another name (§7.3).

What you can brand is your own work: the campaigns, templates, sign-up forms, landing pages and reports you produce for the client.

Why is one instance per client a good idea anyway?

Separate instances keep each client's data, sending reputation and access apart, which is what most clients and their data protection officers expect.

• Data separation: subscriber data lives on infrastructure the client controls, which makes the client's own GDPR documentation simpler. Compliance still depends on how the instance is run.
• Reputation separation: each client sends from its own domain and provider account, so one client's complaint rate does not affect another.
• Clean offboarding: there is nothing to export or untangle when a client leaves.
• Clear responsibility: the licensee, the data controller and the account owner are the same company.

The trade-off is operational: you maintain several installations, including updates and backups for each. Scripting the install and update steps keeps this manageable.

What if you need a multi-client setup?

Ask NetSendo for written permission before you build it. Use outside the scope of the EULA "requires prior written consent from NetSendo and may be subject to additional fees or separate contractual terms".

Describe the setup you have in mind (how many clients, who hosts, who logs in) and write to contact@netsendo.com. Until you have that consent in writing, use the one-instance-per-client model.

Frequently asked questions

Sources

• NetSendo End User License Agreement (EULA)
• NetSendo plans and pricing
• NetSendo repository on GitHub