This guide was technically verified and updated on January 23, 2026.
GreenArrow General SMTP settings (quick reference)
- SMTP host:
smtp.yourdomain.com(or another hostname pointing to your GreenArrow Engine server) - Ports: 25, 465, 587 (plus any custom ports you configure)
- Encryption: STARTTLS or TLS, depending on listener configuration
- Username: SMTP/API user you create in GreenArrow (per app, per tenant, etc.)
- Password: Password or API key tied to that user
- Auth: Authentication required (never run it as an open relay)
GreenArrow licensing & pricing (at a glance)
- Product: GreenArrow Engine, high‑performance MTA / SMTP/API delivery engine for high‑volume senders
- Deployment: Cloud plan and On‑Premises (Engine OnPrem Edition)
- Pricing model (public ballpark):
- Cloud plan: from around 250 USD/month
- Standard On‑Prem: around 600 USD/month or 6,000 USD perpetual license
- Pro On‑Prem: around 800 USD/month or 9,000 USD perpetual
- Enterprise On‑Prem: custom pricing for highest volumes
- Ecosystem: Vendor support, docs, plus third‑party optimization and deliverability partners
GreenArrow Engine is a high‑performance Mail Transfer Agent and SMTP/API engine designed for high‑volume senders who want enterprise‑grade deliverability features with flexible integration options. It sits between your apps and the mailbox providers, handling queues, throttling, IP pools, and detailed reporting so you can build your own sending stack on top.
What Is GreenArrow Engine?
GreenArrow Engine is an MTA‑centric email delivery platform available as both On‑Premises software and a cloud service. It’s built to process millions of messages per hour, with support for multiple injection methods (SMTP, APIs, web UI) and advanced control over IPs, domains, and delivery policies.
At the core, GreenArrow Engine focuses on performance, deliverability and observability rather than “full ESP” features like CRM. You can run it as your main backbone for transactional and marketing email, and pair it with marketing/CRM tools or your own front‑end to deliver a complete solution.
Who Should (and Shouldn’t) Use GreenArrow?
GreenArrow is aimed at teams who want more control than Amazon SES/SendGrid, but don’t necessarily want to hand‑roll everything like raw Postfix/Exim. It’s particularly attractive if you want a commercial MTA with strong support and a clear pricing model, plus options to run on‑prem.
Ideal GreenArrow user profiles
| Use case | Why GreenArrow fits |
|---|---|
| ESPs / email platforms | Enterprise‑grade MTA with queues, throttling, and IP/domain‑level controls. |
| High‑volume SaaS / apps | Consistent throughput, detailed reporting, and integration via SMTP/API. |
| Agencies & service firms | Multi‑client sending with separation, using one Engine cluster behind the scenes. |
| Cost‑conscious volume senders | Clear per‑month or perpetual pricing, potentially big savings vs pure SaaS ESPs. |
When GreenArrow is not a great fit
- Very small senders who can live happily on a simple ESP UI and never touch infra.
- Teams with no appetite for server management or for learning MTA concepts (especially On‑Prem).
- Use cases where a full “all‑in‑one” ESP (forms, CRM, landing pages) is more important than infra control.
Prerequisites Before Deploying GreenArrow
Before you jump into Engine On‑Prem or a serious cloud deployment, line up the basics.
Technical prerequisites
- Stable domain(s) and DNS access to configure SPF, DKIM, DMARC, bounce and tracking domains.
- Clean IP addresses (or ranges) for On‑Prem with proper reverse DNS and non‑toxic reputation.
- Linux servers or VMs sized to match throughput targets, plus firewall and OS hardening.
- Monitoring stack capable of ingesting GreenArrow logs and metrics (or using their built‑in dashboards as a base).
Business & list prerequisites
- Clear traffic mix: transactional, marketing, cold outreach (if at all), multi‑tenant etc.
- Reasonable volume expectations (e.g. 100k/hour, 1M+/day) to choose between cloud vs On‑Prem tiers.
- Permission‑based lists and a process for handling bounces, complaints, and unsubscribes in your stack.
How GreenArrow Licensing Works
GreenArrow Engine has one of the more transparent public pricing pages among commercial MTAs.
Core licensing concepts
- Cloud plan: hosted by GreenArrow; priced from around 250 USD/month depending on volume/features.
- On‑Premises Engine: you license the software and run it on your own hardware or cloud, with monthly lease or perpetual options.
- Tiers: Standard, Pro, and Enterprise editions for On‑Prem with different capacities and features.
- Support: commercial support and updates tied to your plan; higher tiers for high‑touch enterprise deployments.
Add‑ons & extras
- Optional add‑ons and custom features for On‑Prem (in higher tiers or as custom quotes).
- Consulting and “email infrastructure setup” offers from partners for large senders.
GreenArrow Pricing Examples (Public Ballpark)
Public listings give you rough anchors for budgets.
Baseline cost structure
| Component | What it covers | Notes |
|---|---|---|
| Cloud Plan | Hosted SMTP/API email delivery. | Starts around 250 USD/month. |
| Standard On‑Prem | MTA Engine license, ~100k/hour tier. | Around 600 USD/month or 6,000 USD perpetual. |
| Pro On‑Prem | Higher volume + more features. | Around 800 USD/month or 9,000 USD perpetual. |
| Enterprise On‑Prem | Custom high‑volume deployments. | Custom pricing. |
Total cost of ownership (TCO)
| Factor | What to consider | Impact |
|---|---|---|
| Infra & ops | Servers/VMs, storage, bandwidth, ops time. | Higher for On‑Prem; lower for cloud. |
| Deliverability work | Monitoring, configs, warm‑up, remediation. | Required for serious senders either way. |
| Build vs buy | Engine vs full ESP vs raw Postfix/Exim. | GreenArrow is the “middle ground” option. |
Key GreenArrow Engine Features and Limits
GreenArrow Engine gives you many of the “PowerMTA‑class” controls with a slightly more productized feel.
Core features
- High‑performance MTA that can handle millions of messages per hour on proper hardware.
- Multiple injection methods: SMTP, API, and UI integrations depending on edition.
- IP pool and domain management with fine‑grained throttling rules per IP and per domain.
- Cooperative / cluster throttling to coordinate limits across multiple nodes.
- Real‑time and historical reporting: delivery, bounces, engagement, suppression, and more.
Operational limits & considerations
- Throughput depends on your hardware and tuning: scaling from 100k/hour to much higher involves more nodes and IPs.
- Self‑hosted On‑Prem typically requires at least one dedicated engineer for serious deployments.
- Complexity grows with the number of brands/tenants and regions you serve in one cluster.
Common GreenArrow Use Cases
GreenArrow is flexible enough to cover transactional, marketing, and multi‑tenant scenarios.
Transactional email use cases
- SaaS events: signups, login links, password resets, billing notifications.
- Product and system alerts: usage thresholds, security alerts, uptime status.
Marketing & lifecycle email use cases
- Newsletters and promotional campaigns at high volume, triggered from your own UI or integrated tools.
- Onboarding and lifecycle flows driven by CRM or app events, injected via API or SMTP.
Agency and multi‑tenant use cases
- Centralized infrastructure sending on behalf of multiple brands with separate domains and IPs.
- Ability to tune policies and throttling per client or per vertical.
Step‑by‑Step: Typical GreenArrow Deployment Flow
Step 1, Choose cloud vs On‑Prem
- Cloud: fastest start, less infra work, good if you don’t want to manage servers.
- On‑Prem: more control and often better unit cost at scale, but requires devops and infra management.
Step 2, Prepare infrastructure & DNS
- For On‑Prem, provision and harden Linux servers/VMs and ensure IP and DNS (SPF/DKIM/DMARC, rDNS) are in place.
- Plan IP pools and subdomains to separate transactional vs marketing traffic and per‑client sending.
Step 3, Install and configure GreenArrow Engine
- Install Engine On‑Prem following vendor docs and configure listeners, queues, and injection methods.
- Set up throttle templates, IP pool mappings, and domain‑specific rules.
Step 4, Integrate your applications
- Connect your apps, ESP front‑end, or CRM to GreenArrow via SMTP or API using appropriate credentials.
- Feed GreenArrow reports/logs into your suppression logic and analytics dashboards.
Step 5, Warm up and optimize
- Warm up IPs and domains gradually while monitoring per‑ISP metrics and errors.
- Adjust throttling and connection limits as you learn how each mailbox provider responds.
Deliverability & Compliance Best Practices on GreenArrow
GreenArrow gives you the tools; your policies and lists decide the outcome.
Authentication & reputation
- Configure SPF, DKIM, and DMARC correctly for all sending domains and subdomains.
- Separate high‑value transactional from bulk/marketing traffic with different IP pools and potentially different subdomains.
- Use cooperative throttling and per‑domain rules to avoid bursts that trigger filters.
Handling bounces, complaints and unsubscribes
- Use Engine’s reporting to categorize bounces, and pipe them into your suppression system quickly.
- Respect feedback loop complaints and unsubscribe requests to keep complaint rates low.
- Avoid non‑permission‑based lists; cold mail is especially risky at scale even with a strong MTA.
Integrating GreenArrow: SMTP, API and Application Layer
GreenArrow can act both as a classic SMTP relay and as an SMTP/API email delivery backend.
Integration overview
- SMTP: apps connect with host, port, username/password; GreenArrow handles queues, retries, throttling.
- API: programmatic injection, IP management, and throttling rule management (for advanced integrations).
- UI / reports: use GreenArrow’s own interface plus external dashboards for deeper analytics.
When to choose which integration
- Use SMTP if you already support SMTP relays (replacing SES/SendGrid/etc.).
- Use API for tighter control over IPs, throttling, and event ingestion into your SaaS/ESP.
Stacks and Tools That Work Well with GreenArrow
Typical self‑hosted / hybrid stack
| Tool category | Example tools | Role with GreenArrow Engine |
|---|---|---|
| Bulk email / newsletters | MailWizz, Mautic, custom UIs | Lists, templates, campaigns, schedules via SMTP/API. |
| CRM + product | SaaS apps, CRMs | Event‑driven transactional & lifecycle email. |
| BI / monitoring | ELK, ClickHouse, custom dashboards | Aggregate logs, build ISP/IP/tenant‑level views. |
Monitoring, Analytics and Scaling with GreenArrow
Monitoring & analytics
- Use Engine’s built‑in reports plus log exports for delivery, bounce and engagement tracking.
- Feed logs into ELK/Opensearch, ClickHouse or similar for per‑ISP, per‑client, and per‑IP dashboards.
- Watch key metrics: bounce rates, complaints, throttling/backoffs, queue sizes, response codes.
Scaling to higher volumes
- Scale vertically (bigger servers) and horizontally (more nodes) as you grow from 100k/hour upward.
- Use cooperative throttling so the whole cluster respects global per‑domain limits.
- Periodically review IP pool allocations and domain strategies as you add more brands or geos.
Pros, Cons and Alternatives to GreenArrow
Pros
- Clear productized offering with public pricing for Cloud and On‑Prem tiers.
- Strong focus on MTA performance, throttling, and reporting for high‑volume senders.
- Fits nicely as a “middle‑ground” between raw open‑source MTAs and pure cloud ESPs.
Cons
- On‑Prem deployments require serious engineering/deliverability resources.
- Not a full marketing suite; you still need front‑end tools for campaigns, CRM, and forms.
- There is still build vs buy complexity compared to fully managed providers.
High‑level comparison table
| Feature | GreenArrow Engine | Cloud ESP (SendGrid/SES‑style) |
|---|---|---|
| Pricing model | Cloud & On‑Prem tiers; predictable licenses. | Usage‑based (emails/contacts). |
| Control | High (MTA, IPs, throttling, routing). | Medium (provider owns infra details). |
| UI & features | Infra‑focused, some tools; not full CRM. | Rich marketing UI, templates, automations. |
| Skills required | Sysadmin + deliverability + integration work. | Mostly marketing + light dev setup. |
GreenArrow FAQ
Is GreenArrow Engine still relevant in 2026?
Yes. GreenArrow Engine continues to be marketed as a high‑performance MTA for cloud and On‑Prem, with active pricing pages, docs, and partner ecosystem in 2025-2026.
Is GreenArrow cloud‑based or self‑hosted?
Both. You can use GreenArrow’s cloud plan or run Engine On‑Prem on your own hardware or cloud servers, depending on your needs and expertise.
How much does GreenArrow cost?
Public references show cloud plans starting around 250 USD/month, Standard On‑Prem around 600 USD/month (or 6,000 USD perpetual), Pro around 800 USD/month (or 9,000 USD perpetual), and Enterprise as custom.
Do I need a full‑time engineer for GreenArrow?
For serious On‑Prem, high‑volume use, yes-at least one engineer with MTA/deliverability skills is recommended to manage infra, scaling, and configs. Cloud use can be lighter on engineering but still benefits from deliverability expertise.
How does GreenArrow compare to PowerMTA or Postfix?
GreenArrow and PowerMTA both target high‑volume commercial MTA use cases, while Postfix/Exim are general‑purpose open‑source MTAs that require more custom work to match their deliverability tooling. GreenArrow positions itself as an enterprise MTA with vendor support and clear packaging rather than a DIY solution.
About the Author
Alaa · LinkedIn
Email infrastructure specialist with 8+ years of hands-on experience in SMTP, deliverability, and email verification. I’ve configured and troubleshot mail systems across Postfix, Exchange, and cloud relays, managed IP reputation and warmup campaigns, and built verification pipelines processing millions of addresses. My work spans DNS authentication (SPF, DKIM, DMARC, BIMI), bounce handling, blocklist monitoring, and compliance frameworks including CAN-SPAM and GDPR. I write every article on SMTPedia to give email professionals, developers, and marketers the accurate, RFC-grounded reference they need.
About SMTPedia
SMTPedia is an independent email industry reference covering SMTP, IMAP, POP3, email deliverability, marketing platforms, DNS authentication, and email verification. Every article is researched from official provider documentation, IETF RFCs, and industry best practices. Settings and configurations are verified quarterly.
We are cited as a source by ChatGPT, Microsoft Copilot, and thousands of email professionals worldwide. Learn more about our editorial process.
