Appwrite on X

Praise divides almost evenly between what ships and what people simply recommend. The releases people name are specific: one-click email setup with a sending-only API key by default, the official Helm chart for Kubernetes with managed databases, a one-click attack mode and lockdown for spam waves, real-time events that agents can subscribe to, and a serialization change one post credits with 69% less memory and 29% more throughput.

The recommending talk is about ease and dependability: auth and databases on Appwrite Cloud so the work stays on the product, less time spent on auth edge cases, and telling friends to try Appwrite instead of rolling their own backend. 4 people like getting auth, database, storage and functions in one place; one calls a single home for management services hard to find.

Two posts offer a trade-off rather than praise: letting Appwrite pick a scheduling offset suits an hourly cache refresh, and a resent verification code does not immediately cancel the old one, which changes what interface copy can promise. The one disappointment is a student who had planned to subscribe and found per-project pricing on the $25 plan.

Cost is where the section's people are. One comparison prices storing 10 TB and serving 50 TB a month: Railway at $150, Tigris and Bunny around $550 to $600, and Appwrite and Convex over $6,000. Others say vector databases are not free to create, and that hostile traffic against functions carries a second-order cost, where "a single bad request" can blow up a cloud bill.

Dart comes next in volume but is the work of one self-hoster: they need Dart 3.12 or newer for the genkit_anthropic SDK, the docs list neither 3.12 nor 3.13, the self-hosted console tops out at 3.11, and adding dart-3.12 to the runtime environment variables did not make it appear in the console dropdown. Replies point to self-hosted 1.9.5 and above; the same user later posted that upgrading from 1.9.0 to 1.9.6 brought Dart 3.12 straight away.

The education plan is one student's complaint here: a GitHub Developer Pack that promised to last through college showed 23 days left, per-project charges on the $25 plan, and, they say, nowhere to migrate.

Railway carries the section's reach: Appwrite's own founder calls it "an Appwrite competitor in many areas" and wishes its engineers well. An operator of a small European PaaS groups Railway, Appwrite and Render as platforms facing the same security load, and one post calls Appwrite "Railways alternative".

The picking-between talk is broader than any one rival: a poll asks developers to choose a favourite BaaS from Supabase, Firebase or Appwrite, a long Chinese-language post weighs Appwrite's free tier against Firebase and likes that exceeding limits freezes a project rather than charging, and a hosting round-up lists Appwrite among the options still to try.

The roll-your-own comparison is about skipping a homemade backend: users say they tell friends to try Appwrite instead of building their own, one crediting MCPs with making 10+ websites easy to manage.

Storage is measured rather than argued: one benchmark puts Tigris first on a cold start with Appwrite next, and that author's price table has Appwrite above $6,000 a month at 10 TB. Single posts name Cloudflare as the host someone chose after looking at Appwrite, and put Appwrite over Firebase on a self-host list.

The Dart thread: a self-hoster needs Dart 3.12 for the genkit_anthropic SDK, finds the docs list neither 3.12 nor 3.13, and asks whether a workaround exists or a runtime bump is planned; they later ask whether simply upgrading is enough. Help in the thread says self-hosted 1.9.5 and above carries the new runtime and that runtimes can be added through environment variables.

Two people ask for news rather than features: one about a new Coolify template, one noting the PHP update is live and asking what follows. The rest, one person each: when DocumentsDB and VectorDB reach stable and whether volume storage, an MCP gateway and an inference/token gateway are on the roadmap; how account linking handles the same email arriving through a different provider, "before adding six more buttons"; whether attack mode blocks mobile clients and signed webhooks along with spam; whether event subscriptions can be filtered by function or failure type; and whether Postgres on Appwrite supports Realtime.

The Kubernetes asks are about upgrades as much as setup: an official chart should make setup less of a hassle, and community charts "always break on a different version bump". One user had been waiting for proper K8s support. The same day's posts greet the official chart, with managed databases and Functions included, as a big one for self-hosters.

The remaining wishes are single voices: Telegram as a sign-in provider; Azure Blob Storage and AWS S3 as storage backing among the providers people are already discussing; a nudge that Appwrite "might need to upgrade its VCS soon"; and coverage of permissions and session expiry for paid, time-bound agent sessions, which one team treats as part of its product. None of these asks comes with a second person backing it, so they read as requests rather than demands.