Professional installation

We install. We configure. We hand you a working email stack.

One-time engagements: PowerMTA, MailWizz, Acelle Mail, Interspire and full production stacks. Fixed price, scoped up front, documented at handover. Bring your own server or use one of ours.

Fixed price
30-day post-install support
Works on any provider
Documented handover
Crypto accepted

Request a quote See managed hosting instead Chat on WhatsApp

What we install

Email infrastructure, installed properly the first time.

Most people do not actually want a server administrator on staff. They want a working email infrastructure that they can send from. The gap between "I bought a VPS" and "I am sending a million emails a day with good inbox placement" is where this service lives.

We install, configure, tune and document. You operate, send and grow. If something breaks in the first 30 days that relates to what we installed, we fix it. After that, you either manage it yourself with the runbook we leave behind, or you upgrade to a management contract with us.

PowerMTA 6.0 install

Full install: global config, VMTAs per IP, per-ISP throttling, DKIM/SPF, bounce server, FBL consumer. From € 149 one-time.

MailWizz install

Core + PowerMTA integration + DNS + tracking domain + SaaS if needed. From € 199 one-time.

Acelle Mail install

Laravel, Nginx, MySQL, Redis, Supervisor, SaaS mode, PowerMTA wiring. From € 199 one-time.

Interspire install (any version)

Including legacy 6.1.x on modern PHP via compatibility layer. From € 249 one-time.

Mail server stack

Postfix + Dovecot + SpamAssassin + ClamAV + DKIM-Milter + OpenDMARC. From € 299 one-time.

Monitoring + observability

Grafana + Prometheus + Loki + Alertmanager. From € 199 one-time.

How it works

Discovery call: 30 minutes, no commitment. You tell us the goal, the server provider and the time constraint. We tell you whether we can help, how long it will take and what it will cost. If it is not a fit we say so and point you to whoever is a fit — we do not sell engagements we cannot deliver well.

Access and scheduling: you give us root SSH access (a dedicated user with sudo works too) and we book the installation into our queue. Simple installs can start within 24 hours; complex stacks are scheduled 3 to 7 days out.

Installation window: we announce the start time, work through the scoped items, and send you updates at every major milestone. You do not need to be on the line with us — but we respond to questions fast.

Handover: written runbook with everything we changed, credentials documented (and rotated by you immediately after if you prefer), first-week operational notes and the list of what to watch. Plus 30 days of post-install support for anything in scope.

What we will not do

Install pirated software. If you need a licence, we will help you buy it, but we will not install a cracked copy.
Configure a server to send spam. We ask what you plan to send during discovery and decline engagements that do not sit within our AUP.
Take an engagement without scope. Fixed price means we need to know what we are building; "install email stuff" is not a scope we can quote.

2026 reality

Three forces reshaped the email infrastructure installation market between 2024 and 2026.

The market for "install PowerMTA / MailWizz / Acelle on my server" looks superficially similar to what it was in 2020, but three concrete shifts changed the operational picture meaningfully. Operators evaluating installation services in 2026 should understand what changed before signing a $25 Fiverr engagement that becomes a $2,500 cleanup engagement six weeks later.

First, the gap between cheap freelance installs and professional installs widened structurally. The $5-25 Fiverr installs use shared installer scripts that handle the happy-path PowerMTA + MailWizz install in 20 minutes — but skip Feedback Loop registration with major ISPs, skip per-tenant queue worker monitoring, skip MTA-STS records, skip rate-limit tuning per ISP, and skip the operational handover that lets your team actually maintain what was installed. About 40% of our installation engagements in 2025-2026 are clients who first paid a freelancer, watched their deliverability collapse within 30-60 days, and came to us to fix it. The cleanup engagement typically costs 8-15× the original Fiverr install.

