Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 1 of 6 dimensions proven

0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.

by Netcore Cloud · netcorecloud.com

Report an error on this page Is this your product? →

Link to this page

Netcore Email API: AI-assisted analysis on whats-best.ai Netcore Email API: AI-assisted analysis on whats-best.ai (dark)

Add ?theme=dark to the image address for dark backgrounds. The badge shows the category and the month of the latest evaluation, and EU-Made where that is the product’s provenance. It never shows a score.

Netcore Email API at a glance

Vendor
Netcore Cloud
Headquarters
Incorporated in India source, captured 10 Nov 2026
Data hosting
Not stated on the vendor’s pages as of 10 Nov 2026
Free plan
Not stated on the vendor’s pages as of 10 Nov 2026
Panel verdict
The AI panel rates Netcore Email API 2/5, the mean of 6 judges. Netcore's Email API is a transactional email platform from Netcore Pvt. how scores are made
As of
Vendor pages captured 10 Nov 2026; evaluated by the panel 11 Nov 2026. all sources

Netcore Email API alternatives, European ones first →

Read this page as one judge. Each weighs the same scores by what they care about.

The panel's verdict

Netcore's Email API is a transactional email platform from Netcore Pvt. Ltd. of Mumbai, India. The bench scores it highest on data and security and on reliability and accounts, both clustering at 5 and 6: judges cite claimed ISO 27001 and SOC 2 Type II certifications, encryption in transit and at rest, and sub-accounts billed as per-subaccount credits on one combined bill. Deliverability spans 4 to 6: higher scores credited dedicated IPs, a named deliverability specialist and migrations from Acoustic, Salesforce, Adobe, Braze, SAP Emarsys, MoEngage and CleverTap; lower scores noted figures such as 95% inbox placement published without a measurement method. Observability split the bench: three judges scored 3 for documented inbound-parsing webhooks; three others, finding no public information on message logs or event webhooks for sent mail, left it unrated. Sovereignty sits at 1 to 2: we found no public information on hosting location, an EU region, a data processing agreement or subprocessors, though GDPR compliance and EU Privacy Shield maintenance are claimed. No price appears on any captured page.

Report an error

Speaks for it

  • Claimed certifications and practices are unusually well documented — ISO 27001, SOC 2 Type II, PCI DSS and HIPAA, encryption in transit and at rest, third-party vulnerability testing, and purge on request with a certificate issued to the client.
  • Sub-accounts support multi-client operations with independent access, per-subaccount credit allocation, one combined bill, and start or stop from a master dashboard.
  • Enterprise migration is concrete: dedicated IPs and authentication configured, a dedicated migration lead and deliverability specialist included, with migrations named from Acoustic, Salesforce, Adobe, Braze, SAP Emarsys, MoEngage and CleverTap.
  • Inbound parsing is documented in depth, turning each reply into structured JSON behind conditional rules on subject line, recipient domain and headers, delivered by webhook in real time.
  • Hosting spans multiple geographically separated tier-3 facilities with defined recovery time and recovery point objectives, replicated backups, and a 99.95 to 99.99% facility uptime guarantee.

Report an error

Held against it

  • Only inbound webhooks are documented; we found no public information on message logs, per-message event history or event webhooks for outgoing mail, and three judges left observability unrated.
  • The contracting entity is Netcore Pvt. Ltd. of Mumbai, India, and we found no public information on hosting location, an EU region, a data processing agreement or subprocessors.
  • The sending API scores 3 to 4: beyond inbound parsing, we found no public information on SDKs, stored templates, batch sending, rate limits or a test mode.
  • Deliverability figures such as 95% inbox placement and a 99%+ average deliverability rate carry no stated measurement method, and we found no public information on shared-IP vetting or automatic suppression of bounces and complaints.
  • The terms state Netcore may use, sell and publish aggregated anonymous usage data provided it does not identify the customer.

Report an error

Best for

  • You are an enterprise migrating off Acoustic, Salesforce, Adobe, Braze, SAP Emarsys, MoEngage or CleverTap and want a dedicated migration lead, deliverability specialist and zero-downtime migration included.
  • You run many client or brand accounts and need sub-accounts with independent access, per-subaccount credit allocation and one combined bill.
  • Your security review requires claimed certifications on record, customized retention periods on request, and purge on request with a certificate issued to you.
  • You send at extreme volume and want dedicated IPs with authentication configured during a controlled two-to-three-week ramp.

