COMPARISON
MailKaka vs Resend
Both platforms use the same familiar send-email API shape, so switching is usually a one-line change. This page covers what's actually different if you're sending from -- or to -- India.
| MailKaka | Resend | |
|---|---|---|
| Sending region | Mumbai, India (AWS ap-south-1) | North Virginia (US), Ireland, São Paulo, or Tokyo -- no India region |
| Where account data/logs live | India | United States, regardless of which sending region you pick |
| Billing currency | INR via Razorpay, GST invoicing | USD only |
| Free tier | 3,000 emails/month, no fixed daily cap | 3,000 emails/month, capped at 100/day |
| Replies | Land in a real shared team mailbox | Outbound only -- no inbound/reply mailbox |
| Compliance framing | DPDP Act-mapped privacy policy, India data-processor language | GDPR-oriented (US-headquartered company) |
Resend figures reflect resend.com/pricing and resend.com/docs as of August 2026 -- always confirm current details on their site before deciding, since pricing pages change.
WHY TEAMS SWITCH
Four things that actually matter.
Data stays in India. Even if you pick Resend's nearest region (Tokyo), your account metadata, logs, and API records are still stored in the US. If your DPDP Act compliance work assumes Indian data residency, that's worth knowing before you build on it.
No forex, no GST guesswork. Resend bills in USD. MailKaka bills in INR through Razorpay with GST-compliant invoicing -- one less currency-conversion line item for Indian finance teams.
Free tier isn't throttled by the clock. Resend's free tier caps you at 100 emails a day even though the monthly quota is 3,000 -- burst traffic (a launch day, a marketing push) can hit that wall well before the month's allowance is used. MailKaka's free tier has no fixed daily cap.
Replies don't disappear. Resend is a send-only API -- if a customer hits reply on a transactional email, there's no built-in inbox behind it. Every MailKaka domain gets a real shared mailbox by default, so replies land where your team can see them.
MIGRATING
Switching from Resend.
If you're already using Resend's Node SDK, most single-message integrations migrate with one line:
new Resend(MAILKAKA_API_KEY, { baseURL: "https://www.mailkaka.in/api" })Raw HTTP/cURL callers just change the host and bearer token. to/cc/bcc arrays work the same way. Full reference: docs.md migration prompt.
FAQ
Is MailKaka a drop-in replacement for Resend?
For the core single-message and batch send API, yes. Some advanced Resend-specific products and endpoints are outside MailKaka's current scope -- check the docs for exact coverage before migrating a large integration.
What happens to emails Resend already sent?
Nothing -- this only affects new sends going forward. There's no data to migrate; you're just pointing new API calls at a different base URL.