Help me downgrade to the Free plan

Project ID: 6844dad50019ad7eddff
I want to downgrade to the free plan because I do not use any of the features that come with the premium plan. However, I am told that I am "Over limit." I subscribed to Appwrite Premium plan only on Sept 2nd. Before that I had the free plan. I created my project and the four functions more than a year ago when free plan allowed four functions. Now, I am unable to downgrade because I created four functions more than a year before I upgraded. This is really unfair. How should I handle this?
I can prove the date of the creation of my functions via my GitHub.

@Los Feliz The downgrade is based on your current resource usage, not when the functions were created. To switch back to the Free plan, you will need to reduce this project to 2 functions. The downgrade flow will let you choose which functions to remove.

how is that fair? As I said, I joined Appwrite more than a year ago, when free plan allowed four functions. Am I being punished for downgrading?

which business model does this logic follow???? when people join a platform, they are able to keep their initial status, regardless of the changes that the platform may make after that date.

I expect a clear answer. Please do not leave me hanging.

@Harsh

Hey, the free users at the time also were migrated to the new free plan, and those terms were applicable for everyone on the free plan for both old and new users 🙂

To tackle this (if going to free plan), you can try to see if the allowance of two functions can handle the workload of four or not instead of keeping four separate functions.

Hi Feliz,

I can relate to the frustration. I can see how unfair this can feel on individual level, and I can also see into company decisions that lead to this experience. Which is what makes it so hard for me - both perspectives make sense.

First I want make it clear that we are not trying to disadvantage you specifically, or any developer on their journey. I hope transparency and communication from our end goes to prove that. You can focus on building, because we provide you a cloud platform. Thats the relationship we aim for with every developer using Appwrite.

Indeed, there were changes to plans we provide, both free, and pro. Even scale, and even some custom plans we are preparing in the background. Some changes open up more possibilities, while some need to be limiting by nature, to reduce costs. We always aim to be transparent and communicate why we do them, as we do them.
Unfortunately we cannot commit to to a specific pricing for dozens of years, as that would make our business close to impossible to sustain. Very good example of that is that during Beta all messages were free, but we realised SMS became very expensive cost for us, and we had to adjust pricing to better reflect this cost at bigger scale.

To cycle back to your original problem, I am available to discuss your project setup, and be of help to get your current code running within two functions. We see many solo developers having all of their logic nicely categorised under API endpoints within single function. The limit of two per project commonly becomes trouble for larger teams where each team handles a specific serverless function (acting as micro-service), in multi-tenant situations (1 function per client), and a few rare examples, also related to enterprise.
The aim for 2 functions limit is not to prevent you from building with Appwrite.

With all that out of the way, Ill switch to bit more casual tone Soo if you are interested, please drop me a message and we will figure out how to move your project within 2 functons limit, together.

Hello,
I have thought about combining functions, but I am not sure how it will reflect on me as a developer. I do not make any money from this project. I use the project as a demonstration of my skills, and combining the functions may seem like I don't have the understanding of separation of concerns. That being said, I guess it is better to combine functions than not allow users to delete their account.
Should I direct message you on Discord?

@Meldiron

Just left for dinner, but Ill answer first thing in morning 🙌 I have some nice ideas.

no problem.

Thank you.

🙇‍♂️

Morning ☀️

combining the functions may seem like I don't have the understanding of separation of concerns
This caught my attention. Even in Appwrite, we utilize both systems.. Sometimes we do microservices to scale tings out, and sometimes we intentionally ship a service in a monolith.

If your goal with Functions is to showcase skills and understanding, I think same makes sense - show both skills.
First have a big function that does most of the things. This shows good understanding of REST API, code structure, ability to reuse code, follow patterns, consistency...
And then, have one separate function (because Appwrite allows two), which acts as a microservice, showing you can do separation too.

I downgraded already. the cycle would renew tomorrow. now I have to figure out how I can combine the user delete function with the reCaptcha verification function.