Second, CentOS 7 EOL (June 2024) and the broader RHEL ecosystem shift forced OS migrations across thousands of email infrastructure deployments. Operators running PowerMTA on CentOS 7 had to migrate to AlmaLinux 8/9, Rocky Linux 8/9, RHEL 9, or Debian/Ubuntu before security patches stopped flowing. The migration is non-trivial — PowerMTA RPMs need updating, supervisor configurations may need adjustment, dependencies like MySQL/MariaDB versions change. Installation services in 2026 should default to AlmaLinux 8/9 for RHEL-family targets; CentOS 7 deployments are now legacy migrations rather than greenfield installations. Operators who postponed the migration are running unpatched systems that are progressively harder to support as upstream package availability degrades.

Third, the rise of self-hosted MTA alternatives (KumoMTA, Haraka) created new installation patterns that traditional PowerMTA installers do not know how to handle. KumoMTA's Lua-based configuration, Rust runtime requirements, Kubernetes-native deployment patterns, and Prometheus + Grafana observability stack are different from PowerMTA's accounting-log + SparkPost-Signals model. Installation services that only know "PowerMTA + MailWizz" have a shrinking addressable market as more operators evaluate the modern alternatives. Our installation team has handled both stacks since KumoMTA's open-source release; the operational patterns we use for monitoring, deployment, and handover work for both equally.

The takeaway: in 2026 the installation services market has bifurcated. The bottom (cheap Fiverr) handles the happy-path install for operators who do not yet understand what they actually need; the top (us, SmtpHero, similar specialists) handles the production-grade install with operational handover for operators who do. The middle is collapsing. Operators should evaluate which segment their actual needs sit in, then pick accordingly.

Decision framework

Five-question decision tree — should you commission a professional install?

The tree below walks the same logic we use during discovery calls. Five binary questions, four terminal recommendations including an honest "DIY install" branch when paying for installation services would be premature for your scale, and a "managed hosting instead" branch when self-deployment is the wrong primary path entirely.

Two sub-points worth noting. First: the "DIY install" branch is honest output — if you have an in-house Linux engineer who knows PowerMTA, you do not need to pay us for installation. Use the one-click installers from Acelle/MailWizz, follow the docs, save the money. We are not insulted; we are not in the business of selling installs to teams that do not need them. Second: the "managed hosting instead" branch is the right answer for the largest segment of operators who think they want installation services. Most operators evaluating "should I install this myself or pay someone to install it?" are actually asking the wrong question — the right question is "should I run this myself at all?". Managed hosting handles the install, the maintenance, the upgrades, the security patches, the monitoring, all as one bundled service. For most operators that is better economics than install plus self-maintain.

What we actually install — the production stack walkthrough.

The diagram below shows the full stack we deploy for a typical PowerMTA + MailWizz combined installation engagement. Each box represents a specific component we install, configure, document, and verify before handover. The diagram exists because clients frequently ask "what am I actually getting for €349?" — the honest answer is the stack below, plus 30 days of support, plus a runbook your team can use.

Three observations from the installation stack. First: OS hardening is not an upsell, it is part of the install. Cheap freelance installs frequently skip SSH key-only configuration, firewall setup, and unattended security patches — the operator inherits a server that runs but is exposed to attack. Our installs include OS hardening as part of base scope because the server has to be production-grade, not just functional. Second: the FBL catcher and DKIM signing setup are the most commonly missed components in cheap installs. Without FBL registration with major ISPs (Yahoo, AOL, Comcast, etc.), 60-80% of complaint signals never reach your platform; without proper DKIM, your email reputation is structurally weaker. Both are non-optional in our installations. Third: the documentation handover is what separates an install from a finished engagement. The runbook documents every credential, every config file location, every operational procedure, every known issue, and the watch-list of metrics your team should monitor. Without the runbook, your team is operating a black box; with the runbook, your team is operating a system they understand.

Pricing comparison — what installation actually costs across the market.

The table below normalizes pricing across the realistic installation services market in 2026. Numbers reflect current published pricing (Fiverr, SEOClerks freelancers) plus Blue Spirit's own service tiers. The "what's included" column matters more than the headline price — most pricing differences correlate with what is actually being delivered, not with arbitrary markup.

