-
Notifications
You must be signed in to change notification settings - Fork 226
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #1607 from appwrite/otp-pricing-announcement
Otp pricing announcement
- Loading branch information
Showing
2 changed files
with
38 additions
and
0 deletions.
There are no files selected for viewing
38 changes: 38 additions & 0 deletions
38
src/routes/blog/post/announcing-phone-OTP-pricing/+page.markdoc
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,38 @@ | ||
--- | ||
layout: post | ||
title: Announcing phone OTP login pricing change | ||
description: To keep Appwrite Cloud sustainable, we are introducing phone OTP login pricing. | ||
date: 2025-01-10 | ||
cover: /images/blog/announcing-phone-OTP-pricing/cover.png | ||
timeToRead: 4 | ||
author: eldad-fux | ||
category: product | ||
featured: false | ||
callToAction: true | ||
--- | ||
|
||
One-time password (OTP) logins with SMS provide a secure and convenient way for users to authenticate themselves, ensuring that only authorized individuals can access accounts. By sending a temporary, time-sensitive code via SMS, phone OTP logins offer a strong layer of security, helping prevent unauthorized access and protecting user data. This service has become a crucial part of many applications, and we've worked hard to make it as easy and scalable as possible. | ||
|
||
When we launched Appwrite Cloud in beta, we focused on enabling the platform and providing you with as much value as possible. We intentionally didn't charge for every service, even in cases where we were absorbing significant costs ourselves - like phone OTP logins, where sending SMS messages through various telecom companies incurred a considerable expense. | ||
|
||
In the last few months, we've worked tirelessly with various vendors, navigating complex regulations and bureaucracy in multiple countries to ensure excellent phone OTP message delivery. Our goal was always to integrate phone OTP logins as simply as possible while providing a scalable and reliable service. | ||
|
||
It's been incredibly rewarding to see teams successfully implement phone OTP logins, using Appwrite to authenticate hundreds of thousands of users every month securely. Seeing this impact reinforces the importance of continuing to build a secure, accessible, and sustainable platform. | ||
|
||
# Pricing update | ||
|
||
As Appwrite continues to grow, we need to ensure that the platform remains sustainable and that we can provide the best possible service to all our users. Starting February 10th, we will begin charging for phone OTP login attempts. This change will help cover the costs associated with providing this valuable service and allow us to keep improving and expanding the platform. | ||
|
||
Please refer to our rates page for a breakdown of the new pricing, including rates by region and specific SMS costs. | ||
|
||
To help prepare for these changes, each team can visit their organization's usage page or the usage section of a specific project to review their current phone OTP usage. This will help you better understand your usage patterns and plan accordingly. | ||
|
||
![console image](/images/blog/announcing-phone-OTP-pricing/cover.png) | ||
|
||
# Free quota available | ||
|
||
To ensure that free users can continue exploring the platform and its features, we will provide up to 10 phone OTP login attempts per month at no charge. This will allow you to continue utilizing OTP logins to evaluate Appwrite's capabilities and integration into your workflows. | ||
|
||
# We're here to help | ||
|
||
If you have any questions about this change or need assistance with adjusting your application, please don't hesitate to contact us at [[email protected]](mailto:[email protected]). |
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.