Guides
Plain answers to questions developers ask about saving data from a static site or a frontend app. Each guide compares the usual options, including when jstash isn’t the right fit.
How to save user data in a static website
Browser storage, a small backend, Supabase or Firebase with security rules, or a per-user store. What each one costs you, and which to pick.
How to add per-user cloud storage to a Clerk app
Clerk signs people in but doesn’t keep their data. Clerk metadata and its 8 KB limit, Supabase, Convex, your own backend and jstash Apps.
localStorage vs cloud storage for small web apps
When localStorage is enough, where it lets you down, when to store data online, and how to use both.
How to save JSON from a frontend without exposing an API key
Any key in browser JavaScript is public. Safe ways to let a web page save JSON: a serverless function, a backend, per-user rules, or the person’s own login token.
How to add a database to a static website — and when you don’t need one
When a JSON file, a form service or localStorage is enough, and when to reach for a hosted database or jstash.
Comparisons
Honest side-by-sides: what each one does, when to use it instead of jstash, and when jstash fits.
jstash vs JSONBin.io
Free plans credited once or every day, private records, version history, browser keys, and which to pick.
jstash vs Firebase
Firestore with security rules against jstash Apps: the same task both ways, limits, and when to use each.
jstash vs Supabase
A table with row level security against jstash Apps: the same task both ways, limits, and when to use each.
About these guides
jstash writes these guides, and jstash is one of the options they compare. We say when something else fits better, and link the sources for facts about other products. Spotted a mistake? Email support@jstash.app.
To see what jstash does: jstash Apps gives each signed-in user of your app their own private JSON, and the Apps guide shows how to set it up. For a JSON document at a URL, see the bins API docs.