Weweb is great for prototyping and fast iterations, but truly unreliable long term
When talking money, expect being treated like . Lost 7k+ because of Weweb ceo offered us 3month premium and then ghosted us .
Context:
We’ve been running our prod app for 2y on Weweb, with 100k+ monthly traffic
What’s the worst that can happen to a production app ?
To have your server down.
Well it happened 2 times last year only on Weweb, first when they pushed a release breaking existing production workflows, and more recently with the server failure. We lost more than 7k USD in adspend accross those 2 events. There is nothing we could have done on our side expect not rely on Weweb Fixes are SLOW, you can’t afford to be down for +48h on a production app.
But what’s even worse than having your server sown ?
Being treated like sh*t.
I get it, we chose Weweb, we know it’s still a small company and we can’t expect the same reactivity as major actors. But I could not
We’ve paid thousands of dollars to Weweb, and when we got down because of them, we naturally asked for a compensation.
The 2 times, the CEO offered us “3 month premium” and then ghosted us.
Being young and unreliable as a startup is ok, but disrespectful to loyal customers and showing you basically don’t care about user satisfaction is another thing.
What’s next ?
We’ll keep using weweb to make fast visual iterations, it’s really the best platform for prototyping, but guys, when the ceo himself does not care about loyal customers, don’t expect Weweb to be reliable for production app anytime soon.
to see more about @Raphael thoughts on communication read this post and notice the avoidance of supporting users and communicating with them.
Personally I am still happy with the uptime of wewebs services but as you mentioned clearly there is a lack of communication with the team when it is required and a refusal to acknowledge this as an issue.
General uptime is good, but when you’re running paid traffic/influencers you can’t afford to discover your app has been down for 48h during peak traffic and not be notified.
I have noticed this pattern you guys are describing on the community too, the posts with critique often get unanswered or worse.
One solution to this, if you still wanna keep using WeWeb could be self-hosting it and keeping track of your own uptime. Now with the cheap pricing it’s almost as if they wanted you to self host.
If a downtime happens, you have your own server, if you follow 0 reliability on WeWeb principle (no routing through WeWeb’s servers), you’ll be safe from anything that happens to them. If an editor bug happens, you can simply rollback your app to a previous version on your server, which you should keep somewhere.
I think that a 20$/month server is the best solution for peace in mind when spending 7K on ads casually
A lot of the critique is valid. With your size best practice should be to have an SLA in place. I wouldn’t even consider WeWeb for these sizes of apps if that wasn’t the case.
The solution Broberto suggests makes the most sense. Hope you can implement it to reduce risk and potential future losses.
. Lost 7k+ because of Weweb 
ceo offered us 3month premium and then ghosted us 
