NetcoreOrbit

One API. Multiple ESPs. Complete routing control.

Orbit lets you route and manage email traffic across ESPs with minimal migration effort.

See Orbit in action Talk to an expert
LIVE ROUTING
APPLICATIONSAPI
CONTROL PLANEORBITROUTING ACTIVE
Netcore50%
SendGrid30%
Amazon SES20%
TRAFFIC ALLOCATION100% DISTRIBUTED

One ESP shouldn't decide the fate of your email.

When everything depends on one provider, even a small disruption can have a ripple effect.

01
ACTIVE ROUTE

The ESP fails

Provider outage / degraded performance

Your primary ESP experiences an outage or starts rejecting or delaying traffic.

02
TRAFFIC QUEUE

Email slows down

Latency ↑ · Queues ↑ · Delivery delayed

Critical emails start waiting in queues, increasing latency and potentially delaying customer actions.

03
BACKUP ROUTE

Your backup isn't ready

Backup ESP → Idle · Unwarmed · Untested

Email that never stops. Powered by Orbit.

Orbit sits between your applications and email service providers, giving you a single layer to connect providers

Keep an alternate route ready.

Control where your traffic goes.

Use provider and performance signals to inform routing decisions.

One API across providers.

Move traffic progressively as confidence grows.

Take control of where your email goes.

Move traffic across providers without changing your application.

3 providersone control layer

LIVE ALLOCATION

TOTAL · 100%
Select a stream
Netcore40%
SendGrid35%
Amazon SES25%

ACTIVE ROUTE · Payments traffic is directed to Netcore

ROUTING LOGIC

Change the route. Not your application. Orbit supports percentage- and attribute-based routing across these dimensions.

Smarter Ways to Send Email.

Connect your providers once. Then use Orbit to decide how traffic is distributed, routed and moved across them.

01

Run multiple ESPs

Keep more than one provider in your email stack and manage traffic across them from a single layer.

02

Pilot a new provider

Put a controlled percentage of live traffic through a new ESP and evaluate it before expanding.

03

Manage different email streams

Route payments, alerts, notifications or application-specific traffic through different providers based on your requirements.

04

Shift traffic progressively

Move traffic in stages — 90/10 → 75/25 → 50/50 → 100% — instead of making one large switch.

Answers, routed clearly.

No. Orbit supports both progressive migration and permanent multi-ESP operation. You can retain your incumbent ESP, route selected streams through Netcore, or maintain an ongoing percentage split across providers.

You generally replace your current ESP endpoint and application-side API key with the Orbit endpoint and Orbit API key. Your incumbent provider credentials are then configured inside Orbit, and the broader call structure can remain largely unchanged when compatibility is confirmed.

Yes. Separate applications, keys, brands or email streams are represented through Orbit subaccounts, so each stream keeps its own credentials, routing and monitoring.

Traffic can be distributed by percentage and routed using attributes such as sender address, subject line, email tag, communication type, application or subaccount. One provider is designated as the default route for anything that doesn't match a specific rule.

Orbit surfaces the issue, alerts you, and retains affected messages in retry or queue handling. The affected provider can then be disabled and new traffic redirected to an alternate route.

Orbit can automatically fail over traffic to another ESP when a provider experiences an outage or disruption, helping keep your email traffic moving without manual intervention.

Traffic volume, provider selected, the route or rule applied, overall and provider-level latency, delivery health, queue status, and provider-wise distribution — down to the individual API key or subaccount.

Yes, Orbit supports both API- and SMTP-based injection. Compatibility and any provider-specific limitations should be validated during solution design.

Keep Your Email Uninterrupted with Orbit.

Build resilience into every route, without adding complexity to your stack. Talk to an expert about your email infrastructure.