Provider tier	Price range	What's included	Post-install support	Documentation
Bottom freelance (Fiverr/SEOClerks)	$5-$25	Happy-path install only. No FBL, no monitoring, no hardening.	3-7 days bug fixes	None
Mid freelance (experienced)	$100-$300	Install + basic DNS + bounce handler. May skip hardening.	7-14 days	Basic notes
Specialist consultant (SmtpHero etc)	$300-$800	Full install + DNS + FBL + monitoring. Production-grade.	14-30 days	Documented
Blue Spirit one-time install	€149-€499	Full install + DNS + FBL + monitoring + OS hardening + runbook.	30 days	Comprehensive runbook
Enterprise consultancy	$2,500-$10,000+	Full install + custom architecture + extended consulting.	90+ days	Architecture docs

Three observations from the pricing comparison. First: the bottom freelance tier is rationally priced for what it delivers — a 20-minute happy-path install with no operational discipline. Operators getting this and expecting more are setting themselves up for the cleanup engagement six weeks later. Second: the specialist consultant tier and our tier deliver substantially the same scope; the price difference reflects market positioning more than scope. We are competitive at €149-€499 because we have done thousands of these installs and the operational efficiency is high; pure consultants charging $500-$800 for the equivalent work are also delivering quality, just with different cost structures. Third: the enterprise tier ($2,500+) makes sense when you need custom architecture work — multi-datacenter deployments, custom integrations, compliance frameworks (SOC 2, HIPAA, PCI). For a standard PowerMTA + MailWizz install, paying enterprise rates is buying consulting overhead you do not need.

Five operator profiles where one-time installation is the right fit

Below five concrete operator profiles where we have repeatedly seen one-time installation engagements deliver the right outcome. If your situation matches one of these, the discovery call usually moves quickly:

1. Solo entrepreneur or small SaaS validating product-market fit

A solo founder or small team (1-5 people) building a SaaS that needs email infrastructure but does not have engineering capacity to research PowerMTA + MailWizz from scratch. The volume profile is 100K-500K emails/month, the team will operate the platform after handover with the runbook, and the cost economics make managed hosting feel premature. One-time install plus self-maintenance is exactly the right pattern; we have served dozens of solo founders who graduated to managed hosting 18-24 months later when revenue justified the operational hand-off.

2. Existing in-house team adding email infrastructure expertise

An established engineering team (10-50 people) adding email-marketing infrastructure to a product that previously used SaaS providers. The team has Linux DevOps expertise but no specific PowerMTA experience; the install service brings them up to operational competence faster than reading documentation. Our runbook becomes their team's onboarding doc for new hires. Post-installation they handle ongoing operations themselves with occasional consulting check-ins.

3. Migrating from cracked PowerMTA install or compromised system

An operator inherited or acquired a server running cracked PowerMTA or a compromised MailWizz installation and needs to migrate to a clean licensed setup. The install service handles the migration on a new server with proper licensing, data preservation from the old system, and the operator decommissions the old server. About 15-20% of our installation engagements fit this pattern; the operator typically discovered the cracked or compromised state through a deliverability incident.

4. Migrating from CentOS 7 EOL deployment to modern OS

Operator running PowerMTA + MailWizz on CentOS 7 since 2019-2022 needs to migrate to AlmaLinux 8/9 before unpatched-OS exposure becomes a real risk. The migration involves OS rebuild, PowerMTA RPM updating, MariaDB version compatibility checks, and configuration verification. Standard install service plus migration scope; we have done hundreds of these since CentOS 7 EOL in June 2024. About 30% of our 2025-2026 installation pipeline fit this profile.

5. Agency or consultancy installing on behalf of an end-client

A digital agency or hosting reseller whose clients need PowerMTA + MailWizz installations but the agency does not want to develop in-house installation expertise. White-label installation: we install on the agency's client server (with permission), document the handover to the agency's name, the agency relationship-manages the client. Pricing is the same per-install; the agency captures markup on their client billing. Common pattern with reseller programme participants.

Five mistakes operators make when commissioning installations

About 40% of Blue Spirit's installation engagements come from operators who first paid someone else for an install and need it redone correctly. The five mistakes below recur often enough to be predictable:

1. Optimizing on install price rather than total cost of ownership

