Real Next.js code, written in the open.
Kalle writes the code a good team would, in a stack you know. Read every line, review every change, sync it to your own repository and keep building on it yourself.
A stack you already know
Kalle writes the code a good team would: standard tools, clear structure and no proprietary runtime.
Every line is there to read
Open any file while Kalle works, or after. The code is formatted, typed and named the way you would expect.
In your repository, commit by commit
Connect a GitHub repository you own. Every change Kalle makes lands as a readable commit with a clear message.
- feat: one-page checkouta41f2c9 · 10 min ago
- YOUfix: round prices to whole kroner9be07d1 · 1 h ago
- feat: gift cards at checkout3c11e8a · Yesterday
- chore: add browser tests for gift cardse72d4b0 · Yesterday
Review changes like a pull request
Each change comes with a summary in plain words and the full diff. Approve it, or ask for changes in the chat.
- app/checkout/page.tsx+84 −132
- app/checkout/actions.ts+41 −6
- components/CheckoutSummary.tsx+58 −0
- tests/checkout.spec.ts+37 −12
Migrations, not magic
Every change to the database is a numbered SQL migration in your repository, so you can see, run and review it.
alter table orders add column gift_message text;
Tests you can run yourself
The browser tests Kalle writes live in your repository and run with the usual commands.
Write code yourself. Kalle keeps up.
Push your own commits. Kalle reads the latest code before every change, so it builds on your work instead of overwriting it.
Run it anywhere, any time
Clone the repository and it runs like any Next.js project. Deploy it to your own servers or any host that runs Node and Postgres.
- Standard toolingnpm scripts, ESLint and TypeScript, nothing custom.
- Your environmentA .env.example lists every setting the app needs.
- Your databasePoint it at any Postgres and run the migrations.
Questions developers ask
Next.js with React and TypeScript, Postgres on Supabase, and standard libraries for payments and email.
Yes. Connect a GitHub repository you own and every change lands there as a commit.
Yes. Push your own commits, and Kalle reads the latest code before it changes anything.
No. Clone it and run it anywhere that runs Node and Postgres.
Ship faster without giving up the code
Every Appmake app is a real Next.js project you own.