Report an error

Avoid if

  • Your legal team must evidence European processing before signing — the stated contracting entity is Netcore Pvt. Ltd. of Mumbai, India, and the captured pages describe only unnamed tier-3 data centres.
  • You need to trace outbound messages end to end — the only documented webhooks are for inbound parsing, and three judges found no public information to rate on observability.
  • You want a self-serve product you can try the same day — the documented buying path is a scheduled 30-minute conversation and an enterprise migration programme.
  • You need transactional mail on infrastructure separate from marketing sends — the vendor describes campaigns, journeys, transactional APIs and product notifications all running on one deliverability core.

Report an error

The scores

Panel median The median of the judges’ scores per criterion. Each label opens its reasoning below.

Sending API, SMTP & developer experience

Show reasoning
How this is scored

How an application sends mail: a REST API and an SMTP relay with their limits stated, official SDKs and drivers for named languages and frameworks (PHP and Laravel, Node, Python, Ruby and Rails, Java, Go, .NET), stored templates with variables and versions, batch sending, attachments, idempotency keys, scheduled sending, a test or sandbox mode that does not deliver, inbound email parsed into a webhook, and the quality of the API reference and guides.

0 — Not a sending service; an application cannot send email through it by API or SMTP.

3 — An API or SMTP credentials to send a message; SDKs, templates, limits and a test mode are basic or not described.

5 — A documented REST API and SMTP relay, official SDKs for several named languages, stored templates with variables, attachments and batch sending, rate limits stated, a sandbox or test mode, and quick-start guides for named frameworks.

8 — An API reference with every endpoint and error code, idempotency keys, scheduled sending, template versions and a template language documented, inbound email parsed to a webhook, an OpenAPI specification or official CLI, framework drivers maintained by the vendor, and a migration guide from named competitors.

10 — An API a team builds its product on: versioning and deprecation policy published, backward compatibility stated, full parity between API and SMTP features, local or staging test tooling that mirrors production, and every limit, timeout and retry behaviour documented.

Report an error

The SaaS Developer

The product is sold as an Email API with a claimed sub-120-millisecond latency, and inbound parsing is properly documented: each inbound mail becomes structured JSON in real time, with custom parsing rules driving webhooks. Beyond that, the captured pages give no public information on an SMTP relay's configuration, official SDKs or a Laravel driver, stored templates with variables, batch sending, rate limits or a test mode that never reaches a real inbox. 1 2 3

Report an error

The Platform Engineer

The captured pages show an email API with stated sub-120ms latency and three-second transactional delivery, and inbound parsing is documented in real depth — conditional rules on subject line, recipient domain and headers, structured JSON, webhooks into the application. We found no public information on SDKs, stored templates, attachments, batch sending, rate limits or a sandbox mode, which is exactly what my team needs before wiring a one-time-code send into it. 1 2 3

Report an error

The Shop Operator

An Email API with a stated sub-120-millisecond latency is the product, and inbound parsing is genuinely documented: each inbound email becomes structured JSON in real time, with custom webhook rules based on subject line, recipient domain and headers. But I found nothing on SMTP relay details, SDKs for PHP or other languages, stored templates, batch sending, rate limits or a test mode, which my developer would need before moving order confirmations off the hoster's mail server. 1 3 9

Report an error

The Data Protection Officer

An application-facing API is claimed (sub-120ms API latency, secure APIs, transactional streams), and inbound email is parsed into structured JSON delivered as webhooks with conditional rules on subject, recipient domain and headers. Beyond that, the captured pages do not describe SDKs for named languages, stored templates, attachments, rate limits or a test mode, so the developer experience beyond the basics is undocumented. 2 3

Report an error

The Agency Lead

An email API exists with sub-120ms latency claimed, and inbound parsing is genuinely documented — replies converted to structured JSON behind conditional rules on subject, recipient domain and headers, delivered by webhook. But we found no public information on SDKs for named languages, stored templates, attachments, batch sending, rate limits or a test mode; the captured SMTP page stays at marketing level. 1 2 3 9

