The eSimphony Roadmap, in Our Own Words

A roadmap is a story about what the team believes will matter in the next 12–24 months. We'd rather tell that story directly than leave it to be inferred from feature announcements.

This is what eSimphony is shipping next, what each piece changes, and why it's on the list.

May 2026: Multi-eSIM

What it is: The ability to hold multiple active eSIM profiles on the same device — your home-country SIM, an eSimphony travel plan, occasionally a local SIM you bought for a specific reason — and switch between them without reinstalling anything.

What it changes: Today, most users keep their home-country physical or eSIM SIM as their primary line, and install eSimphony as a secondary line for travel. Multi-eSIM management makes this seamless: hold both profiles, switch the default with one tap, set rules for which line handles which kind of traffic (calls vs data, specific apps, etc.).

For users who keep both lines active all the time, multi-eSIM makes the eSimphony experience as low-friction as having a home-country plan with international roaming included — but at travel-eSIM prices and quality.

Why it's first: Multi-eSIM is the smallest change that gives existing users the biggest immediate upgrade. The lifetime-eSIM foundation we've already built supports it cleanly; we just need to ship the profile-management UX and the per-line routing rules.

June 2026: Family Plans

What it is: One eSimphony account that covers a whole family. Shared data pool, per-device controls, parental tools, single billing.

What it changes: Travel for families is one of the most underserved segments in the entire travel-eSIM industry. Today, family travel means:

• Parents install eSIM on their own phone.
• Each kid needs their own eSIM, often on the same account or a duplicate.
• Plans are sold per-device, not per-household.
• No shared data pool — so the kid who watches one YouTube video burns half the family's daily data, and you find out only after the bill.

Family plans solve all of this. One purchase covers up to N devices, with a shared data pool. Parents see per-device usage in real time, can set limits or pause specific devices, can buy top-ups that flow to whichever device needs them.

This is a category-defining feature in travel data. No major competitor has shipped it well. We're going first.

Why it's after multi-eSIM: Family plans require the multi-device account architecture that we're hardening for multi-eSIM in May. Shipping multi-eSIM first lets us validate the underlying account model under real load before opening it up to the family-plans surface.

August 2026: Loyalty and Rewards

What it is: Miles, tier status, and partner perks for active eSimphony users.

What it changes: Today, travel-eSIM users have no loyalty mechanism. Every trip is a fresh transaction. The customer relationship doesn't compound into rewards.

In a lifetime-eSIM model, where customers stay with one provider over years, loyalty starts to make sense. The eSimphony loyalty program will include:

• Miles for every dollar spent. Earn miles on every plan purchase. Redeem for free data, plan upgrades, or partner rewards.
• Tier status. Frequent travelers unlock benefits — priority support routing, free top-ups, exclusive plans.
• Partner perks. Discounts at travel-adjacent brands. Specific partners under negotiation, but the category will include lounges, travel gear, and travel-insurance providers.

Loyalty is travel-native rather than retrofitted. Airlines and credit cards have rich loyalty programs because they have long-term customer relationships. The travel-eSIM industry has lacked the relationship duration to support loyalty at all. eSimphony's lifetime architecture is the first model that supports it.

Why August: Loyalty programs require months of partner-negotiation and program-mechanics design before launch. The base infrastructure (miles ledger, tier engine) can be built in parallel with multi-eSIM and family plans; the partner ecosystem takes longer.

2027: Worldwide Direct-Carrier Coverage

What it is: Negotiated agreements with major carriers in every country we serve, replacing today's wholesale-aggregator-based coverage in regions where the aggregator approach is structurally weaker.

What it changes: Today, eSimphony's coverage is excellent in most regions but routed through wholesale aggregators in many countries. Aggregators are great for fast time-to-market (one contract gives you access to 100+ countries), but they're middle-layers — they take a margin, they have less negotiating leverage with the underlying carriers, and they can be slow to resolve carrier-specific issues.

Direct-carrier deals produce four improvements:

• Better pricing. Margin captured by aggregators flows back to users.
• Better network quality. Direct relationships mean better signal-routing, faster failover, priority access during congestion.
• Faster issue resolution. A direct relationship means we can pick up a phone (or open a Slack channel) with someone at the carrier when problems hit, rather than going through an aggregator's queue.
• Custom plans. Direct relationships let us build country-specific plans (e.g., extra coverage for a specific event, day-pass options, edge-case data shapes) that aggregators can't support.

Why 2027 and not sooner: Direct-carrier deals take time. Each country has a different carrier landscape, different regulatory environment, different negotiation cadence. We've started conversations with carriers in 15+ countries; the meaningful coverage shift will happen across 2027 as those deals close in clusters.

In the meantime, our aggregator coverage is strong enough that users won't see degradation while we transition. The direct-carrier transition is a quality and economics upgrade, not a "we're finally launching coverage" announcement.

Beyond 2027

A few things on the horizon that aren't yet committed to a quarter but are explicit team priorities:

AI Companion v2. Moza's capabilities expand significantly as the underlying language models improve and as we accumulate more interaction history. Expect proactive trip planning, smarter language coverage, and tighter integration with other travel apps.

eSIM for IoT. Travel data is the natural starting category, but the lifetime-eSIM architecture extends to connected devices — cars, wearables, point-of-sale terminals — that travel internationally. This isn't a near-term product, but it's a real long-term direction.

Partner program expansion. Today, the partner program is small and curated. Over 2027, we're expanding it significantly — more affiliate partners, more API integrations, more white-label opportunities for niche travel brands.

Group and enterprise plans. Family plans are the v1 of shared-pool data. Group plans (small businesses with travel-heavy teams) and enterprise plans (large companies with global rotational workforces) are natural extensions.

What the roadmap doesn't include

A few things explicitly not on the roadmap, because we get asked:

Domestic plans for the home country. eSimphony is a travel eSIM. We're not building a home-country mobile plan. The MVNO landscape for domestic carriers is well-served by other operators; we're focused on the international travel use case.

A subscription tier with premium features. All eSimphony AI features — Moza, Dynamic Plans, Troubleshooting — are part of the base product. We are not introducing a "Premium" tier that gates AI behind a monthly subscription. Buy the data plan you need; everything else is included.

Buying a competitor. People ask. The answer is no. We're building the product we want to build; the path doesn't run through buying a smaller version of the same thing we're trying to replace.

How to track the roadmap

We post visible product updates monthly on the blog and in the in-app changelog. Major milestones get explicit announcements. If the roadmap shifts (and software roadmaps do shift), we'll tell users — we won't quietly remove items.

Subscribe to the blog feed, follow @eSimphony on X, or download the app to get release notifications natively.

The thread that runs through all of it

Every item on the roadmap is enabled by the lifetime eSIM foundation. Multi-eSIM, family plans, loyalty, direct carriers — none of these work cleanly in a trip-by-trip model.

That's the bet underneath the roadmap. The foundation isn't a single feature; it's the platform that the next two years of features build on top of.

See the full pitch deck from MVNO Nation Americas, download eSimphony, or read about what makes us different. The roadmap is in motion.