Zia ArsalanHome›PassKit Alternative
For agencies and product teams
A PassKit alternative you own and resell
PassKit is a capable platform, and for most teams renting that capability is the right call. It stops being the right call when wallet passes become the product rather than a feature — when per-pass pricing scales faster than your revenue, or when you are reselling and the margin belongs to the platform instead of you.
When replacing the platform makes sense
You resell wallet passes to clients
Every client you add pays a platform before it pays you. Owning the stack turns that recurring cost into recurring margin, and lets you brand it as your own product rather than reselling someone else's.
You are embedding passes in your own SaaS
Depending on an external issuing platform means an outage, price change or roadmap decision you do not control sits inside your product. Owning the issuing layer removes that dependency.
Volume has made per-pass pricing hurt
Usage-based pricing is cheap while you are small and punishing once you are not. The crossover point arrives quietly, usually a year after anyone last looked at the invoice.
You need behaviour the API does not expose
Unusual pass update logic, a bespoke scanning flow, a CRM integration nobody supports. With your own stack these are development tasks rather than feature requests.
What gets built
The pieces a wallet platform needs before it can replace a hosted provider.
The honest case against building
A comparison page that only argues one way is marketing. These are the real reasons to stay on a hosted platform.
- PassKit is mature, supported, and live in minutes — a build is neither.
- You take on hosting, monitoring and certificate renewals, or pay someone to.
- If your volume is low or unpredictable, usage-based pricing is genuinely cheaper.
- A build only pays back if wallet passes are core to your business rather than a side feature.
If two or more of those describe you, stay where you are. I would rather say that now than three months into a build.
Common questions
Why replace a platform that works?+
Usually you should not. The case for owning it appears when wallet passes become core to what you sell rather than a feature you bought — when per-pass pricing scales faster than your revenue, when you are reselling and the margin belongs to someone else, or when you need behaviour the API does not expose.
How long does building an issuing platform take?+
A focused issuing and scanning service is typically 6 to 10 weeks. A full multi-tenant, white-label platform with dashboards, reporting and integrations runs longer — 3 to 5 months depending on how much of the surrounding product already exists.
Can it be white-labelled for my clients?+
Yes, and this is the common request. Multi-tenant with per-client branding, domains and pass designs is the same architecture as the reseller platforms already in my portfolio, several of which agencies use under their own brand.
What about Apple certificate management at scale?+
This is the part teams underestimate. Certificates expire annually and a lapse silently breaks issuing. Whether you use one Pass Type ID across tenants or one per client is an architectural decision with real consequences, and it gets made deliberately at the start rather than discovered later.
Can you migrate us off an existing platform?+
Customer and pass data usually exports cleanly. Passes already issued under the old provider's certificate cannot be transferred to yours, so end customers add a new pass — planned as a staged migration with a message campaign rather than a hard cutover.
Talk through the architecture
Tell me what you are issuing today, at what volume, and whether you are reselling. I will come back with an architecture, a timeline and a straight answer on whether owning it beats renting it at your scale.