Operators paying $25 for a Fiverr install think they are saving money compared to a €149+ professional install. The actual TCO calculation: $25 install + 20-40 hours of operator time troubleshooting issues that the cheap install left ($1,500-3,000 of opportunity cost at $75/hour) + likely $400-800 cleanup engagement to fix what was missed = $1,925-3,825 total. Compared to €149+ professional install + 30-day support + runbook = €149-€499 total. The cheap install is structurally more expensive once you account for time and rework. Pay for the right install up front.

2. Not asking for documentation as part of scope

Cheap installs frequently deliver "the system works" without documenting what was changed, where credentials are stored, or how to perform routine operations. Three months later when something breaks at 2 AM, the operator has no documentation to work from and no ability to reach the original installer. The fix: explicitly require a written runbook as part of any installation engagement, regardless of price tier. If the installer cannot or will not provide one, walk away — they are selling installs but not finished engagements.

3. Skipping FBL registration assuming PowerMTA handles it automatically

PowerMTA can consume FBL emails (it has the parser logic built in), but FBL registration with each major ISP (Yahoo, AOL, Comcast, etc.) is a separate operator action — submit the form on each ISP's postmaster site, designate the bounce mailbox to receive complaints. Cheap installs frequently skip this because it is operator paperwork rather than technical work. Result: complaint signals are silently lost, sender reputation degrades without visible cause, deliverability drops 6-12 weeks post-install. The fix: FBL registration is part of scope on any production install regardless of installer.

4. Installing on shared or budget VPS that lacks resource headroom

PowerMTA + MailWizz combined stack realistically needs 4 vCPU, 8GB RAM, and 100GB SSD as production minimum. Operators provisioning a $5/month 1GB-RAM VPS hit performance walls within weeks — slow MySQL queries, queue worker OOM kills, web UI timeout under tenant load. The fix: provision appropriate hardware before the install. Hetzner CX31 (€15/month, 4 vCPU + 8GB RAM + 80GB SSD) is the budget floor that actually works; everything below that fails at production scale.

5. Pointing the new install at a stale or dirty subscriber list immediately

The install completes successfully, the operator imports their existing subscriber list (which has been sitting unmaintained for 6-12 months), sends a campaign on day one, watches the bounce rate hit 15-20% and the IP get blacklisted. The install is fine; the operator just executed the worst possible first-send pattern. The fix: validate the subscriber list before importing (use a service like NeverBounce or ZeroBounce), warm the IPs gradually starting with most-engaged subscribers, do not send to inactive subscribers in the first 30 days. The runbook explicitly warns about this; operators who skip the runbook predictably hit this wall.

Stack-specific scope — what each install actually covers, line by line.

The table below is the line-by-line scope for each installation tier. We publish it because clients frequently ask "what is included in PowerMTA install vs MailWizz install vs the combined stack?" — the honest answer is the matrix below. Anything outside the matrix is custom scope and gets quoted separately during discovery.

Component / scope item	PMTA install (€149+)	MailWizz install (€199+)	Acelle install (€199+)	Combined stack (€349+)
OS hardening (SSH, firewall, patches)	✓	✓	✓	✓
Nginx + HTTPS termination	⚠ if needed for admin UI	✓	✓	✓
PowerMTA 6.0 install + global config	✓	✗ separate	✗ separate	✓
VirtualMTA pools per IP	✓ up to 16 IPs	✗	✗	✓ up to 16 IPs
DKIM key generation + SPF + DMARC	✓	✓	✓	✓
DNS records published in your DNS	✓	✓	✓	✓
FBL registration + bounce mailbox	✓ all major ISPs	✗ requires PMTA	✗ requires PMTA	✓ all major ISPs
MailWizz core install + tracking domain	✗	✓	✗	✓
Acelle Mail core install + multi-tenant SaaS mode	✗	✗	✓	⚠ Acelle OR MailWizz, not both
MySQL 8.0 tuned for write-heavy	✗ not needed	✓	✓	✓
Redis 7 + Supervisor queue management	✗ not needed	✓	✓	✓
PHP-FPM 8.2+ tuning	✗ not needed	✓	✓	✓
Bounce processor daemon	✓ standalone	⚠ MailWizz native or PMTA bridge	⚠ Acelle native or PMTA bridge	✓ PMTA → app bridge
Test campaign + smoke test	✓	✓	✓	✓
Handover runbook (PDF + markdown)	✓ 15-25 pages	✓ 15-25 pages	✓ 15-25 pages	✓ 30-50 pages
30-day post-install support	✓	✓	✓	✓