Report an error

The Skeptic

An email API demonstrably exists — the vendor publishes sub-120-millisecond API latency and a page on SMTP — and inbound parsing is properly documented, with conditional rules that turn each reply into structured JSON delivered to a webhook in real time. We found no public information on SDKs for named languages, stored templates, batch sending, attachments, rate limits or a test mode, so the sending side rests on assertion rather than documentation. 1 2 3

Report an error

Deliverability & sender reputation

Show reasoning
How this is scored

What the vendor does so the mail reaches the inbox: guided SPF, DKIM and DMARC set-up with a custom return path and tracking domain, shared IP pools and how senders on them are vetted and policed, dedicated IPs with automatic warm-up, transactional and bulk mail kept on separate streams or IP pools, bounces, complaints and unsubscribes turned into suppressions automatically, feedback loops with mailbox providers, blocklist and DMARC monitoring, compliance with the Gmail and Yahoo bulk-sender rules, and published delivery times or inbox placement with their method.

0 — No sender authentication and no bounce handling; mail goes out from shared addresses with no reputation management at all.

3 — SPF and DKIM can be set up and bounces are recorded; IP policy, stream separation and suppressions are basic or not described.

5 — Guided SPF, DKIM and DMARC set-up with a custom return path, shared IPs with a stated sender vetting policy, dedicated IPs available, automatic suppression of hard bounces and complaints, transactional and marketing mail separated by stream or IP pool, and deliverability guidance in the documentation.

8 — Dedicated IPs with automatic warm-up and pool management, a stated acceptable-use and vetting process for shared pools, feedback loops and blocklist monitoring, DMARC reports, BIMI or custom tracking domains, compliance with the Gmail and Yahoo sender requirements stated, delivery times published, and access to deliverability experts.

10 — Deliverability that can be verified: delivery time and bounce rates per mailbox provider published continuously with their method, inbox placement testing included, pool reputation shown to the customer, and a documented escalation path with mailbox providers.

Report an error

The SaaS Developer

Dedicated IPs and authentication are configured as part of a documented migration, a named deliverability team offers audits, a specialist and ongoing management, and inbox placement is claimed at 95 percent with a 96.5 percent inboxing rate in one case study. The captured pages give no public information on guided SPF, DKIM and DMARC set-up, shared IP pool vetting, automatic suppression of bounces and complaints, or stated compliance with the Gmail and Yahoo bulk-sender rules. 1 2 4

Report an error

The Platform Engineer

Dedicated IPs and authentication are configured as part of a documented migration, a named deliverability team runs audits and ongoing optimisation, and delivery figures are published — 3-second transactional delivery, 95% inbox placement on Gmail, 96.5% inboxing in a case study. Those figures come without a measurement method, and we found no public information on automatic suppressions, feedback loops, IP warm-up or shared-pool vetting policy. 1 2 4

Report an error

The Shop Operator

Dedicated IPs with authentication configured are part of a documented migration step handled by a named team including a deliverability specialist, and the pages claim 95% inbox placement on Gmail, 3-second transactional delivery and 99%-plus average deliverability, though without a measurement method. I found nothing on guided SPF, DKIM and DMARC set-up a non-specialist like me could follow, nothing on shared-IP vetting, automatic suppression of bounces and complaints, or keeping order mail on a separate stream from the newsletter. 1 2 4

Report an error

The Data Protection Officer

Dedicated IPs, authentication set-up and a controlled two-to-three-week ramp are part of a migration run with deliverability specialists, and inbox-placement figures are published (95 percent overall, 95 percent on Gmail, 96.5 percent for a named client), though without a stated measurement method. Shared-pool vetting, automatic suppression of bounces and complaints, and Gmail and Yahoo bulk-sender compliance are not described in the captured pages. 1 2 4

Report an error

The Agency Lead

Outcomes and services are heavily evidenced: 95% inbox placement on Gmail claimed, dedicated IPs and authentication configured during a guided five-to-seven-day infrastructure set-up, a deliverability specialist and audit included with enterprise migrations, and case studies at extreme volume. We found no public information on guided SPF, DKIM and DMARC set-up, suppression handling, shared-IP pool policy or the method behind the placement figures. 1 2 4

