FAQ

Honest answers about where MailingCore is today and what to expect.

How mature is the product?

MailingCore is an MVP in active development — roughly 75% of the planned SaaS surface is shipped. Core flows (send, domains, templates, contacts, campaigns, webhooks, billing) work in production. Advanced features (sequences UI, A/B testing, full audit log UI) are partial or API-only.

We document what is live and label beta features explicitly.

Is there a staging environment?

Yes. Staging mirrors production architecture with separate credentials and data. Use mc_test_ keys and staging dashboard URLs for integration work before going live.

Production and staging OpenAPI specs may differ slightly; always check /docs-json on the host you target.

Is mailingcore-js on npm?

Not yet as a public npm package. The SDK source lives in the monorepo; you can copy integration patterns from Send with SDK or call the REST API directly. npm/GitHub Packages publication is on the roadmap.

Where is data stored?

MailingCore is positioned as a European email platform. Processing and storage are EU-oriented for GDPR alignment. See Data residency.

Can I send from the browser?

Technically yes with an API key, but not recommended for production. Keys in frontend bundles are extractable. Use a backend proxy or serverless route. See API key security.

What transports deliver mail?

AWS SES and SMTP are supported behind the queue worker. You verify your own domain; MailingCore signs with your DKIM keys.

How do I get help?

• Read this documentation and OpenAPI
• Contact support through the dashboard or your account channel
• Report API bugs with request id, tenant id, and timestamp