Three observations from the scope matrix. First: the PowerMTA-only install does not include a web application — operators frequently get confused expecting a UI and getting a CLI service. PowerMTA is the SMTP back-end; you need MailWizz, Acelle, Mautic, or your own application as the front-end that PowerMTA delivers email for. Second: the combined stack price (€349+) is a discount versus buying PowerMTA + MailWizz separately (€149 + €199 = €348) because we do them together as one engagement with shared OS hardening and configuration verification. Third: Acelle and MailWizz are mutually exclusive in the standard combined stack — they are competing platforms doing the same job. If you want both for different tenant segments, that is a custom multi-platform engagement quoted separately.

Migration vs greenfield — two fundamentally different installation engagements

Operators frequently treat "install PowerMTA on my server" as one thing. It is two things, and the operational complexity differs by 3-5×. Greenfield install is what most people picture: clean server, fresh installation, configuration tuning, handover. Migration install is greenfield install plus moving data, preserving sender reputation, validating the new system matches the old system's behavior, and decommissioning the old environment without service interruption. Understanding which type your engagement is determines the right scope and pricing.

Greenfield install — the simpler engagement

You provisioned a new server, you have no existing email infrastructure to preserve, you want PowerMTA + MailWizz installed and ready to send. The scope is what we install on this new server: OS hardening, application install, configuration tuning, DNS records published, FBL registration, smoke test, handover. Timeline 2-5 days depending on whether it is a single-product install or the combined stack. Pricing fits cleanly into the €149-€499 range. About 60% of our installation engagements are greenfield.

The greenfield install path has predictable scope because there is no legacy system constraining decisions. We pick the OS we prefer (AlmaLinux 8/9), the database version we recommend (MySQL 8.0), the cache backend that performs best (Redis 7). Operators who have engineering opinions get to specify; operators who do not want to make these decisions get sensible defaults. The runbook documents what was chosen and why so future migrations have context.

Migration install — the complex engagement

You have an existing email infrastructure (CentOS 7 + PowerMTA 5.x + MailWizz 1.x, or a SendGrid account, or a competing self-hosted platform) and you need to migrate to a new server with current versions. The scope expands meaningfully: greenfield install on the new server, plus data migration (subscriber lists, suppression lists, campaign history, template library), plus reputation preservation (DKIM key handling, IP warmup planning, parallel-send strategy), plus validation (sending behavior matches the old system, deliverability metrics do not regress), plus old-system decommissioning. Timeline 7-14 days; pricing typically €600-€1,500 depending on data volume and complexity.

The migration install path has unpredictable scope because the legacy system's quirks determine what work is actually required. A clean SendGrid-to-MailWizz migration is mostly data export and reputation transfer; a CentOS 7 + PowerMTA 5.x + MailWizz 1.x migration is OS rebuild plus PowerMTA major version upgrade plus MailWizz major version upgrade plus database schema migration. We always do a discovery phase before quoting migration installs because the scope depends on what we find when we audit the legacy system. Operators expecting fixed-price migration quotes without discovery are signaling they have not done one before.

The hybrid pattern — install fresh, migrate selectively

Some operators run both old and new systems in parallel for 30-90 days. New campaigns go to the new system from day one; subscriber data migrates progressively as old campaigns complete; sender reputation transfers gradually via shared-IP overlap during the transition window. This pattern reduces risk meaningfully but requires running two systems simultaneously, which adds operational complexity during the transition. We have done this pattern for operators where migration risk was unacceptably high — typically large established lists where deliverability degradation would cost meaningful revenue.

The hybrid pattern is not always the right answer. For smaller operations (under 100K subscribers, under 1M emails/month), the operational complexity of running parallel systems exceeds the risk reduction. For larger operations (500K+ subscribers, 5M+ emails/month), the parallel-systems pattern is frequently worth the complexity because the cost of getting migration wrong is meaningfully larger than the cost of running two systems for 60 days.

