Sending email from your own custom domain
Send from your own domain (e.g. [email protected]) with a few DNS records — rolling out now. Where it isn't enabled yet, a Resend or SendGrid integration covers you.
Every OverSkill app can already send transactional email out of the box — no setup required. And if you want that email to come from your own domain (like [email protected] instead of the shared OverSkill sender), that's now built in and rolling out across workspaces. Here's how it works, and what to use if it hasn't reached your workspace yet.
What works today, for everyone
Every app sends transactional email — signup confirmations, order receipts, notifications, weekly summaries — from a shared OverSkill sender address right out of the box. No account to create, no setup, capped at 100 emails/day per workspace. See Sending emails from your app.
Sending from your own domain
When custom-domain sending is enabled on your workspace, the setup lives in the editor's Email tab:
- Connect a custom domain to your app (if you haven't already).
- Open the Email tab and click Set up email for yourdomain.com.
- Add the DNS records it shows at your DNS host — a few CNAME records that let your domain sign its own email (DKIM), plus bounce-handling records. If your DNS provider is supported, the Set up automatically button adds them in one click.
- Click Check again once the records propagate (usually minutes). When the status flips to Verified, your app sends from
[email protected]on its next deploy.
What you get:
- Your own sending identity — email is signed by your domain, which means better inbox placement and recipients seeing your brand, not ours.
- No shared daily cap — instead of the shared sender's 100/day, your limit follows the sender trust ladder and grows automatically with healthy sending. See Understanding your email sending limits.
- Credit-metered sends — custom-domain sends cost 0.1 credits per email (1 credit per 10 emails).
The Email tab also recommends a DMARC record once you're verified — it's optional, but it improves deliverability and stops others spoofing your domain. Add the suggested TXT record whenever you're ready.
If your workspace doesn't show the setup yet
Custom-domain sending is rolling out gradually. If your Email tab doesn't offer the setup yet and you need your own from-address today, connect an email-sending integration instead — Resend, SendGrid, Postmark, MailerSend, or SMTP2Go. In chat, just ask:
Connect Resend and send order confirmations from [email protected].
The AI walks you through connecting the integration and wires up the sending logic. You'll verify your domain with that provider (a few DNS records at your registrar) and have full control of the from-address.
This is also the right path if you need marketing or bulk email — OverSkill's built-in sending (shared or custom-domain) is for transactional email only.
Which one should I use?
- Just need transactional email fast, don't care about the sending domain? Use the built-in shared sender — nothing to connect.
- Want your own domain and your Email tab offers the setup? Use it — DNS records once, then limits grow automatically.
- Need your own domain but the setup isn't on your workspace yet? Connect Resend, SendGrid, Postmark, MailerSend, or SMTP2Go.
- Sending marketing/bulk email? Use one of those integrations, not the built-in sender.
What to read next
- Sending emails from your app — the built-in shared sender and its limits
- Understanding your email sending limits — how limits grow with healthy sending
- Why was my email sending paused or throttled?
- Browsing the integrations marketplace — how to connect Resend, SendGrid, and others
- Connecting your own domain — for your app's web address (separate from email sending)
- Connecting Mailjet or any other email provider not in the marketplace — using Mailjet, Postmark, or another provider that isn't pre-built yet