@@ -202,26 +202,6 @@ It's also a good choice if you:
202
202
- Prefer to manage authentication, database, storage, and hosting in one place
203
203
- Want rollback support, deployment visibility, and runtime logs built-in
204
204
205
- # Appwrite Sites vs Vercel: feature comparison
206
-
207
- | **Feature** | **Appwrite Sites** | **Vercel** |
208
- | --- | --- | --- |
209
- | Full-stack integration | Yes | No |
210
- | Static hosting | Yes | Yes |
211
- | Server-side rendering | Yes | Yes |
212
- | Git-based deployment | Yes | Yes |
213
- | Manual deployment via UI | Yes (drag-and-drop) | No |
214
- | Preview deployments | Branch, commit, PR | Branch, commit, PR |
215
- | Rollbacks | Yes | Yes |
216
- | CORS with Appwrite backend | Automatic (trusted by default) | Manual setup |
217
- | API key injection | Automatic (build + runtime) | Manual setup + rotation |
218
- | Environment variables | Build + runtime, auto-injected Appwrite vars | Build + runtime, manual |
219
- | Wide framework support | Yes | Yes |
220
- | Templates | Yes (multi-framework) | Yes (mostly Next.js) |
221
- | Timeout configuration | Yes (up to 30s) | Yes |
222
- | Logging | Build logs, request logs, SSR console output | Build + function logs |
223
- | Custom domains | Yes | Yes |
224
-
225
205
# Final thoughts
226
206
227
207
Both Appwrite Sites and Vercel are great platforms for deploying modern web applications. But they're built for slightly different workflows.
0 commit comments