Forkhaus logoForkhaus

00 / About Forkhaus

A letter
from the studio.

Why this place exists, who it's for, and what we believe about making software with AI as a collaborator.

Public labOpen archiveEducational software
Read the letter
Based at
Aalborg University
Founded
2026
Status
Public beta

01 / Origin

How this place came to be.

I have always carried around ideas for small, helpful tools — solutions to little frustrations, half-formed concepts, things I wished existed. The problem was never imagination. The problem was that I could not really make them real. I could imagine the house in detail, but I did not know how to build it.

Then I tried vibe coding for the first time, first in Lovable and later in tools like Cursor, Claude Code, and Codex, and it felt like a door opened. Suddenly I could build through conversation. I could try things, change direction, iterate quickly, and prototype ideas without needing everything mapped out in advance. What used to stay in my head could finally take shape on screen.

That was the beginning of Forkhaus. It came from the excitement of realizing that building software could be more conversational, more accessible, and more experimental than I had assumed — and from wanting a place where that process could be shared, studied, and built upon by others.

02 / The practice

What I mean by vibe coding.

Vibe coding is building software through fast, conversational collaboration with AI, guided by judgment rather than rigid planning.

Putting thoughts and ideas into functions and features before finishing your coffee. It is less about typing and more about steering — describing intent, reading what the machine offers back, and deciding together what the next move should be.

When it works, it collapses the distance between an idea and a running thing. When it fails, it fails visibly, and you learn something. Either way, the practice belongs in the open.

forkhaus.dev/

Forkhaus / a public lab

Educational software,
with the decisions still visible.

Working tools, forkable material, honest notes from the bench.

Fig. 01 — The Forkhaus home page. Shapes instead of stock photos.

03 / Invited

Who it is for.

Students

Curious about AI-assisted building but unsure where to start. Forkhaus is a reading room, a sketchpad, and a gallery — all at once.

Educators + researchers

Looking for tools that are both usable in the classroom and transparent about how they were made. Fork any of them — they were written to be taken apart.

Practitioners

Already vibe coding. This is a place to publish what you've made, share the process honestly, and keep the archive honest for everyone after you.

A belief

Good software practice should be visible, reusable, and shared.

04 / Principles

What we hold to.

01

Software as practice, not just product

We care as much about how a tool was made as what it does. The bench matters.

02

Document decisions, not only outcomes

Every project shows why it exists, what was tried, what was dropped, and what's next.

03

AI is a collaborator, not magic

Vibe coding shortens the loop between thought and artefact. Judgment still has to come from a human.

04

Make things forkable

Everything is written to be copied, bent, remixed. The name is not an accident.

05

Unfinished work can still be valuable

A half-built prototype with clear intent teaches more than a polished black box.

06

Educational software should be understandable and personal

It's built by people with names, for people with names. Not a platform — a place.

05 / Boundaries

What Forkhaus is not.

Not

A showcase of polished apps

Instead

A working archive where process is always visible.

Not

A hype space for AI-generated software

Instead

A careful, opinionated practice with AI as a collaborator.

Not

A private dumping ground of half-finished ideas

Instead

A public record where intent and decisions stay with the code.

06 / In practice

A project, shown plainly.

forkhaus.dev/projects/drawbook

01 / Project · teaching

Drawbook — a sketchpad for classroom maths.

A minimal canvas where students and teachers think through geometry together, in real time. Built in a weekend with Cursor.

ReactSupabaseCursor

Problem

Classroom whiteboards disappear the moment a lesson ends. Students can never revisit the reasoning that got them there.

Fig. 02 — A project detail page. Problem, process, tools, roadmap — all visible.

Every project on Forkhaus follows the same rhythm: the problem it solves, how it was built, the tools it leans on, and what might change next. No heroic narratives. Just enough structure to let someone else take the wheel.

If that sounds useful, or if you recognise the itch to make something small and real — keep reading.

07 / Closing

If you're curious, start anywhere.

Read a project. Fork a prompt. Borrow a guide. Submit a sketch of something you're working on, even if it's rough — especially if it's rough. This is a lab, not a gallery.

With warmth,

Jonas

Founder of Forkhaus · Aalborg

08 / Doors

Three ways in.

Pick the one that fits where you are today. You can always come back through a different one.

Browse

See what others are making.

Working tools from the archive — with problem, process, and decisions shown.

Open
Contribute

Share your practice.

Notes, guides, prompts, skills. The reusable material that helps ideas travel.

Open
Submit

Publish something you built.

Small, rough, or ambitious — if it teaches, it belongs here.

Open