I am building an app for my client in canada and I'm in need of SMS. They are okay with long code numbers itself. Can anyone help me with the pricing for number (one time or monthly ) and sms pricing (Local).
I'm not sure if you are calculating the price correctly, because a single delivery could be triggered by a single publish if multiple subscribers are on the topic. This help with scenario's like regional events, but wouldn't help so much with personal events like new friend requests.
If I have all 150 million subscribes on a single SNS topic, I would expect to be paying $75.50 every time I publish and publish a message. 150,000,000 deliveries @ $.50 per million = $75. Then add the cost of the 1 publish @ $.50. So if you only had one list your cost would be significantly less. It would always cost you $15,000 for delivering 150 million messages to 200 users, but it may only cost an additional $100 dollars if all of the users were on the same SNS topic and only 200 publishes were performed.
https://aws.amazon.com/sns/pricing/
When you use SNS topics to broadcast identical messages to many recipients at once, your effective price can be even lower than $1.00 per million mobile push notifications
By the way parse push is shutting down.
Sometimes service providers don't advertise sustainable business models. Their prices are sometimes teaser rates which increase once you buy-in and build your application. Once you are actually sending 150 million messages 200 times a month $30k a month starts to look cheap when you consider the resources of that kind of operation.
Now you have to factor in the cost of migrating away from a volatile service provider. You need to fill at least three professional roles to do the migration: developer, quality assurance and project manager. That's going to quickly cut down any previous savings. I'm not just being theoretical here. I've had to do these kind of migrations in the past, because service providers did giant price increases.
I would not only expect the pricing in AWS to only go down over time, but I would also expect a high quality of service and support over the service's lifetime with AWS. Service quality and support is something you don't get to test until you are in production and have already implemented.
A big part of what you are paying for is trust in the service and that's not going to be reflected on any specification of what the service provides.
If you'll consider even other providers, such as PushApps, you'll find out that there are also unlimited notifications packages for 50$ per month.