Interspire · Legacy & modern

Interspire Email Marketer hosting, kept alive on modern infrastructure.

For teams with years of Interspire history — customised themes, translated templates, accumulated automation — we keep the install running on up-to-date PHP, modern MySQL and our dedicated PowerMTA back-end.

PHP 8.x compatible
Legacy versions welcome
PowerMTA delivery
Dedicated IPs
Migration included

Migrate my Interspire Compare options Chat on WhatsApp

Why keep Interspire running

Don't throw away years of Interspire work because your host got lazy.

Interspire Email Marketer is no longer the newest platform in the room — the last major release is years old — but thousands of businesses still run campaigns on it every day. Many of them sit on heavily customised installs: translated templates, bespoke automations, custom fields tied to ERP systems. Ripping that out and migrating to a newer ESP is often a year-long project.

We take the opposite view. If your Interspire is working and your team knows it well, the problem is not Interspire — it is probably an ageing server, a PHP version that is about to lose security updates and an MTA that never delivered anything reliably anyway. Fix the infrastructure, keep the platform.

Modern PHP, hardened legacy

We run Interspire on PHP 8.x through a compatibility layer, backport security patches and isolate known-legacy endpoints behind a proxy. Security without the rewrite.

PowerMTA delivery

Interspire's built-in sender is bypassed in favour of PowerMTA. Per-ISP throttling, DKIM, DMARC, FBLs — all the deliverability features Interspire never had.

Cron and queue tuning

Interspire's sending cron ships with defaults that have not changed since 2016. We tune concurrency, queue batching and database indexes for your real workload.

Backups and DR

Full database and filesystem backups weekly, retained off-site. MySQL point-in-time recovery for the last 7 days. Interspire upgrades tested in staging first.

Who chooses Blue Spirit for Interspire hosting

Mostly ESPs and agencies that built their business on Interspire between 2010 and 2018 and who now want a grown-up host that understands the platform — rather than a generic shared provider that will disable their cron the first time it spikes CPU. We also host Interspire for regional publishers in Latin America and Europe who have years of Spanish, Portuguese or Italian templates, bilingual automations and customer workflows that would cost a fortune to rebuild.

Whatever your situation, we will not pressure you to migrate. If you want to evaluate MailWizz or Acelle, we will set up a parallel environment so you can compare side-by-side. If you decide to stay on Interspire, we will operate it professionally for as long as you need.

Pricing

Because every Interspire install is different — different PHP version, different data size, different custom modules — we quote Interspire hosting case by case. As a reference, the infrastructure baseline matches our MailWizz pricing: starter environments from € 89/month, mid-tier from € 169/month, high-volume from € 279/month. Migration from your current provider is included on mid-tier and above.

2026 reality

The "Interspire is dead" narrative is wrong. Three forces resurrected the platform between 2024 and 2026.

If you read articles from 2020-2022 saying Interspire Email Marketer was abandoned, those articles are now factually wrong. Three concrete shifts changed the platform's positioning meaningfully, and operators evaluating Interspire in 2026 should understand the current reality before making migration-vs-stay decisions.

First, Interspire shipped four major releases in 2025-2026 with substantive new features. Version 8.7.0 (July 2025) added Cloudflare Turnstile CAPTCHA, honeypot spam protection, and cross-site form embedding. Version 8.7.1 (October 2025) extended automatic cleanup to unsubscribed contacts and added new XML API methods. Version 8.7.2 (December 2025) added IPv6 support across all tracking tables, proxy header support for reverse proxy and load balancer deployments, and disabled-by-default RSS feeds for security hardening. Version 8.7.3 (February 2026) added new automation trigger types — Autoresponder Opened, segment subscription, list owner notifications — plus Large System Mode for installations managing millions of contacts. The release cadence over 12 months is healthy active development, not maintenance-mode patching.

Second, PHP 8.2/8.3 support reached production maturity in v8.5.0 (December 2024) with PHP 8.4 readiness shipping incrementally across the v8.7.x series. The "Interspire only runs on PHP 5/7" reputation is now five years out of date. Modern Interspire deployments run on PHP 8.3 with MySQL 8.0 on AlmaLinux 9 or Ubuntu 22.04 LTS — the same modern stack as MailWizz or Acelle deployments. The compatibility-layer hosting pattern that emerged 2018-2022 (running Interspire 6.1.x behind hardened PHP 7.4 proxies) is becoming legacy itself; operators on those configurations should be planning upgrades to v8.5+ on PHP 8.x rather than perpetuating the compatibility-layer pattern indefinitely.

