App Platform for Node.js

Vs Vite (default SPA/library toolchain) and Rolldown/Oxc-adjacent Rust tooling: OJ is the agent/CI-memory-oriented React builder, not the ecosystem default yet. Young Lovable Labs surface — verify plugin compatibility before you rip Vite out of a production app.

Self-hosted Appwrite is a stack of many Docker containers, so plan for upgrades, backups and monitoring yourself; major-version upgrades have migration steps. You are buying into Appwrite's APIs and permission model, which makes leaving harder than with plain Postgres. The managed Appwrite Cloud is a separate commercial offering.

Sync, auth and collaboration come from Dexie Cloud, a separate commercial service; the library itself is local only. IndexedDB storage can be evicted by the browser under storage pressure unless you request persistence. Queries are index-based, not SQL.

Decorators and reflection metadata feel heavy next to schema-first tools like Drizzle or Prisma, and type safety for complex queries is weaker. Maintenance went through quiet years before the 1.x releases, so some old issues linger. Lazy relations and migrations need discipline.

The index lives in memory in your process, so it fits small to medium datasets, not millions of large documents. The last release was December 2025 and the last code change July 2026, so the open-source library moves slowly while the company focuses on Orama Cloud. GitHub does not detect the license; the LICENSE.md text is Apache-2.0.

v9 requires Node 22.13+ and is ESM-only, so upgrading from v8 needs code changes. Cookies cap out at about 4 KB, so store IDs, not big objects. Stateless sessions cannot be revoked server-side without extra bookkeeping. It manages sessions; login, OAuth and passwords are up to you.

The GraphQL API runs on Hasura, so you inherit Hasura's permission model. Self-hosting the whole stack in production is possible but the hosted Nhost platform (free tier plus paid plans) is the main path. Smaller community than Supabase.

Opinionated by design: heavy visual customization means fighting the defaults. React only. Releases are occasional.

Fewer built-in features than Sonner, such as stacking and action buttons, and slower development. React only.

Smaller than TanStack Query in features like devtools and fine cache control. With React Server Components, much fetching moves to the server, so you need SWR less in new Next.js apps.

The company now also promotes an AI agent product, and core releases have slowed since April. The abstractions take time to learn, and you still write all the UI code.

ESM only. Releases are fast, so pin versions and read changelogs. It is a framework you set up yourself, not a hosted docs platform like Mintlify.

Development has slowed: no release since December 2025. It is tied to Next.js, and moving between major versions has meant real migration work. Fumadocs is the more active alternative.

Setting it up is more involved than a plain Markdown folder, and the smoothest editing path runs through TinaCloud. Self-hosting the backend means wiring your own database and auth. Schema changes need a rebuild.