Free
For developers and apps proving fit
$0Up to 2,500 reached customers a month
- Two objectives
- Community support
Pricing
Pay for the customers Ambipath reaches.
A reached customer is one Ambipath sends a notification to or builds a screen for in a calendar month. Customers it leaves alone cost nothing.
Plans
Start free, and move to an annual contract when the holdout reads.
Growth
Self-serve, billed monthly
$0.20per reached customer, $500 monthly minimum
- Up to 50,000 reached customers a month
- All objectives
- Studio and holdout reporting
Scale
For apps of 200K to 5M monthly actives
From $0.11per reached customer, graduated, annual contract
- An onboarding engineer
- Flow review before launch
- Warehouse export and single sign-on
- 99.9% uptime
Enterprise
For apps above 5M monthly actives
10%of measured incremental revenue, $250K annual platform minimum
- Custom connectors
- A choice of composition model
- A dedicated engineer
Design partner pilots
Run your first objective with us, free through June 2027.
We are taking five to eight design partners in the first half of 2027. Each pilot runs one objective in your app against a 10% holdout, eight to ten weeks from the day we agree scope, counting your next release.
- Week 0
Agree the scope
We pick the journey with you and write down the metric, the holdout size and the success threshold before anything ships.
- Your next release
Ship the SDK
Your engineers add the Swift package and register the components you already ship. An Ambipath engineer pairs with them through the release.
- Four to six weeks
Run one objective
Ambipath works with 90% of the customers the objective covers and leaves 10% alone. You can review every flow before it goes live.
- Readout
Read the result together
We compare the metric against the holdout using the events in your own warehouse, and decide on a Scale contract from there.
What we ask in return
- A holdout from the first day
- A success threshold, agreed in writing
- Permission to publish the result
From July 2027, pilots cost $15,000, credited against the first year of a Scale contract.
Who a pilot fits
A pilot reads fastest in an app that already has these in place.
- Customers sign in
- So the app knows who each person is.
- Push already works
- A CRM or engagement platform delivers notifications, so opt-in and consent exist.
- A release every two weeks
- Or more often, so the SDK ships inside the pilot window.
- A component library
- A design system Ambipath can build screens from.
- An owner for retention
- One person measured on it every week.
- A frequent, countable outcome
- An order, a booking, a deposit or a class, so the holdout reads in weeks.
Questions
What finance asks first
- What counts as a reached customer?
- A customer Ambipath sends at least one notification to or builds at least one screen for in a calendar month. Ten notifications to the same customer in a month count once.
- Is model usage included?
- Yes. Decisions and screens are included in the rate. A larger model for first screens is an option on Enterprise.
- What happens after the pilot?
- If the result meets the threshold we agreed, the objective moves to a Scale contract and keeps running. If it misses, you keep the readout, and your app runs as it did before, since every Ambipath link falls back to your own screens.
- Can we pay on results instead?
- Apps above 5M monthly actives can pay 10% of measured incremental revenue against the holdout, with a $250K annual platform minimum.