AWS Pinpoint shuts down October 30. Here are your real options.

If you run campaigns, journeys, or segments on AWS Pinpoint, you have until October 30, 2026 before they stop working. This isn't a maintenance-mode deprecation — the engagement layer is being removed, and AWS deletes Pinpoint data after the deadline. New customers have already been blocked since May 2025.

We build WingBlaze, a messaging platform, so we have a horse in this race — the disclosure is right up front. But this page is the decision framework we walk migrating teams through, and it's vendor-neutral: two of the four paths below don't involve us at all.

What's actually going away

Pinpoint was two products wearing one API: a transport layer (push, SMS, email delivery) and an engagement layer (projects, endpoints, segments, campaigns, journeys, message templates, the analytics dashboard). AWS is keeping the transport and retiring the engagement:

You use	AWS says move to	Survives?
Push/SMS sending APIs	AWS End User Messaging	✅ renamed, kept
Email sending	Amazon SES	✅ kept
Segments, campaigns, journeys	Amazon Connect	⚠️ different product
Endpoint/user data	export it yourself before EOS	❌ deleted after

Option 1: Follow AWS's path (End User Messaging + SES + Connect)

Honest take: this works if what you mostly used was transport. If your Pinpoint usage was SendMessages calls with your own orchestration on top, End User Messaging + SES is a clean, cheap landing — stay there.

The friction is the engagement layer. Amazon Connect is a contact-center suite; Outbound Campaigns and Customer Profiles can be configured for lifecycle messaging, but you'll be operating a call-center product to send push campaigns. Multi-tenant setups (agencies, platforms with per-customer projects) translate especially poorly — Pinpoint's project model has no clean equivalent, a pain point AWS's own community documents. If you loved Pinpoint because it was cheap, usage-priced engagement infra for developers, Connect is not that.

Option 2: DIY on raw transport

FCM and APNs are free. SES is $0.10/1k. You can rebuild segments, scheduling, retries, opt-outs, and analytics yourself — plenty of teams do. Budget for: idempotent send ledgers (retried jobs must never double-send), token lifecycle (dead-token pruning), quiet hours and frequency caps, per-subscriber timezones, and an events pipeline for open/click attribution. It's months of platform work to get back to where Pinpoint's console was on day one. The right call at very large scale or with unusual requirements; expensive everywhere else.

Option 3: Enterprise engagement platforms

Braze, MoEngage, CleverTap, Iterable and friends will happily absorb your Pinpoint workload — with sales cycles, annual contracts, and entry pricing that typically starts around $25K–$60K/year. If you have a marketing team that wants agentic AI, web personalization, and a CDP, this tier earns its price. If you're a developer-led team that chose Pinpoint because it was usage-priced infrastructure, the pricing whiplash is severe.

Option 4: Usage-priced engagement platforms (where we sit)

The middle path: keep Pinpoint's shape — API-first, usage-priced, no contracts — and keep the engagement layer too. This is what WingBlaze is: campaigns, journeys, segments, funnels/cohorts/RFM analytics, over push (FCM/APNs/web), email, SMS, voice, WhatsApp, LINE, Zalo, Viber, Telegram, RCS and KakaoTalk. First 10,000 MAU free with every feature; $5 per 1,000 MAU after; no feature gates, no sales call. Data hosted in Southeast Asia (asia-southeast1) if that matters to you.

The Pinpoint concept map is nearly 1:1 — project→app, endpoint→device, UserId→subscriber, attributes→tags — and our importer reads Pinpoint's endpoint export JSONL directly: it merges endpoints by UserId into unified subscriber profiles, maps channels, preserves attributes as tags, and respects opt-outs. The migration guide walks the whole path; most teams complete the data move in an afternoon and run both systems in parallel until the numbers match.

Start free with Google sign-in →

Whatever you pick, do this now

1. Export your endpoint data today (aws pinpoint create-export-job). It costs nothing to have the JSONL sitting in S3, and after October 30 the data is gone.
2. Inventory which Pinpoint features you actually use — transport-only teams have an easy migration; journeys/segments teams don't.
3. Leave a month for parallel running. Deliverability and attribution need real traffic to validate.