Internal Tool Stack

A deliberately minimal stack for internal dashboards and small-team tools: auth, a database, a fast frontend. No more.

What it is

The small stack on purpose. Internal tools don’t need CDN-scale architecture, they need to exist, log the team in, and read/write data reliably.

How it fits together

Team member
   │  (login, create/read/update)
   ▼
Astro app ──► Supabase  (Auth + Postgres, row-level security per role)

The pieces

• Astro — pages and server routes for forms and tables.
• Supabase — auth and the database, with row-level security so people only see what they should.

When to use it

Replacing a fragile spreadsheet-and-Slack workflow with something real and fast.

Build it

Auth first (lock it down), then the data screens. Public intake forms reuse the waitlist pattern.