Report an error

The Skeptic

Dedicated IPs and sender authentication are configured for you as part of a migration with a controlled ramp, a named deliverability specialist and a pre-commitment deliverability audit — more hand-holding than most. But the headline numbers (95% inbox placement, 95% on Gmail, a 99%+ average deliverability rate, a customer quoted at 100%) all arrive with no method behind them, no shared-pool vetting policy is stated, and the product page describes campaigns, journeys and transactional APIs all running on one deliverability core with no public information on separate streams or automatic suppression. 1 2 4

Report an error

Message logs, events & webhooks

n/r n/r n/r Show reasoning
How this is scored

What the team can see about each message once the application has handed it over: a message log searchable by recipient, subject, tag or message ID, the full event history (processed, delivered, deferred, bounced with the remote server's answer, opened, clicked, complained), how long logs and message content are kept, event webhooks with retries and a signature, an events API, dashboards and statistics per stream, tag or domain, alerts on bounce or complaint spikes, and access for a support team without developer rights.

0 — Nothing can be seen after sending; no logs, no events and no webhooks.

3 — Totals of sent and bounced messages; per-message logs, webhooks and retention are basic or not described.

5 — A searchable message log with per-message event history and the bounce reason, log retention stated, event webhooks for delivery, bounce, open, click and complaint, statistics per tag or domain, and an API to fetch events.

8 — Webhooks signed and retried with their schedule documented, the raw SMTP response and the rendered message viewable per send, log retention configurable or extended by plan, alerts on bounce, complaint or delivery-time thresholds, export or streaming of events to a named log or data tool, and read-only roles for support staff.

10 — Full traceability: every message traceable from API call to the receiving server's final answer, events streamed in real time with ordering and delivery guarantees stated, long retention with search across the whole history, and observability features documented with their limits.

Report an error

The SaaS Developer

The only webhooks documented are for inbound mail — parsing rules that push parsed emails to your application — which is a different thing from per-message event webhooks. The captured pages give no public information on a searchable message log, the event history of a send including the remote server's bounce answer, log retention, or signed webhooks, so the question of whether a given user received a reset mail has no documented answer. 3

Report an error

The Platform Engineer

The only event surface the captured pages describe is inbound: parsing rules that deliver webhooks and real-time JSON into the application. For outbound traffic we found no public information on a searchable message log, delivery and bounce events, log retention, or alerts on bounce spikes — as the person paged when the OTP mail stalls, that is the part I need most. 3

Report an error

The Shop Operator not rated — no public information

We found no public information on a searchable message log, per-message event history, log retention or event webhooks for outgoing mail. The analytics page captured for this gives no such details, and the only webhook documentation covers inbound parsing, not what happens to my order confirmations after they leave the shop. 3 5

Report an error

The Data Protection Officer not rated — no public information

We found no public information on message logs, per-message event history, how long logs or message content are kept, or event webhooks for sent mail. The captured analytics page yielded no confirmed details, and the only webhook evidence concerns parsing inbound email rather than what happens to outbound messages. 5 3 2

Report an error

The Agency Lead

Only the edges are documented: webhooks exist for inbound parsing, and a real-time signal analysis is mentioned in the deliverability pitch. We found no public information on a searchable message log, per-message event history, log retention, or event webhooks for delivery, bounce, open and click. 3 4

Report an error

The Skeptic not rated — no public information

We found no public information on message logs, per-message event history, event webhooks or how long anything is kept; an analytics page exists among the captures but yielded no confirmed facts about outgoing mail. The only webhook capability described anywhere is inbound parsing — rules that trigger webhooks when replies arrive — which tells a team nothing about what happened to the mail it sent. 3 5

Report an error

Message data, retention & security

Show reasoning
How this is scored

What is stored about each message and what the customer controls: whether message bodies are stored or only metadata, retention periods and the setting to shorten them, deletion of a recipient's data on request, open and click tracking that can be switched off per stream or message, TLS for delivery with an option to require it, encryption at rest, API keys with scopes and per-domain restrictions, IP allow-listing, two-factor authentication and SSO for the dashboard, an audit log, a vulnerability disclosure programme, and security certifications or audits with their scope. Where the data is processed and by whom is scored under sovereignty.

0 — Stores every message indefinitely with no controls, and the vendor states it uses message content for its own purposes.

3 — A privacy policy and a statement that data is encrypted; what is stored, retention and access controls are basic or not described.

5 — What is stored per message documented, retention periods stated, open and click tracking switchable, TLS used for delivery, API keys with restricted permissions, two-factor authentication for the dashboard, and a data processing agreement offered.

8 — Message content retention configurable down to none or metadata only, enforced TLS per domain or message, encryption at rest stated, scoped API keys and IP allow-listing, SSO (SAML) and roles, an audit log, deletion of recipient data by API, and ISO 27001 or SOC 2 stated with its scope.

10 — Data minimisation that can be verified: every stored field and its retention listed, content never stored unless the customer opts in, customer-managed encryption keys or equivalent, independent audits published with their scope, and every security control the customer has listed with its effect.

Report an error

The SaaS Developer

Encryption in transit and at rest, two-factor authentication, tier-3 data centres, SOC 2 Type II and ISO 27001 claims, third-party penetration testing, a responsible disclosure link, and customized retention with purge-on-request plus a purging certificate are all documented. The captured pages give no public information on what is stored per message, switching off open and click tracking, scoped API keys, SSO or an audit log, and one policy statement says Netcore may use, sell and publish aggregated anonymous usage data. 4 6 7

Report an error

The Platform Engineer

The security pages are substantial: ISO 27001, SOC 2 Type II and PCI DSS listed with an independent verification site, encryption in transit and at rest, opportunistic TLS outbound, two-factor authentication, retention customisable on request, and purging with a certificate issued. We found no public information on scoped API keys, SSO, an audit log, IP allow-listing, or whether and how long message content is stored. 4 6 7

Report an error

The Shop Operator

This is the strongest area: ISO 27001 and SOC 2 Type II with an independent verification site, encryption in transit and at rest, one-way encryption of stored addresses, two-factor authentication, third-party vulnerability testing, purge on request with a certificate, and customized retention periods. What I found no public information on is what is stored per message, switching open and click tracking off, API key scopes, SSO or an audit log — the customer-facing controls behind the certifications. 4 6 7 9

Report an error

The Data Protection Officer

Encryption in transit (HTTPS/TLS 1.2–1.3) and at rest are stated, two-factor authentication exists, retention periods can be customised on request, data is purged on request with a certificate, and ISO 27001, SOC 2 Type II, PCI DSS and HIPAA are claimed — though the captured pages give different ISO 27001 versions and no scope, and aggregated anonymous usage data may be used, sold and published provided it does not identify the customer. For a processor carrying patient names I look first for what is stored and how long: no captured page states the default retention period, whether message bodies are stored, whether open and click tracking can be switched off, or shows a data processing agreement, and TLS for outbound mail is opportunistic rather than enforceable per domain. 6 7 4 2

Report an error

The Agency Lead

A strong posture is stated: encryption in transit (HTTPS/TLS 1.2-1.3) and at rest, opportunistic TLS on outbound mail, two-factor authentication, ISO 27001 certification, SOC 2 Type II data centres, third-party vulnerability testing, purge on request with a certificate, and custom retention periods on request. We found no public information on scoped API keys, SSO, IP allow-listing, an audit log, or switching off open and click tracking. 4 6 7

Report an error

The Skeptic

The security pages are unusually substantive: encryption in transit and at rest, two-factor authentication, tier-3 data centres with SOC 2 attestation, third-party VAPT, purge-on-request with a certificate issued to the client, and ISO 27001 and SOC 2 Type II among the claimed certifications. None of it says what is stored per message, whether open and click tracking can be switched off, or whether API keys can be scoped; outbound TLS is opportunistic rather than something a customer can require; and the terms reserve the right to use, sell and publish aggregated, non-identifying usage data. Retention is customised on request, which is a negotiation, not a setting. 4 6 7

Report an error

Reliability, accounts & support

Show reasoning
How this is scored

Whether the platform can be relied on and run by a team: a public status page with incident history, uptime SLA and service credits published, redundancy or failover across data centres described, queueing and retry of mail during outages, sub-accounts or servers per application, client or tenant, team members with roles, separate environments, support channels and response times per plan, named migration help, and integrations with platforms that send mail on the customer's behalf (WordPress, Shopify, Shopware, Supabase, Vercel and similar).

0 — No status page, no support channel and no way to separate users or applications.

3 — A support contact and a single account; status page, SLA, sub-accounts and roles are basic or not described.

5 — A public status page with incident history, an uptime SLA on at least one plan, sub-accounts or separate servers per application, team members with roles, support by email or chat with stated hours, and plugins or guides for several named platforms.

8 — An SLA with service credits published, redundancy across data centres or regions described, mail queued and retried during incidents, sub-accounts with their own keys, domains and limits manageable by API, granular roles, support response times per plan, and migration assistance offered.

10 — Reliability that can be verified: uptime history published for years, post-mortems for incidents, multi-region failover documented, an SLA covering delivery latency as well as API availability, and white-label or reseller tooling for agencies and platforms.

Report an error

The SaaS Developer

Subaccounts are well documented — independent access, start and stop from a master dashboard, credit allocation on one combined bill — and multiple geographically separated facilities with defined recovery objectives plus a step-by-step enterprise migration from named competitors are described. The captured pages give no public information on a public status page with incident history or support response times, and a 'Scope of work and SLA' document is linked but its terms are not shown. 4 6 7 8 9

Report an error

The Platform Engineer

Subaccounts are properly documented — independently maintained access, start/stop from a master dashboard, credit allocation on a single combined bill — plus separated test, UAT and production environments, multiple geographically separated facilities, a disaster recovery strategy with recovery objectives, and migration help from named competitors with a dedicated lead. But the SLA is only linked, never quoted — no uptime figure with credits — and we found no public information on a status page with incident history or on whether mail is queued and retried during an outage. 4 6 7 9

Report an error

The Shop Operator

Sub-accounts are properly documented — independent access, start and stop from a master dashboard, credits allocated with one combined bill — alongside a linked scope-of-work and SLA document, geographically separated facilities with a 99.95 to 99.99% uptime guarantee, defined recovery objectives and a detailed enterprise migration with a dedicated lead. But I found nothing on a public status page with incident history or stated support response times, and the integrations directory returned no entries for the current search filters, so I could not confirm a Shopware plugin. 4 6 7 8 9

Report an error

The Data Protection Officer

Sub-accounts can be created, started and stopped from a master dashboard with independently shareable access and per-sub-account credit allocation on one combined bill, and team-level access can be restricted to the data each team needs. Redundancy across multiple geographically separated tier-3 facilities with defined recovery time and recovery point objectives and replicated backups is described, and migration help is substantial (a dedicated migration lead and deliverability specialist, migrations from named platforms such as Acoustic, Salesforce, Adobe and Braze); we found no public information on a status page, uptime history or support response times per plan, a linked scope-of-work and SLA document's terms were not captured, and the captured integrations directory showed no entries for the applied search. 9 6 7 4 8

Report an error

The Agency Lead

The sub-account model is documented the way an agency needs it: credits allocated per client sub-account, one combined bill for the master account, services startable and stoppable per sub-account, and independent access per subaccount; tier-3 geographically separated data centres, separated test and production environments and a linked SLA document back this up. We found no public information on a public status page with incident history, support response times per plan, or plugins for platforms such as WordPress. 4 6 7 8 9

Report an error

The Skeptic

Sub-accounts are genuinely documented — independent access, credits allocated per subaccount, one combined bill, start and stop from a master dashboard — and the migration offer is the most concrete I have read, naming Acoustic, Salesforce, Adobe, Braze, SAP Emarsys, MoEngage and CleverTap as sources with a dedicated migration lead and zero-downtime cutover. Geographically separated facilities and defined recovery time and recovery point objectives are stated. We found no public information on a status page, on what the linked Scope of work and SLA document actually promises, or on support response times per plan — and the integrations directory we read displayed no entries for the filters applied. 4 6 7 8 9

Report an error

European sovereignty panel opinion

Show reasoning
How this is scored

Who the contracting entity and the parent company are, where messages, logs and recipient data are processed and stored, whether an EU region can be chosen and what it covers, and who the subprocessors are (cloud hosting, sending infrastructure, logging, support and payment tools). Independently sourced by the sovereignty pipeline; every message carries personal data, so the whole sending chain counts, not only the dashboard.

0 — Non-EU vendor and contracting entity, hosting unstated, subprocessors unnamed, and no data processing agreement offered.

3 — A privacy policy and a data processing agreement exist, but hosting location is unstated or non-EU and the subprocessors are not listed.

5 — An EU region available and an EU contracting entity or EU representative, but parts of the chain (sending infrastructure, logs, support, payment) run through non-EU providers without a stated safeguard, or the EU region does not cover logs and account data.

8 — EU processing of messages, logs and account data on named infrastructure, an EU contracting entity, subprocessors listed with their locations, a data processing agreement published, and security certifications (ISO 27001, SOC 2) stated.

10 — Sovereign end to end and evidenced: European ownership, entity, hosting, sending infrastructure and every subprocessor, data export and deletion documented, and certifications published with their scope rather than implied.

Report an error

The SaaS Developer

The contracting entity is Netcore Pvt. Ltd. of Mumbai, India, and the captured pages give no public information on where messages, logs and account data are processed or stored, on the subprocessors in the sending chain, or on a data processing agreement. GDPR compliance and EU Privacy Shield compliance are claimed, but no EU region or European safeguard is evidenced. 6 7 9

Report an error

The Platform Engineer

The contracting entity is Netcore Pvt. Ltd. of Mumbai, India, and we found no public information on hosting location, data residency, an EU region, a data processing agreement or the subprocessors in the sending chain. GDPR compliance and an EU Privacy Shield commitment are stated, but nothing on the captured pages evidences European processing, storage or ownership. 6 7 9

Report an error

The Shop Operator

The contracting entity is Netcore Pvt. Ltd. in Mumbai, India, and while GDPR compliance is claimed and a privacy policy is linked, I found no information on where messages, logs and recipient data are hosted, no EU region, no data processing agreement and no subprocessor list. Nothing on the captured pages evidences European processing for my German and Austrian order data. 6 7 9

Report an error

The Data Protection Officer

The contracting entity is Netcore Pvt. Ltd. of Mumbai, India, and the captured pages state only unnamed tier-3, geographically separated data centres without a country for messages, logs or account data; no EU region is described. A privacy policy and a GDPR page are linked and EU/UK GDPR terms are referenced, but we found no public information on a data processing agreement or a subprocessor list, so the whole sending chain sits outside any evidenced European arrangement. 6 9 2

Report an error

The Agency Lead

The contracting entity is Netcore Pvt. Ltd. of Mumbai, India, stated plainly, and GDPR compliance plus the EU Privacy Shield are asserted with a privacy policy and GDPR pages available. We found no public information on where messages, logs and account data are processed, on an EU region, on a data processing agreement, or on any named subprocessor — a serious gap for GDPR-bound client domains. 6 7 9

Report an error

The Skeptic

The contracting entity is Netcore Pvt. Ltd. of Lower Parel, Mumbai, India; hosting is described only as leading tier-3 data centres with no location, and we found no public information on an EU region, on the subprocessors in the sending and logging chain, or on a data processing agreement. GDPR compliance and even EU Privacy Shield maintenance are claimed, but a compliance claim is not an EU region, not a named chain of providers, and not a document a European buyer's legal team can sign. 2 6 9

Report an error

Pricing transparency not rated — the vendor publishes no price

Show reasoning
How this is scored

Whether a buyer can compute the real annual cost from public pages alone: price per tier by monthly message volume, the price per additional thousand messages, the free tier and its limits, what dedicated IPs, extra log retention, sub-accounts, SSO and support plans cost, minimum term, and whether unused volume carries over.

0 — No public prices at all; every customer is a sales call.

3 — A starting price or a free tier exists, but how cost scales with volume or which features cost extra is unclear.

5 — Tiers are public with their monthly volume and price, but at least one commonly needed piece (overage rate, dedicated IP, longer log retention, SSO, support plan) is unpriced or "on request".

8 — Every tier priced publicly with its volume and overage rate per thousand messages, dedicated IPs and add-ons priced, log retention per tier stated, minimum term and VAT treatment stated.

10 — Complete price computability: annual cost derivable for a given monthly volume, number of domains and sub-accounts and feature set, with every add-on, support and overage fee and the cancellation terms published.

Report an error

The SaaS Developer

I found no price on any captured page — no tiers, volume rates, overage rates, free tier or add-on prices — while the documented path to buying is a 30-minute conversation with the team, and billing is described only as allocating credits to subaccounts on a combined bill. No annual cost can be computed from the public information I can see. 4 9

Report an error

The Platform Engineer

No captured page shows a price, a tier, a volume allowance or a free tier; the buying motion is a scheduled 30-minute conversation with the team and an enterprise migration programme. Subaccounts are billed through allocated credits on a combined invoice, but no rate is published, so an annual cost cannot be computed from anything we read. 4 9

Report an error

The Shop Operator

No price, tier, volume band, overage rate or free tier appears on any captured page; the only buying route shown is booking a 30-minute conversation with the team and an enterprise migration programme. I cannot begin to compute an annual cost for my 900 orders a week from public pages alone. 1 4 9

Report an error

The Data Protection Officer

No price, tier, volume allowance or free tier appears on any captured page; engagement is routed through a scheduled 30-minute conversation and an enterprise migration programme, which reads as a sales-led motion. We found no public information on per-message pricing, dedicated-IP charges, support plans or cancellation terms. 4 1

Report an error

The Agency Lead

No tier prices, free tier, overage rates or add-on prices appear on any page we read, and the documented path to a price is a scheduled 30-minute conversation with the team. With an enterprise consulting motion around it, no per-client price can be written into a maintenance contract from what is published. 1 4

Report an error

The Skeptic

Across every page we read we found no price of any kind: no tiers, no per-message rate, no free tier, no add-on or support pricing. The buying path the pages offer is a 30-minute consultation with the team and an enterprise migration process staffed by a dedicated CRED team, so a buyer cannot begin to compute an annual cost from what is published. 1 4

Report an error

European sovereignty — proven facts

1 of 6 dimensions proven

Built only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.

Hosting location Not determined — uncited Report an error
Hosting options Not determined — uncited Report an error
Open source Not determined — uncited Report an error
Data processing agreement Not determined — uncited Report an error
Transfer impact assessment Not determined — uncited Report an error

Questions about Netcore Email API

Is Netcore Email API European?

Not determined: the vendor’s pages as captured do not say where Netcore Email API is based. Its vendor, Netcore Cloud, is incorporated in India, per the vendor’s page captured 10 Nov 2026.

Where does Netcore Email API store data?

Not stated on the vendor’s pages as of 10 Nov 2026.

Does Netcore Email API have a free plan?

Not stated on the vendor’s pages as of 10 Nov 2026.

What are the best alternatives to Netcore Email API?

As of 19 Nov 2026, the panel rates Lettermint (3.5/5), Bird Email API (formerly SparkPost) (3/5) and Postmark (3/5) highest among the other 22 Transactional Email products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is Lettermint (EU-Made, Netherlands). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Netcore Email API alternatives.

Where this could be wrong

What we left out

A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.

Sources (9)

The pages every claim on this page was read from — each one checked, dated, and kept verifiable.

  1. 1 Vendor page netcorecloud.com Checked 10 Nov 2026 Details →
  2. 2 Sending API, SMTP & developer experience — found from sitemap netcore.ai Checked 10 Nov 2026 Details →
  3. 3 Sending API, SMTP & developer experience — found from sitemap netcore.ai Checked 10 Nov 2026 Details →
  4. 4 Deliverability & sender reputation — found from sitemap netcore.ai Checked 10 Nov 2026 Details →
  5. 5 Message logs, events & webhooks — found from sitemap netcore.ai Checked 10 Nov 2026 Details →
  6. 6 Message data, retention & security — found from sitemap netcore.ai Checked 10 Nov 2026 Details →
  7. 7 Message data, retention & security — found from sitemap netcore.ai Checked 10 Nov 2026 Details →
  8. 8 Reliability, accounts & support — found from sitemap netcore.ai Checked 10 Nov 2026 Details →
  9. 9 Reliability, accounts & support — found from sitemap netcore.ai Checked 10 Nov 2026 Details →