Platform operational

One email setup. Every app you ship.

You already know how to wire up Resend for one product. FCMailX is for the founder who's done that three times this year and is tired of it — verify a domain once, connect every app, see every send from one dashboard.

  • No per-email pricing creep as you add products
  • No re-verifying domains for every new launch
  • Runs on your own VPS — you own the data

Not for you if you're running one app with simple needs — Resend's free tier is genuinely the better call there.

5
Verified domains
Verified on this instance
6
Connected apps
Active SaaS connections
5
Logged sends
Logged sends on this instance

What FCMailX is

FCMailX is a self-hosted email control plane that runs on your own VPS (for example via Coolify). It is built for transactional email — password resets, verification messages, billing receipts, and product notifications — not bulk marketing campaigns.

The platform provides a guided Setup Hub where you add a sending domain, copy DNS records for SPF, DKIM, and DMARC, provision an admin@ unified inbox plus standard app mailboxes, generate per-application credentials, and run deliverability checks before you route live traffic.

Outbound delivery uses self-hosted SMTP on your server by default. Optional Resend relay is available in Settings. FCMailX centralizes configuration, logging, and credential management so you are not rebuilding email plumbing for every new product.

One admin@ inbox per domain

Every verified domain gets a unified webmail inbox. Log in once as admin@yourdomain.com and read inbound mail for your full email kit — without opening separate SOGo sessions for hello, support, billing, or noreply.

New · Email Kit Step 3

admin@yourdomain.com

Your single webmail login for every kit mailbox on that domain.

  • Auto-created in Setup Hub Step 3 alongside your standard email kit.
  • Inbound mail to kit addresses is copied to admin@ via Mailcow — originals still land in each app mailbox for SMTP identity.
  • Reply from admin@ using Send as in SOGo when you need to answer as support@ or hello@.
  • Each domain in your portfolio gets its own admin@ — fcmailx.com, wasup.app, and every brand you add.
Provision admin@ in Setup Hub

Who FCMailX is for

FCMailX is aimed at founders and small teams operating two or more software products — for example a main SaaS app, a WordPress site, and a side project — who want one dashboard instead of separate Resend projects and SMTP configs per app.

It fits stacks already deployed on a VPS or Coolify where you can set environment variables and point SMTP or HTTP calls at a single platform URL.

If you run a single app with simple email needs and no plans to add products, a direct Resend integration may be enough. FCMailX earns its place when duplication and scattered logs start costing you time on every launch.

Why centralize transactional email

These problems compound when you add a second or third product to the same VPS or brand family.

Repeated DNS and credential work

Each new app means another round of domain verification, API keys, and SMTP users — easy to misconfigure and hard to audit later.

Too many webmail logins

Each kit mailbox (hello, support, billing) used to mean another SOGo password. FCMailX provisions admin@ per domain so you read all inbound kit mail from one inbox.

No fleet-wide send visibility

When a user says they did not receive an email, you may need to check multiple apps and providers instead of one send log.

Launch-day deliverability risk

Missing or incorrect SPF, DKIM, or DMARC records often surface only after users report messages in spam.

How FCMailX works

The Setup Hub follows the same six steps you see in the admin panel — no separate onboarding flow.

Step 1

Add your sending domain

Enter the domain you send from (for example mail.yourbrand.com or your apex domain). FCMailX stores the domain and prepares verification checks.

Step 2

Copy DNS and verify

The Setup Hub shows the TXT and CNAME records you need at your DNS host. After propagation, run verification from the same screen.

Step 3

Email kit + admin@ inbox

Creates admin@yourdomain.com — one webmail login for all inbound kit mail — plus noreply, hello, support, and billing for app sending.

Step 4

Connect a SaaS application

Choose a preset (RealLead, WordPress, or custom) and copy the generated .env block into that app's environment.

Step 5

Run a deliverability test

Send a test message to Gmail or Outlook inboxes and confirm it lands before you switch production traffic.

Step 6

Monitor from the dashboard

Review send logs, connected products, and domain status from the admin dashboard as your portfolio grows.

What you can connect

Each application gets its own credentials while sharing verified domains and centralized logging.

SMTP submission

Use generated SMTP credentials with WordPress, nodemailer, Laravel, Django, or any client that supports SMTP on port 587.

HTTP API

Call POST /v1/send (or /v1/send-email) with a per-app API key. Same delivery path as SMTP — choose what fits each codebase.

Setup Hub presets

Presets format environment variables for common stacks so you paste once into Coolify or your host panel rather than hand-assembling keys.

What you get on day one

Self-hosted SMTP delivers the messages. FCMailX is the control plane on your VPS — one Setup Hub, one admin inbox per domain, and one send log across every app you connect.

admin@ unified inbox

Setup Hub Step 3 provisions admin@ on each domain. One SOGo login reads inbound mail for hello, support, billing, and noreply — apps still send from their own addresses.

Guided Setup Hub

Add a domain, copy DNS records, connect an app, and run a deliverability test — the same six steps in the admin panel, not a separate onboarding tool.