What discovery actually accomplishes for migration engagements

Before we quote a migration install, we do a paid discovery phase (€150 deposit, applied to engagement) where we audit the legacy system, document what is currently running, identify migration risks, and produce a written migration plan. The audit covers: OS version and patch level, application versions and customizations, database size and schema state, IP reputation and warmup history, DNS configuration and record state, FBL registration status with each ISP, integration points with external systems (CRMs, analytics, billing), volume profile and seasonal patterns. The output is a 5-10 page migration plan that becomes the contract scope for the actual engagement.

About 20% of discovery phases conclude with "the migration is more complex than this engagement should handle, you should hire a senior consultant or run the migration in-house with our advisory support". Honest discovery is what separates migration engagements that succeed from migration engagements that become billing disputes. Operators who reject the discovery phase and demand fixed-price migration quotes upfront are flagging that they have not done a migration before; those engagements are statistically more likely to fail. We will work with operators who want fixed-price upfront, but the price will reflect the unknown-scope risk premium.

When NOT to commission an installation engagement — five honest scenarios

Not every operator who thinks they need an install actually needs one. The five scenarios below are situations where we have repeatedly told operators "do not pay us, do something else instead". We document them publicly because the bias in our sales conversations should be honesty about fit, not maximizing engagements that will produce unhappy outcomes.

1. You are testing whether you want to send email at all

If you are still validating whether email marketing fits your business model, do not commission a self-hosted install. Use Brevo's free tier (300 emails/day), Mailchimp's free tier (500 sends to 500 subs), or Resend's free tier (100 emails/day) to validate the use case first. The €149-€499 install plus €15-30/month VPS plus operational time you would commit to self-hosted is wasted spending if you discover six weeks later that email is not core to your strategy. We have refunded operators who hit this realization mid-engagement; the kinder honest answer is "wait six months until you know you need this".

2. Your volume is genuinely low and likely to stay low

Self-hosted email infrastructure breaks even against SaaS alternatives at roughly 100K-200K emails/month. Below that threshold, the operational overhead of maintaining your own server (security patches, backup verification, queue worker monitoring, occasional outage troubleshooting) costs more in operator time than SaaS pricing costs in dollars. If you genuinely send 5K-50K/month, stay on hosted services. The math only flips at higher volumes; we explain the breakeven analysis during discovery and frequently recommend operators stay on hosted SaaS rather than commission an install.

3. You do not have anyone who can SSH into a server when something breaks

The 30-day post-install support covers issues related to what we installed. It does not cover operational incidents three months later (server outage, OS upgrade required, MySQL fills up disk). If your team genuinely cannot operate a Linux server post-handover, the right answer is managed hosting rather than install plus self-maintain. Managed hosting prices are €89-€279/month for the same stack; over 12 months that is comparable to install + ongoing self-maintenance time cost. We sell both services; the right answer depends on whether you have someone who actually wants to operate the server.

4. You are migrating to escape a problem you have not understood

Operators sometimes commission migrations because "deliverability is bad on our current platform" without diagnosing why deliverability is bad. If the root cause is dirty list, sending pattern issues, content quality, or compliance violations, migrating to a new platform reproduces the same problems within 60 days. The new platform is not the fix. We do diagnostic discovery before migration engagements specifically to identify whether migration is the right answer or whether the operator should fix root causes on the existing platform first. About 15% of migration discovery calls conclude with "do not migrate yet, fix X first".

5. Your hosting environment is structurally hostile to email infrastructure

Some hosting environments make production email infrastructure impractical: cPanel/Plesk shared hosting that blocks port 25, AWS EC2 with the default port 25 throttle that requires support ticket to lift, residential ISP connections that get every outbound mail blacklisted. We can install on these environments, but the install will not produce good outcomes regardless of installation quality. The honest answer is "change your hosting environment first, then commission the install on appropriate infrastructure". We can recommend providers (Hetzner, OVH, Contabo, dedicated email-friendly providers) during discovery; we will not pretend the install will work on hostile infrastructure just to capture the engagement.

