$ 5,00,000
*
Cost breakup
Build cost (one-time)
This includes engineering resources
$400,000
Cost of running (yearly)
This includes infrastructure costs (compute and storage), maintenance, and on-call teams.
$400,000
100% deliverability
Zero development cost
Min. 20% savings on messaging cost
*Calculated using continuous data modelling using polynomial model of degree 7 for accuracy. Best practices on cloud infra development & monitoring considered.
Engineering & Product takes 50 hours per month.
Engineering & Product takes 100-500 hours per month.
Engineering & Product takes 1000+ hours per month.
Free forever plans create bad incentives, and aren’t sustainable. Fyno doesn’t have a free forever plan and doesn’t plan to. Free plans create bad incentives that hurt our users. Digital products that don’t charge money, or don’t charge enough, end up selling customer data or shutting down. Neither of those outcomes is acceptable to us. When a users pays for Fyno, they are sending a strong signal that we’ve created something of significant value for them. This signal drives our product development process. We build and improve Fyno for our paying customers, first and foremost. On the other hand, users on a free forever plan can be the most fickle while getting the least value from the product. Their requests can dilute a product which ultimately hurts the people who use it the most.
A notified user is a unique user who has receives at least one communication/ notification in a month. Each unique user would in turn have unique destinations configured on the available channels (like unique mobile number for SMS and WhatsApp or unique email address for Emails).
No. We do not offer a self-hosted solution. But we offer a managed solution, where we spin up a dedicated instance of Fyno in a separate server only for you. This server can be managed by you or by us for you.
Yes
Notification event refers to a configuration to trigger communication to users. It triggers the communication workflow to send the notification through the and the route/ channels configured. Example: A trigger to notification event “Order under processing” will send the “Order under processing” message through the configured route/ channels.
We work with regulated companies and have supported all their security requirements. Checkout our Data Security page for more details.
An API request is a request/ payload sent to Fyno to trigger customer communication. Each API request can send communication to the user over all the channels that have been configured for that notification event.
Checkout our dedicated Data Security Page for more details.
Yes. Fyno is built to meet all enterprise needs like user based access controls, workspaces, advanced security features and more!
Yes, we do. On paid plans, we promise uptime SLA for our cloud system for 99.5%. For our enterprise plan we can offer upgraded SLA as part of the commercial contract.
For businesses that have repeat engagement from users and are using Fyno to send communications to engage and retain such users, pricing based on number of notified users will make more sense. Example would be Mobile/ web app companies that want to maximise user engagement/ retention.For Businesses that do not have repeat engagement from users in a month and want to use Fyno to send only status updates/ alerts, pricing based on number of API requests will be suitable. Example: Delivery or logistics companies who want to notify order updates to their users.