Per-app SMTP and API credentials

Each SaaS product gets its own keys without spinning up a separate Resend project or hand-building env vars for every launch.

Fleet-wide send logs

When someone says they did not get an email, check one log filtered by app, domain, or status instead of hunting across multiple dashboards.

Deliverability checks before go-live

Run inbox tests to Gmail and Outlook and review domain health factors on the dashboard before you route production traffic.

Credential and connection management

Presets for RealLead, WordPress, and custom stacks output ready-to-paste .env blocks for Coolify or your host panel.

What stays on your side

Clear boundaries so you know exactly what FCMailX handles and what you still manage.

  • Newsletters and drip campaigns — FCMailX is for app-triggered transactional mail (resets, verifications, receipts), not Mailchimp-style marketing lists.
  • DNS hosting — we show the SPF, DKIM, and DMARC records to add at Hostinger or your DNS provider; you publish them, we verify them.
  • Inbox guarantees — we guide setup and test placement, but reputation, content, and sending patterns still determine where mail lands.
  • Optional Resend relay — default outbound is self-hosted SMTP; you can enable Resend in Settings if you prefer a paid relay.
  • Domain inbox — admin@ on each verified domain (e.g. admin@fcmailx.com) is your single webmail login; kit mailboxes stay for app SMTP sending.

Pricing

Priced by verified domains — not per email. Each domain includes a free admin@ inbox and unlimited apps. Fair-use volume on self-hosted SMTP may apply for extreme outliers.

Starter
$29/month

1 verified domain (admin@ included). Self-hosted SMTP + API, no per-email fee. 30-day send log retention. One-time deliverability test. Extra domains +$12/mo.

  • 1 verified domain (admin@ included)
  • Unlimited apps per domain
  • Self-hosted SMTP + API — no per-email fee
  • 30-day send log retention
  • One-time deliverability test (Setup Hub)
  • Extra verified domain $12/mo each
  • Fair-use volume on self-hosted SMTP

14-day trial · cancel anytime

Get started

Frequently asked questions

What is FCMailX used for?

FCMailX centralizes transactional email setup for multiple applications: domain verification, per-app SMTP and API credentials, send logging, and deliverability testing from one admin panel on your VPS.

How does domain-based pricing work?

Starter ($29/mo) includes 1 verified domain; Growth ($99/mo) includes 5. Each verified domain gets a free admin@ inbox and unlimited apps. Extra domains are +$12/mo on Starter and +$8/mo on Growth. There is no per-email send fee — fair-use volume caps may apply for extreme outliers on self-hosted SMTP.

What happens if I try to verify more domains than my plan includes?

Verification is blocked with a clear upgrade or add-on prompt. Existing verified domains stay fully usable — we never silently fail or revoke a domain you already run.

Do I need Resend?

No. Default outbound uses self-hosted SMTP on your VPS (smtp.fcmailx.com:587). Resend is an optional paid relay you can enable in Settings if you prefer it.

Should I use SMTP or the HTTP API?

Both reach the same pipeline. Use SMTP when an app already expects SMTP_HOST and credentials. Use the HTTP API when you prefer a single POST /v1/send call from application code.

Who can access the admin panel?

Only email addresses listed in FOUNDER_EMAILS can sign in. Admin access is intentionally restricted — there is no shared team password by default.

Where is my data stored?

Domain records, SaaS connection metadata, API key hashes, and send logs are stored in your platform database on the VPS. Message content in logs follows your retention settings; credentials are stored encrypted and secrets for sending stay in environment variables on each app.

Can I use my own domain?

Yes. You add the domain in the Setup Hub, publish the shown DNS records at your DNS provider, and verify from the admin UI. App routing uses your FCMailX hostnames; sending identity uses the domains you verify.

What happens if I change platform URLs?

Per-app API keys and SMTP passwords stay the same. Update MAIL_PLATFORM_URL, SMTP_HOST, and related env vars in each connected application to point at the new host.

Is there a free trial?

Active plans include a trial period shown on the pricing section. You can walk through the Setup Hub and connect a first app before subscribing.

Does FCMailX send marketing email?

The product is designed for transactional messages triggered by your applications. Bulk promotional campaigns are out of scope.

How do I get help?

Use the Setup Hub for guided setup, check /health for platform status, and contact support@fcmailx.com for account or billing questions.

What is the admin@ domain inbox?

During Email Kit (Setup Hub Step 3), FCMailX creates admin@ on each domain you verify. Inbound mail to your kit addresses (hello, support, billing, noreply) is copied to that one inbox so you log into SOGo once instead of managing separate passwords for every mailbox.

How does founder send and receive work?

Use admin@fcmailx.com on your platform domain — or admin@ on any domain you add in Setup Hub — as your unified SOGo login. Apps send via noreply@fcmailx.com through SMTP. Add optional inbound MX in Step 2 to receive mail from the internet.

Start with the Setup Hub

Add a sending domain, get your admin@ inbox and email kit, connect your first app, and confirm deliverability before production traffic.

Open Setup Hub