BärnHäckt 2026 — Beyond Money

A personal-finance dashboard built on bank statement exports: email/password accounts, and each account sees only its own transactions. A year of statements becomes income and spending per month, a category breakdown, a merchant ranking, and a filterable ledger.

Built for BärnHäckt 2026 on the PostFinance challenge.

Next.js 16 · shadcn/ui · Tailwind v4

• docs/BernHackt_Tech_Jury_Klickt_Gern_uf_Sache.docx
• docs/BernHackt_Tech_Jury_Klickt_Gern_uf_Sache.pdf
• docs/pitch.pdf
• docs/video_demo.mp4

Deployments

Branch	URL
development	https://dev.beyond-money.ch/
main	https://beyond-money.ch/

Setup

The SQLite file lives at ./data/app.db and is not committed, so a fresh clone needs the schema pushed before the app will run:

npm install
npm run db:push   # creates ./data/app.db and its tables
npm run dev

Then open http://localhost:3000 and create an account at /register.

Once an account exists, load the statements:

npm run seed

seed creates the demo account if it is missing and imports every .csv in scripts/seed-data/ into it.

Email	jeanine@example.com — override with SEED_EMAIL
Password	beyond-money-demo — override with SEED_PASSWORD

Importing your own statements

Any account can upload its own CSV from Account settings → Data → Import your own CSV. The file is read in the browser: the delimiter (comma, semicolon, tab or pipe) and the date, amount and description columns are detected, shown as a preview, and every one of them can be corrected before anything is sent.

Swiss, German and English number and date formats are all understood (1'234.50, 1.234,50, 1,234.50; 23.01.2026, 2026-01-23), as are statements that split money in and out into two columns. Uploaded rows are added to the account rather than replacing it, and a line already there is skipped — so re-importing an overlapping month is safe.

Access

Creating an account is currently disabled: /register renders a "sign-up currently disabled" notice instead of the form, and the register server action refuses before it looks anything up — a form is not the only way to reach an action, so the switch has to sit in both. It is SIGNUP_DISABLED in lib/auth-gate.ts; set it to false to hand the door back.

Signing in is untouched — an account that already exists works exactly as before.

LOGIN_KEY is the way back in while sign-up is off. Set it and /register renders the form again with an access-key field; register refuses anything that does not match, before it says whether the email is taken. Unset, sign-up is simply closed. Both /register states point a visitor at hi@beyond-money.ch to ask for a key — the address is site.contactEmail in lib/site.ts.

LOGIN_KEY	SIGNUP_DISABLED	/register
unset	true (today)	the notice
unset	false	open to anyone, as it always was
set	either	the form, plus the key field

Scripts

Script	Does
npm run dev	Dev server on port 3000
npm run build	Production build
npm run start	Pushes the schema, seeds the demo account if the database is empty, then serves the production build
npm run db:push	Apply db/schema.ts to the database (drizzle-kit push)
npm run db:studio	Drizzle Studio against the same file
npm run db:backup	Snapshot the database into data/backups/ (VACUUM INTO)
npm run seed	Import scripts/seed-data/*.csv into an existing account. -- --if-empty skips when the database already holds transactions
npm test	Vitest: CSV parsing, aggregation, import rules, auth, and per-account scoping

Environment

Copy .env.example to .env. Fill in the values, see .env.example.