Third, the IEM Addons ecosystem signaled the platform's renewed health by discontinuing its Advanced Triggers addon. The reason: v8.7.3 made the addon's functionality native to core Interspire. When third-party addon vendors are losing addressable market because the core product is investing in features they used to charge for, that is structurally a healthy platform signal. The remaining IEM Addons portfolio (premium templates, custom integrations, specialized reporting) continues to operate; the bellwether discontinuation suggests the platform is competing with newer ESPs on workflow sophistication rather than ceding ground.

The takeaway: in 2026 Interspire is in its strongest position since 2018 — modern PHP support, active feature development, healthy addon ecosystem evolution, and pricing economics that beat per-subscriber SaaS at scale. Operators with existing Interspire installs have less reason to migrate than they did in 2022; operators starting fresh have more reason to seriously evaluate Interspire alongside MailWizz and Acelle than mainstream "compare email platforms" articles suggest.

Decision framework

Five-question decision tree — should you stay on Interspire or migrate?

The tree below walks the same logic we use during discovery calls with operators currently running Interspire who are weighing migration versus modernization. Five binary questions, four terminal recommendations including a "migrate now" branch when staying is genuinely the wrong choice and a "stay and modernize" branch when migration would be premature.

Two sub-points worth noting. First: the "vanilla deployment + alternatives" branch is honest output — if your Interspire install is vanilla and you do not have years of customization sunk cost, MailWizz or Acelle on a fresh install will likely save your team significant time over the next 24 months. We are not commercially biased toward keeping you on Interspire; we host all three platforms on the same infrastructure with the same margins. Second: the "legacy version" branch resolves to upgrade-first, decide-later. If you are running Interspire 6.x or 7.x in 2026, your immediate task is upgrading to 8.5+ regardless of long-term migration plans, because the v8.5+ codebase has substantively better PHP 8.x compatibility, MySQL 8.0 support, and security posture than legacy versions. After upgrade, the stay-vs-migrate decision becomes meaningful in a way it was not while you were running unsupported PHP versions.

Modernization stack — what we deploy when you stay on Interspire.

The diagram below shows the full production stack we deploy for managed Interspire customers in 2026. The stack reflects what modern Interspire actually deserves now that v8.7.3 supports PHP 8.3, MySQL 8.0, and IPv6 natively — not the compatibility-layer hosting pattern that emerged when operators ran legacy 6.x on outdated PHP. Everything is configured, monitored, and patched by us; nothing is hand-rolled.

Three observations from the modernization stack. First: PowerMTA replaces Interspire's native SMTP sender, not augments it. Interspire's built-in SMTP is functional but lacks per-ISP throttling, accounting log granularity, and the FBL processing patterns that production-grade deliverability requires. Operators who keep Interspire's native sender for "simplicity" are leaving 30-50% of their inbox placement potential on the table. Second: Redis is optional for Interspire because the core does not depend on it — unlike Acelle (Laravel queue workers) or modern Mautic, Interspire uses cron-driven task processing rather than queue worker pools. We deploy Redis when the install crosses 1M+ subscribers because session management and rate limiting benefit from caching, but smaller deployments run fine without it. Third: the IPv6 dual-stack support added in v8.7.2 actually matters for compliance environments. Operators in regulatory contexts (healthcare, finance) increasingly need IPv6 reachability for audit-trail completeness; Interspire on the modern stack handles this natively as of December 2025.

Interspire version timeline — what changed when, and what it means for your install.

The table below maps Interspire releases from 2018 to 2026 against the technical capabilities each release introduced. Operators on legacy versions can use this to identify what their current install lacks; operators considering Interspire fresh in 2026 can use this to confirm the platform is in active development.

Version	Released	Key technical capability	Status in 2026
6.1.x	2018 era	PHP 5.6/7.0, no MySQL 8 support	Legacy — must upgrade
7.0.0	2022	PHP 8.0/8.1 added	Aging — should upgrade
8.3.0	2024	MySQL 8.0 support added	Acceptable, dated UI
8.5.0	December 2024	PHP 8.2/8.3 + modernized UI	Acceptable production target
8.6.0	January 2025	Bounce processing fixes, UTF-8 imports	Acceptable production target
8.7.0	July 2025	Cloudflare Turnstile, honeypot, cross-site forms	Recommended baseline
8.7.1	October 2025	Email search filters, contact cleanup	Recommended baseline
8.7.2	December 2025	IPv6 support, proxy headers, RSS hardening	Strong production target
8.7.3	February 2026	Advanced triggers, Large System Mode (millions of contacts)	Current — recommended for new installs

