Turso or Supabase for a small side project that's mostly reads?

At 3000 rows with you as the only writer, both are fine and speed won't be your deciding factor. Pick on what you'd miss:

• Supabase gives you auth, storage for trail photos, and a dashboard to edit rows. If you ever want users to submit trails, it's all there.
• Turso is nice if you want plain SQLite with the file locally in dev and replicas close to users. You'd bring your own auth.

If you already know Supabase, stay. The "edge is faster" part saves milliseconds that nobody reading about trails will notice.

Honestly for mostly-reads at this size, a static site that rebuilds when you edit is faster and cheaper than either. But if you want a database, what Fatima said.

Used Turso for a similar hobby thing. The local-file dev loop is lovely, but I ended up writing my own login and image upload, which Supabase would have given me for free. For your plan to let users add trails, Supabase.