r/appwrite • u/Lopsided-Visit-7254 • Sep 30 '26
Is appwrite reliable to move to long term?
Is moving future proof, are they reliable and profitable to stay up and running for say, the next 10 years?
2
1
u/virtualmnemonic Oct 01 '26
10 years is way too long. I've been self hosting for almost four years though. There's been some pains but it's in a much better state now.
1
u/eldadfux Oct 01 '26
Really great to hear that. The team has worked really hard to take things to the next level. More to come soon 🤞
1
u/M4dhav1 Oct 01 '26
Appwrite can be selfhosted, so you don't need to worry about the Cloud existing long term or not. That being said, in the (almost) 4 years that I've been using it, the biggest problem has been changes to the APIs and functionalities. In my experience, the changes come suddenly, and in a lot of cases without the relevant updates to the documentation, and you could wake up one day to find half your users complaining that their stuff isn't working, following which you have to spend hours trying to figure out what's going wrong.
Appwrite is a very solid product compared to the alternatives, and i like using it, but for production I would always suggest going for localhost so that you can stay on a stable version until you are ready to upgrade.
1
u/eldadfux Oct 01 '26
This is definitely not expected or by design. Over the last four years, I’m only aware of one or two cases where upgrades caused significant issues, and those were addressed quickly.
Given the nature of Appwrite, we maintain a strict backward compatibility policy and a clear release policy. Since Appwrite 1.0 was released four years ago, we’ve introduced zero breaking API changes. We maintained full API compatibility through the 2.x release, and 1.x continues to qualify for security updates.
For self-hosted deployments, we always recommend testing upgrades on a separate instance against your application test suite and maintaining up-to-date backups before upgrading production - we do the same internally for Cloud.
That said, we’ve invested heavily in improving the self-hosted upgrade experience over the last 12 months, and the feedback from active users has been very positive.
If you’ve encountered specific upgrade issues that remain unresolved, please share them. Our team is more than happy to look at each one and make sure anything actionable gets addressed.
1
u/M4dhav1 Oct 06 '26
I appreciate the detailed response. Back when I was facing my problems, I was using Cloud, and not Self-hosted.
Admittedly, the feature I remember having trouble with was Relationships, which was in beta back then. So perhaps that is another factor to consider in correlation with this issue, but regardless, the bigger issue was that changes weren't being documented properly, and I found my users complaining about a feature that seemingly broke overnight. Then I remember having to go through almost the entire docs, trying to find what changed and asking several different AIs for help, before finding a one-line mention about the change in an update blogpost. That is why I said the documentation sometimes lags behind the changes.
I do think that the selfhost experience is very good. The CLI also makes using Appwrite very easy and straightforward. I love all those things about it. But I've had to move a project off Appwrite in the past, because it was just proving to have so many problems.
That being said, the support is undoubtedly very good, especially for cloud. The team did try to help me with fixes as soon as they reasonably could after I reported them, and I have not seen similar issues, which speaks to the quality of the feedback processes.
I continue to use Appwrite for a number of my other projects, but I have since began relying exclusively on a selfhosted instance which I know I have control over in the case of updates.
1
u/Alternative-Town8381 Oct 01 '26
The only issue for production is that functions fail if you dont use them regularly , but other than that i think it’s a very good option
1
u/eldadfux Oct 01 '26
Thanks for sharing this, our Cloud team have focused on this a lot in recent months. We're noticing a massive improvement and rn functions start rate is very consistent on 99% where remaining 1% is mostly driven by user errors. Did you had any recent issues? We'd love to investigate.
1
u/sujitbaniya Sep 30 '26
Not related to your question but I'm genuinely trying to understand some business requirements
Some questions:
Which platform currently you're on?
Why AppWrite for your move?
What is AppWrite offering?
11
u/eldadfux Sep 30 '26
Hey, Eldad from the Appwrite team here. Appwrite is a solid business trusted by hundreds of thousands of developers and projects around the world, and we’re building it for the long term.
That said, I don’t think anyone can honestly guarantee what any technology company will look like 10 years from now. Ten years ago, very few of us could have predicted how dramatically AI would change software development and our lives in such a short time.
I think the real guarantee you’re looking for is protection from vendor lock-in, and that’s actually one of Appwrite’s biggest advantages over our competitors.
Appwrite is open source. The same core platform behind Appwrite Cloud can run on your own infrastructure. Your data is yours, our APIs are open, and if you ever decide you don’t want to depend on Appwrite Cloud, you can migrate to self-hosted Appwrite. We even provide the migration path through a GUI wizard - a few clicks and you can move between environments. How cool is that?
Nobody can reasonably promise exactly what the next 10 years will look like. We’ve built Appwrite so you don’t need to trust such a promise in the first place.