Three observations from the version timeline. First: the gap between v6.1.x (2018-era) and v8.7.3 (2026) is roughly equivalent to the gap between MailWizz 1.x and 2.x; operators on legacy versions are not running "old Interspire", they are running an effectively different platform. Second: the release cadence accelerated meaningfully from late 2024 onward — five major releases between December 2024 and February 2026. That cadence is comparable to MailWizz's v2.x release cycle and dramatically faster than the v6.x era. Third: the v8.7.x series is where Interspire became competitive again on automation features (v8.7.3 trigger types) and operational maturity (v8.7.2 IPv6 + proxy headers + Large System Mode prep). Operators evaluating Interspire in 2026 should anchor on v8.7.3 as the reference point, not on the 2020-era platform documentation that still appears in older articles.

Interspire 8.7.3 vs MailWizz vs Acelle vs Mautic — the honest 2026 capability comparison.

Most platform comparisons treat Interspire as legacy and dismiss it. That framing was reasonable in 2020-2022 but is now wrong. The matrix below compares Interspire 8.7.3 against the three most common alternatives on the dimensions that actually matter for production decisions.

Capability	Interspire 8.7.3	MailWizz	Acelle	Mautic
Codebase / framework	⚠ Yii 1.x (mature)	⚠ Yii 1.x (mature)	✓ Laravel 12	✓ Symfony 6
License model	⚠ $295 + $399/yr maintenance	✓ $79-$249 perpetual	✓ $64-$199 perpetual	✓ free GPL
PHP support (current)	✓ 8.2/8.3, 8.4 in progress	✓ 8.x	✓ 8.2+ required	✓ 8.1+
Active development cadence	✓ 5 releases 2024-2026	✓ active	✓ active	✓ active community
Multi-tenant SaaS native	⚠ multi-user, not full SaaS	⚠ via extension	✓ from day one	✗ single-tenant
Automation / triggers	✓ 8.7.3 advanced triggers	⚠ basic autoresponders	✓ visual workflows	✓ best-in-class
Large dataset performance	✓ Large System Mode 8.7.3	✓ established	✓ distributed deploy	✓ horizontal scaling
Direct PowerMTA integration	✓ via SMTP delivery	✓ first-class	✓ first-class	⚠ requires custom config
REST/XML API	✓ XML API + new methods	✓ REST	✓ REST	✓ REST
Form security (CAPTCHA, honeypot)	✓ Turnstile + honeypot 8.7.0	✓ reCAPTCHA	✓ reCAPTCHA	✓ reCAPTCHA
IPv6 support	✓ since 8.7.2	⚠ partial	✓ Laravel native	✓ Symfony native
Extensions / addons ecosystem	⚠ small (IEM Addons)	✓ richest (200+)	⚠ smaller (~30)	⚠ medium (~100)
Operator skill required	⚠ PHP/MySQL admin	⚠ PHP/MySQL admin	⚠ Laravel admin	⚠ Symfony admin
Data ownership	✓ self-hosted	✓ self-hosted	✓ self-hosted	✓ self-hosted