Installation service — frequently asked questions

What do you install exactly?

Our main installation services are: PowerMTA 6.0 (global config, VMTAs, authentication, bounce and FBL wiring), MailWizz (core + PowerMTA integration + SaaS mode if needed), Acelle Mail, Interspire (including legacy versions on modern PHP), and full stacks combining the above. We also handle mail server stacks (Postfix/Dovecot), webmail, DNS zone files, monitoring (Grafana + Prometheus), and Nginx with TLS.

Do I have to host with you?

No. Our installation service is a one-time engagement you can commission on a server of your choice — AWS, DigitalOcean, Hetzner, OVH, Contabo, your own datacenter. We just need root SSH access for the duration of the work. If you later want us to manage the server, we can, but it is not required.

How long does it take?

Installation time depends on what you are deploying — a single PowerMTA install is much faster than a full multi-tenant MailWizz + PowerMTA + Acelle stack with custom monitoring. We confirm the exact timeline as part of the quote, after a short discovery call where we understand your stack, your servers and your goals. We commit to that timeline in writing and we hit it.

What if something breaks after the installation?

Every installation includes 30 days of post-delivery support for any issue related to what we installed. After 30 days you can extend with a management contract or handle it yourself — we document everything so a competent admin can pick up from where we left off.

Do you provide the licences?

If we are installing a licensed product (PowerMTA, MailWizz, Acelle), we expect you to supply a valid licence or buy it through us. We do not install pirated software, ever.

Why does this cost €149+ when I see Fiverr installs for $5-$25?

The €5-25 freelancer market exists, but the structural problems are predictable: shared installer scripts that miss configuration nuances, no reputation isolation strategy, no FBL setup, no 30-day support, no documentation. About 40% of our installation engagements are clients who first paid a Fiverr freelancer and are now paying us to fix what was installed. The €149+ price reflects what professional installation actually costs to deliver correctly the first time, with a runbook your team can use after handover.

Can you install on my AWS / DigitalOcean / Hetzner / Contabo server?

Yes. We work on any Linux server with root SSH access. We have done installations on AWS EC2, AWS Lightsail, DigitalOcean droplets, Hetzner dedicated servers, OVH dedicated, Contabo VPS, Vultr, Linode (now Akamai), Google Cloud Compute Engine, and on private datacenter hardware. The server provider does not matter; what matters is the OS version (we recommend AlmaLinux 8/9, Debian 11/12, Ubuntu 22.04 LTS) and resource specs appropriate for the workload.

What OS versions do you support?

AlmaLinux 8 and 9 are our preferred targets for PowerMTA stacks because RHEL-family compatibility is the path of least resistance for PowerMTA RPMs. Debian 11/12 and Ubuntu 22.04 LTS work well for MailWizz and Acelle stacks. We avoid CentOS Stream (rolling release pattern is wrong for production email infrastructure) and CentOS 7 (EOL since June 2024). If you have a specific OS requirement we can usually accommodate; ask during discovery.

Can you install on shared hosting (cPanel, Plesk)?

Almost never. PowerMTA, MailWizz, and Acelle all require root access, custom service management (systemd or supervisor), and direct port 25 / port 587 access that shared hosting providers either do not allow or restrict heavily. If you want a managed-style experience, dedicated VPS at €5-30/mo from a provider like Hetzner or Contabo costs less than upgrading shared hosting to allow what email platforms need. We will tell you honestly during discovery if your hosting choice will work or not.

What happens if my server gets blacklisted after installation?

Blacklisting after installation usually points to two root causes: dirty list (the operator sent to a spam-trap-heavy list immediately after install) or insufficient warmup (full volume immediately on cold IP). Neither is the installation itself; both are operational mistakes the runbook explicitly warns about. Within the 30-day support window, we help you diagnose the cause and execute IP recovery (delisting requests, warmup re-start at lower volume). After 30 days, blacklisting recovery becomes a separate consulting engagement.

Let's get your stack installed properly and move on.

Book a discovery call Chat on WhatsApp