Short answer
A dedicated server should be a step you take on the same API when your volume or your security review calls for it, not a migration you plan for months. Most teams do not need one on day one. The teams that do usually know it because someone in procurement asked who else sends from their IPs, or because their sign-in codes now carry enough volume that sharing a reputation with strangers feels like a risk they cannot explain away.
This page covers what a dedicated server isolates, how it differs from a shared pool and dedicated IPs, when it is the wrong purchase, what reviewers will ask, and what the first week looks like.
On this page
- Short answer
- What a dedicated server isolates
- When a dedicated server is the move, and when it is not
- Same API, no code changes when you move up
- A first week moving resets and receipts onto isolated sending
- Answers for security and procurement reviews
- Why we can isolate your mail: we run the servers and IP space
- Transactional mail only, at any price
- What $299/mo covers
- How setup works with our team
- Start on Free, move to dedicated when you need it
- FAQ
What a dedicated server isolates
Every email you send is judged by mailbox providers on two things: your domain and the IP address it left from. On a shared pool, the IP reputation is pooled across every sender on it. On dedicated IPs, the addresses are yours but the mail server software, queues and configuration behind them are still shared. On a dedicated server, the machine that hands your mail to Gmail, Outlook and Yahoo runs only your mail.
| Shared pool | Dedicated IPs | Dedicated server | |
|---|---|---|---|
| IP reputation | Pooled with other senders | Yours alone | Yours alone |
| Mail server and queues | Shared | Shared | Yours alone |
| Who affects your inbox placement | You and the pool's other senders | You | You |
| What a reviewer has to trust | The provider's policy on who shares the pool | The provider's IP assignment | The provider's operation of one isolated server |
| Fits when | You are starting out or sending modest, steady volume | You have the volume to keep your own IPs warm | A security or procurement review asks for isolated sending, or your mail is critical enough to justify it |
Our guide to shared vs dedicated IPs goes deeper on the IP half of that choice.
When a dedicated server is the move, and when it is not
It is the move when:
- A security or procurement review asks who handles your sign-in and receipt mail and whether it shares infrastructure with other companies.
- Your transactional volume is steady and large enough that your own reputation is worth more to you than a pooled one.
- A delayed password reset or two-factor code turns into a support ticket or a lost customer, and you want no other sender's behavior in that path.
It is not the move when:
- You send a few thousand emails a month. A dedicated IP with little traffic gives mailbox providers little data to judge, and a clean shared pool usually serves you better.
- You hope isolation will fix a bounce problem. If your bounce or complaint rate is high, a dedicated server makes that rate entirely yours. Mailbox providers still see it. Clean the list, suppress hard bounces automatically, and confirm addresses at signup first.
- You want to send newsletters or cold outreach from it. Those belong on a separate service built for marketing mail.
Same API, no code changes when you move up
The point of isolation as a setting is that your application does not know or care which tier it is on. A send looks like this:
curl
curl -X POST https://api.groundmail.dev/emails \
-H "Authorization: Bearer $GROUNDMAIL_API_KEY" \
-H "Idempotency-Key: reset-8841" \
-H "Content-Type: application/json" \
-d '{
"from": "security@yourdomain.com",
"to": "ada@example.com",
"subject": "Reset your password",
"html": "<p>Use this link to reset your password.</p>"
}'That call is the same on the shared pool, on dedicated IPs and on a dedicated server. The developer docs overview lists the rest of what stays constant: SDKs for Node, Python, Go, PHP and Ruby, batch sends of up to 100 emails, idempotency keys kept for 24 hours, and signed webhooks for every delivery, bounce and complaint. Your bounce handling, your templates and your webhook consumers do not change when the infrastructure underneath them does.
A first week moving resets and receipts onto isolated sending
Day 1: separate your streams. List every email your product sends. Keep password resets, sign-in codes, receipts and alerts. Move anything promotional to a different service.
Day 2: authenticate the domain. Publish SPF, DKIM and DMARC for the sending domain, starting DMARC at a monitoring policy so you can see who sends as you before you enforce.
Day 3: test failure paths. Use a test key to run sends that deliver nothing, and send to simulator addresses that return a hard bounce, a block or a complaint. Confirm your webhook consumer suppresses those recipients.
Day 4: scope your keys. Issue a send-only key for production, restricted to the domains it may send from, so a leaked key cannot send as your other brands.
Day 5 onward: shift traffic gradually. Move a slice of real transactional traffic, watch bounces and complaints, then increase. Our walkthrough on switching providers without downtime covers running two providers in parallel during the change.
Answers for security and procurement reviews
Reviewers ask the same questions about transactional mail every time. Have answers ready for:
- Who operates the servers that send our mail? One named company, or a chain of infrastructure vendors behind the one you are buying from?
- Who else sends from our IPs and servers? With a dedicated server the answer should be nobody.
- Who can send as our domain? Scoped API keys and domain-restricted keys narrow this to specific services and domains.
- Can we get our data out? Export of sent mail, received mail and suppressions matters for audits and for leaving.
The first question is the one a dedicated server answers best, but only if the provider runs the server itself. A dedicated server rented from someone else's cloud and resold still leaves the reviewer with a second party to assess.
Why we can isolate your mail: we run the servers and IP space
Groundmail sends from mail servers and IP space we own and operate. That is what makes a dedicated server something we can build for you rather than resell. When a reset lands in spam, the team reading the logs is the team that can change the IPs and the server configuration.
The shared pool works on the same principle. Marketing and cold email are not allowed on our IPs, so every sender on the pool sends the same kind of mail a user is waiting on.
Transactional mail only, at any price
That rule does not change on the Dedicated plan. A dedicated server is for resets, sign-in codes, receipts and alerts. Keeping marketing off the server keeps its reputation tied to mail recipients expect, which is what you are paying to protect.
What $299/mo covers
The Dedicated plan starts at $299 a month and gives you your own server and IPs, built, warmed and managed by our team, with 250,000 emails included and $0.80 per 1,000 after that. The full plan list is on the pricing page.
| Plan | Price | Included | After the included volume |
|---|---|---|---|
| Free | $0/mo | 3,000 emails a month, 100 a day, 1 domain | |
| Pro | $20/mo | 50,000 emails, 10 domains | $0.90 per 1,000 |
| Scale | $90/mo | 100,000 emails, tiers up to 2.5M | Down to $0.46 per 1,000 |
| Dedicated | From $299/mo | 250,000 emails, own server and IPs | $0.80 per 1,000 |
What the Dedicated plan costs at common volumes, from those rates:
| Emails per month | Dedicated plan cost |
|---|---|
| 250,000 | $299 |
| 500,000 | $499 ($299 + 250 × $0.80) |
| 1,000,000 | $899 ($299 + 750 × $0.80) |
How setup works with our team
You do not build or warm the server yourself. Our team sets up the server and IPs, warms them, and runs them. Your side is the work in the first-week plan above: authenticate the domain, test your bounce handling, scope your keys, and keep sending the way you already do through the API or SMTP relay. The dedicated IPs and servers page describes the options.
Start on Free, move to dedicated when you need it
You do not need the dedicated server to begin. Start on the Free plan or Pro, wire up the API, and build your bounce handling against test keys. When volume or a review calls for isolation, move to dedicated IPs or a dedicated server on the same integration. If you want to start that way, you can create your free Groundmail account and send your first email today.
Frequently asked questions
Do I need a dedicated server at 100,000 emails a month?
Not because of volume alone. At that level a clean, transactional-only shared pool is often enough. A dedicated server earns its price when a review requires isolation or when your mail is critical enough that you want no other sender in its path.
Will a dedicated server get my emails out of spam?
Only if the cause was someone else's reputation. If the cause is your own bounces, complaints or missing authentication, isolation exposes it more clearly. Fix those first.
Do I have to change my code to move to a dedicated server?
No. The same API calls, SDKs, SMTP settings and webhooks work on every tier.
Can I send newsletters from a dedicated server?
No. Groundmail only sends transactional mail, on the shared pool and on dedicated infrastructure alike.
Who warms the IPs?
Our team builds, warms and manages the dedicated server and its IPs.
What does it cost above 250,000 emails?
$0.80 per 1,000 emails on top of the $299 monthly base.