The matrix exposes the structural reality: Interspire 8.7.3 is now competitive with MailWizz on automation features (where it was previously behind) and ahead of MailWizz on form security (Turnstile + honeypot ship native), IPv6 support (since v8.7.2), and Large System Mode (millions of contacts native). The remaining MailWizz advantage is the extensions ecosystem (200+ extensions vs Interspire's smaller IEM Addons portfolio). Acelle wins on multi-tenant SaaS architecture and Laravel modernity; Mautic wins on workflow sophistication and pure GPL license. The "Interspire is legacy and dying" narrative is empirically wrong as of 2026 — operators should evaluate based on current capabilities rather than five-year-old impressions.

Five operator profiles where managed Interspire is the right fit in 2026

Below five concrete operator profiles where managed Interspire on modern infrastructure is structurally the right answer in 2026. If your situation matches one of these, the discovery conversation usually moves quickly:

1. Long-time Interspire operator with years of customizations

An operator (ESP, agency, or in-house team) running Interspire since 2014-2018 with substantial sunk-cost investments: customized templates in multiple languages, bespoke automation flows tied to ERP systems, custom fields integrated with internal CRM, branded subscription forms embedded across multiple websites. Migrating to MailWizz or Acelle would require rebuilding all of these from scratch. The 8.7.3 platform is feature-competitive with the alternatives, so migration would be lateral movement at significant cost. Stay on Interspire, modernize the infrastructure underneath, get on with operations.

2. Regional publisher in non-English-speaking markets

A publisher in Spain, Italy, France, Germany, the Nordics, or other non-English EU market with extensive translated email templates, multilingual subscription forms, regulatory-compliance content tailored to specific jurisdictions (LSSI in Spain, UWG §7 in Germany, Garante decisioni in Italy, CNIL guidance in France), and customer relationships spanning 5-10 years on the platform. The translation work alone is a barrier to migration; the customer-facing branding consistency matters more than the platform identity. We host Interspire for several publishers in this profile across Continental Europe and the UK.

3. Compliance-sensitive sender needing perpetual-license model

A fintech, healthcare provider, or regulated industry operator where SaaS subscription billing creates audit complexity (recurring vendor relationship, per-contact data sharing terms, shifting AUP that creates compliance review burden). Interspire's perpetual-license model ($295 one-time + $399/year maintenance, optional) fits these procurement contexts better than per-subscriber SaaS pricing. The data ownership story is identical to MailWizz/Acelle but the licensing relationship is structurally simpler for compliance review.

4. Operator on legacy 6.x or 7.x version needing modernization without migration

An operator running Interspire 6.1.x or 7.x on an aging server with PHP 7.4 or older. The current install works but is increasingly hard to maintain — security patches lagging, hosting provider warning about PHP version sunset, occasional crashes that take longer to diagnose. The path forward is upgrade to 8.7.x on modern PHP 8.3 infrastructure, not migration to a different platform. We handle the version upgrade as part of the hosting onboarding; data flows seamlessly because Interspire's database schema upgrade is well-tested.

5. Mid-volume operator (250K-2M emails/month) graduating off SaaS

An operator currently paying $300-1,500/month for Mailchimp, ActiveCampaign, or similar SaaS who has hit the volume tier where self-hosted economics flip. Interspire on managed PowerMTA hosting at €169/month (Growth tier) saves 50-80% versus the SaaS alternative while delivering equivalent functionality. The platform choice (Interspire vs MailWizz vs Acelle) at this volume is secondary to the self-hosted-vs-SaaS decision; Interspire is a credible answer when the operator's team prefers its UI/workflow conventions.

Five mistakes operators make running Interspire in 2026

About a third of Blue Spirit's managed Interspire clients are migrating from a self-hosted Interspire deployment that hit operational walls. The five mistakes below recur often enough to be predictable:

1. Running Interspire's native SMTP sender instead of PowerMTA

Interspire ships with a built-in SMTP sender that uses PHP's mail() or fsockopen() to deliver email directly. It works at small scale but lacks per-ISP throttling, accounting log granularity, FBL ingestion, and the rate-limiting patterns that production deliverability requires. At any volume above ~50K emails/month, native SMTP delivery starts producing reputation damage that is operationally difficult to recover from. The fix: configure Interspire to relay through PowerMTA, Postfix-with-DKIM-OpenDKIM, or any production-grade MTA. Native SMTP is for testing, not production sending.

2. Staying on legacy versions because "upgrades break things"

Operators on Interspire 6.x or 7.x sometimes refuse to upgrade because they tried once and it broke a custom modification. The fix is not to refuse upgrades indefinitely; the fix is to do the upgrade properly. We do the upgrade in staging first, identify customizations that need updating for the new version, port them, validate, then promote to production. Refusing upgrades indefinitely means staying on PHP versions that lose security support, which becomes a worse problem than the initial upgrade pain.

3. Missing the v8.7.3 advanced triggers that replace third-party addons

Operators paying for IEM Addons' Advanced Triggers addon (now discontinued because v8.7.3 made the functionality native) or other addon dependencies that have been absorbed into core. The fix: review your addon portfolio annually against current Interspire releases. Several addons that were essential in 2022 are now redundant because their functionality shipped to core. Continuing to pay addon vendors for capabilities that are now native is wasted spend.

4. Not enabling Large System Mode when subscriber count crosses 1M

Interspire UI responsiveness degrades meaningfully when subscriber lists cross 500K-1M contacts because legacy SQL queries calculate segment sizes and statistics on every page load. The v8.7.3 Large System Mode adds on-demand calculation and batched summaries to address this. Operators who do not enable it after crossing the threshold experience progressively slower admin UI, eventually leading to "the platform feels broken" complaints that are actually configuration issues. The fix: enable Large System Mode in the admin settings; we do this by default for Growth tier and above on managed deployments.

5. Treating bounce processing as set-and-forget rather than monitored

Interspire's bounce processing has been improved across multiple v8.7.x releases (better RFC categorization, Google compliance, OAuth bounce processing fixes). Operators on older versions or with default bounce processing configurations frequently see "stuck bounces" — contacts that should have been removed from active lists remaining in active rotation. The fix: monitor bounce processing logs as a routine operational task, validate that bounce categories are flowing correctly, alert on stuck bounce processing. We include this in our managed deployment standard ops; self-deployers frequently skip it because Interspire's defaults appear to "just work" until they don't.

How Interspire migrations actually work — what the 48-72 hour timeline covers

About a quarter of our managed Interspire engagements start as migrations from another hosting provider rather than from-scratch installs. The 48-72 hour migration timeline is real and we hit it consistently, but the activities that fit inside that window are worth understanding so operators can plan accordingly. The walkthrough below is what actually happens during a typical Interspire migration engagement.

Pre-migration discovery (24-48 hours before migration starts)

Before we touch the legacy system, we audit it: Interspire version (determines upgrade-then-migrate vs migrate-as-is path), PHP version on source server (determines compatibility with destination stack), MySQL version and database size (determines dump strategy), filesystem size (determines transfer time), customizations to track during migration (custom themes, modified controllers, third-party addons installed, integration touchpoints), DNS configuration (subscription form domains, tracking domains, sender domains), IP addresses currently in use and warmup state, FBL registrations to transfer or re-register. The output is a written migration plan that goes to you for approval before we proceed. Most discovery completes within 24-48 hours; complex installs with extensive customizations may take longer.

Day 1: New environment provisioning + first data copy

We provision the destination server (AlmaLinux 9, PHP 8.3, MySQL 8.0, Nginx 1.24, PowerMTA 6.0) using our standard managed-Interspire stack. Initial database dump from the source server, restored on destination. Filesystem rsync from source to destination. Interspire admin UI brought up on destination using temporary subdomain. We run a smoke test: log in, verify list counts match, send a single test campaign to a personal email address. This first-day work happens with the source system still actively operating; no traffic has moved yet. Source system continues sending campaigns normally.

Day 2: Customization validation + integration testing

If the source had customizations (modified controllers, custom themes, custom integrations with external systems), Day 2 is when we validate they work on the destination. Some customizations need updating for newer Interspire versions; some need updating for newer PHP versions; some integration credentials need rotation. We run these in staging mode on the destination — not yet receiving traffic — to confirm everything works before promoting to production. About 60% of migrations have at least one customization that needs adjustment during Day 2; the remaining 40% are clean and Day 2 is mostly verification.

Day 2-3: Final data sync + DNS cutover

Once the destination is validated as working correctly, we do a final database dump-and-restore (incremental from Day 1 baseline, capturing any campaign sends that happened during the migration window). DNS cutover happens at a coordinated time: we update A records, MX records (for bounce processing), CNAME records (for tracking domains), and TXT records (DKIM, SPF, DMARC). DNS propagation takes 30-60 minutes typically; during propagation, traffic gradually shifts from source to destination. We monitor metrics on both systems during this window to catch any unexpected issues.

Day 3: Post-cutover validation + source decommissioning

After DNS fully propagates, we validate that all traffic is hitting the destination correctly: subscription forms working, tracking pixels firing, click-through redirects functioning, bounce processing flowing, FBL signals reaching the destination's bounce mailbox. Once we confirm 24 hours of clean operation on the destination, we decommission the source system: shut down services, take final backup, archive credentials, terminate the source server (or hand it back to you to decommission depending on engagement terms). The full timeline from "go" decision to "destination operational + source decommissioned" is typically 48-72 hours; longer for installs with extensive customizations or complex DNS topologies.

What can extend migration beyond 72 hours

Three factors regularly push migrations past the 72-hour baseline. First: extensive customizations requiring porting — heavily customized themes, modified controllers, third-party addons that need re-installing or updating. Second: large datasets requiring extended transfer windows — installations with 5M+ subscribers or hundreds of GB of campaign history take longer to dump, transfer, and restore than smaller installs. Third: legacy version migrations requiring intermediate upgrades — migrating from Interspire 6.1.x directly to 8.7.x is not a single-step operation; we typically do 6.1.x → 7.0.0 → 8.5.0 → 8.7.x in staged upgrades over 5-7 days. We flag these scenarios during discovery so timeline expectations are realistic upfront.

When NOT to choose Interspire — five honest scenarios

Despite Interspire's improved 2026 positioning, it is not the right answer for every operator. Below five concrete scenarios where we have repeatedly told operators "Interspire is not the right fit, consider X instead":

1. You are building a multi-tenant SaaS where end-customers need their own branded email-marketing layer

Interspire supports multiple admin users and basic customer-account management, but it is fundamentally a multi-user platform rather than a multi-tenant SaaS architecture. Plans, subscriptions, billing, resource quotas, and tenant-level data isolation are not first-class concepts. For SaaS builders embedding email-marketing into their product (real estate platform, healthcare scheduler, e-commerce platform giving end-customers branded email capability), Acelle Mail's native multi-tenant architecture is structurally better. Interspire works for this use case but requires significant custom development; Acelle works out of the box.

2. You need the most sophisticated marketing automation workflows available

Interspire 8.7.3's advanced triggers are competitive with MailWizz autoresponders and ahead of basic Mailchimp Customer Journeys. They are not as sophisticated as Mautic's behavior-driven automation flows or HubSpot's enterprise-grade Customer Journey Builder. If your primary email-marketing requirement is sophisticated multi-channel automation (email + SMS + push + behavioral triggers + lead scoring), Mautic on the same managed PowerMTA infrastructure is the right answer. Interspire supports the basics well; sophisticated automation is not its strength.

3. You want a free, fully open-source platform with GPL licensing

Interspire is commercial software (perpetual license + maintenance contract model). The license terms are reasonable and the cost economics work at production scale, but it is not GPL-licensed open-source. If your procurement requirements specifically demand free, fully open-source platforms (some compliance environments, some procurement processes that prohibit commercial software in certain categories), Mautic is the right answer. The data-ownership story is identical to Interspire but the licensing relationship is structurally different.

4. Your team is fundamentally a Laravel shop with no Yii experience

Interspire and MailWizz both run on Yii 1.x, which is a different framework from modern Laravel or Symfony. Your engineering team can learn Yii quickly if motivated, but if your existing codebase is heavily Laravel-based and your hires are filtered for Laravel experience, the platform extensibility you can achieve on Acelle (Laravel 12) will be meaningfully greater than what you can achieve on Interspire (Yii 1.x). For pure Laravel shops, Acelle on the same managed infrastructure is the better fit. Interspire works fine but you will not extend it as easily.

5. Your volume is genuinely tiny and likely to stay that way

Self-hosted email infrastructure breaks even against SaaS alternatives at roughly 100K-200K emails/month. Below that threshold, the operational overhead of running any self-hosted platform — Interspire, MailWizz, Acelle, or Mautic — costs more in operator time than SaaS pricing costs in dollars. If you genuinely send 5K-50K/month and your business model does not depend on volume growth, stay on Brevo, Mailchimp, or similar hosted SaaS. The Interspire perpetual-license model ($295 + $399/year + €89/month hosting = ~€1,700/year all-in) does not pay for itself at low volumes regardless of how good the platform is. Self-hosted Interspire makes sense at production scale; for testing-volume operators it is overkill.

Interspire hosting — frequently asked questions

Is Interspire still worth running in 2026?

Yes. Interspire Email Marketer is in active development as of 2026 — version 8.7.3 was released February 2026 with new automation triggers, Large System Mode for millions of contacts, IPv6 support, and Cloudflare Turnstile integration. Four major releases shipped in 2025-2026 (v8.7.0 through v8.7.3). PHP 8.2/8.3 support has been mature since v8.5.0; PHP 8.4 readiness is currently in progress. The "Interspire is dead" narrative you may have read in 2020-2022 articles is outdated. For long-time operators with customised installs, the platform is more viable in 2026 than it was three years ago.

Do you support older Interspire versions (6.1.x and earlier)?

Yes, within reason. We keep legacy versions secure by isolating them behind a hardened proxy layer and modern PHP-FPM, and we back-port security patches when upstream no longer ships them. We do encourage moving to a supported version (8.5+) when possible because the official upgrade path now handles PHP 8.x cleanly — we handle the upgrade if you want.

Will Interspire deliver as well as MailWizz or Acelle?

The platform itself does not decide deliverability — the MTA and authentication do. On our PowerMTA back-end, your Interspire campaigns hit the same inbox placement as our MailWizz or Acelle clients with equivalent list quality. Interspire 8.7.x has improved bounce categorization for better RFC and Google compliance, which actually helps deliverability tracking accuracy.

Can you migrate my Interspire install from another provider?

Yes. We take a database dump plus the filesystem, restore on our infrastructure, reconfigure the MTA, set up new DNS records and help you verify everything before pointing traffic. Most migrations complete in 48 to 72 hours. We have done dozens of these migrations from generic shared hosting, cPanel/Plesk environments, and aging dedicated servers.

What if I want to eventually move away from Interspire?

We can help you map Interspire lists and templates to MailWizz or Acelle when you are ready. Parallel-run both platforms for a month during the transition so you do not lose any historical data. Given Interspire is in active 2026 development, we are increasingly seeing operators decide to stay rather than migrate; the calculus is different than it was in 2020.

What versions of PHP and MySQL does Interspire 8.7.x support?

Interspire 8.5.0+ supports PHP 8.2 and 8.3. PHP 8.4 readiness is being delivered across v8.7.0 through v8.7.2 with deprecation warnings addressed; full PHP 8.4 support is expected in v8.7.4 or 8.8.0. MySQL 8.0 has been supported since v8.3.0. Our managed Interspire deployments default to PHP 8.3 + MySQL 8.0 on AlmaLinux 9 for the modern-versions scenario; we can also operate older PHP 7.4 environments behind hardened proxy for legacy installs that are not yet upgraded.

How much does Interspire actually cost in 2026? (license + maintenance + hosting)

Interspire uses a perpetual software license model. The license is purchased per-domain through Interspire directly; standard pricing is $295 one-time for the regular license. The maintenance contract is sold separately and provides access to new releases (currently $399/year for standard maintenance). Our managed hosting starts at €89/month for the Starter tier. Total cost for a new Interspire deployment year-1: $295 license + $399 maintenance + €1,068 hosting (12 × €89) = approximately €1,700/year all-in for low-volume; comparable to MailWizz or Acelle at the same volume tier.

Can Interspire compete with newer platforms on automation features?

As of v8.7.3 (February 2026) yes, in many areas. The release added new trigger types — Autoresponder Opened triggers, segment subscription triggers, list owner notification emails, advanced multi-condition automations — that previously required third-party addons. The Advanced Triggers addon from IEM Addons was discontinued because the functionality is now native. Interspire automation is now competitive with Mautic and ahead of basic MailWizz in workflow sophistication; it still lags Mautic on the most sophisticated multi-channel automation scenarios.

What is Large System Mode and do I need it?

Large System Mode is a feature added in Interspire 8.7.3 that optimizes performance for installations managing millions of contacts — on-demand segment calculation, batched statistics, optimized SQL queries. If your subscriber base is under 500K contacts you do not need it; if you are above 1M it is essentially required for reasonable UI responsiveness. We enable it by default on Growth and Scale tier deployments because most clients in those tiers cross the 500K threshold within their first year.

How does Interspire compare to MailWizz and Acelle in 2026?

Interspire (Yii 1.x base, PHP 8.2/8.3, perpetual license $295 + $399/yr maintenance) is mature and feature-stable; MailWizz (Yii 1.x, PHP 7.4-8.x, $79-$249 perpetual license) has the largest extension ecosystem; Acelle (Laravel 12, PHP 8.2+, $64-$199 perpetual license) is the most modern codebase and best multi-tenant SaaS architecture. Choose Interspire when you have years of customizations to preserve or your team knows it well; MailWizz when you need extensions ecosystem; Acelle when building multi-tenant SaaS or your team is Laravel-shop.

Let's modernise your Interspire stack without throwing it away.

Request a migration quote Chat on WhatsApp