← Tool Garage
Data station
Google Sheets
The database you already know how to use, and a perfectly honest place to start.
1. Learn it
- A sheet is a table: columns are fields, rows are records. That is a database, conceptually.
- Starting here is not cheating — it's the fastest way to learn whether your data shape is right.
- It stops working when several people write at once, when you need logins, or past a few thousand rows.
- It has an API, so an app or an automation can read and write it while you keep the familiar view.
- Moving to a real database later is easier when your columns were sensible from the start.
Cost: Free.
2. Practice it
Simulated — nothing real happensDesign your table before you build anything
Write the column names for the main thing your app stores. Include an ID, a created date, and who it belongs to.
3. Connect it
Real — your own account- 1Make a new sheet and add your practice columns as the first row.
- 2Add five realistic rows, including one awkward one — a missing value, a weird name.
- 3Connect it to an automation tool before you consider writing code against it.
MessyDev never signs you up, spends your money, or touches your accounts. You do that part.
4. Use it
Prototypes, internal trackers, and the source data behind an automation.
Honest alternatives
There is no single correct stack. Any of these would be a reasonable choice instead.
- Airtable
- Notion
- A real database once people log in
More in Data
SupabaseYour app's memory: a database, logins, and file storage in one place.NeonA Postgres database on its own, with branches like code.ZapinnerOne API that cleans, checks and de-duplicates messy data before it reaches your app.File storageWhere uploaded pictures, PDFs and videos actually live — not in your database.AirtableA spreadsheet that behaves like a database, with real field types and links between tables.NotionDocs and simple databases in one place — where your plan, notes and content live.