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.
Platform online — connect Resend to enable delivery
FCMailX — centralized transactional email for founders running multiple apps
FCMailX gives you one place to verify sending domains, issue per-app SMTP and API credentials, and review send logs across your product portfolio. Delivery runs through Resend when configured — you keep control of DNS and credentials on your VPS.
0
Verified domains
Add a domain in Setup Hub
0
Connected apps
Connect your first application
0
Logged sends
Run a deliverability test to start
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, generate per-application credentials, and run deliverability checks before you route live traffic.
Outbound delivery is handled through Resend when you connect an API key. FCMailX does not replace your DNS provider or your application code; it centralizes configuration, logging, and credential management so you are not rebuilding email plumbing for every new product.
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.
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 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
Provision standard sender addresses
Optional email kit creates common local parts (noreply, support, billing) tied to your verified domain.
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 FCMailX is not
- Not a marketing automation or newsletter platform like Mailchimp.
- Not a replacement for owning your DNS records — you still add SPF, DKIM, and DMARC at your registrar or DNS host.
- Not a guaranteed inbox placement service; deliverability depends on your domain reputation, content, and list hygiene.
- Inbound mailboxes and IMAP are a separate phase (Mailcow integration) and are only available when that integration is configured on your instance.
Pricing
Plans are billed monthly. Trial length is shown on each plan — start in the Setup Hub before subscribing.
Starter
$29/month
Core email platform for one SaaS product
14-day trial · cancel anytime
Get startedFrequently 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.
Do I need Resend?
Yes, for outbound delivery on the current release. You add your Resend API key to the platform environment. FCMailX manages how your apps connect and log sends; Resend carries the messages.
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.
Start with the Setup Hub
Add a sending domain, connect your first application, and confirm deliverability before you route production traffic.
Open Setup Hub