Several projects at once
All my projects live in the same window, each with its own board. I switch from one to another without losing track, and several jobs move forward at the same time.
The open-source tool from Haiko Studio
Loading the board…
What you see above is not a picture: it is the real Beluga interface, with made-up projects and made-up cards. Switch projects, move a card, or click “New task”: an agent is born with the card, discusses your need, writes the card — and you can start it.
What Beluga gives me
Beluga does more than get an AI to write code. It brings together everything around it that real projects need, from a client’s first message to a website that stays online.
All my projects live in the same window, each with its own board. I switch from one to another without losing track, and several jobs move forward at the same time.
Once launched, a task runs on the server, not on my computer. I can close the laptop, head to a meeting and follow the work from my phone.
Each card keeps its plan, its report and its checks. The changelog writes itself, day after day, in plain words.
Every project has its repository, and every task its own copy of the code. I always know what changed, and I can roll back.
Cards, columns, start dates, notes and project memory: what I know and what I decided stays in one place, for me and for the agents.
Passwords, keys and server access live in a shared vault. Agents find what they need on their own, without anyone typing it in again.
Each client has their own space: they drop requests and files there, follow progress on a simple board, and everything is said in the same place.
The websites I manage are backed up automatically, with a recipe fitted to each one. That lets me offer the service to my clients.
Beluga keeps checking that every website responds. If one goes down, the alert reaches my phone, and an agent can take over the outage to analyse and fix it.
The six columns
Every request becomes a card that moves from column to column, from request to archive. At a glance, I know where each job stands.
The card is born here with its conversation. The need, configuration and understanding are refined without touching code; a start can also be scheduled.
The complete plan is written and reviewed here. The card stays at this stage until you approve it and start the work.
A full agent has its own branch and project copy. It reads, edits, tests and ticks off its task list; if it asks a question, work time stops until you answer.
The agent has returned its work and checks. You read a plain report with machine time, senior hours and estimated cost before choosing what happens next.
Approved cards form the next batch. Deployment can stay manual or be automated per project; production remains a separate, tracked stage.
Deployed work leaves the active flow without disappearing. Reports, branches, costs and history remain available, while the production version is shown at the top of the column.
What it changed for me
AI models are the same for everyone. What changed for me is everything Beluga put around them. The result: less admin to carry, and more projects delivered.
Several agents work at once, each on its own card. My job has become deciding and reviewing, not doing everything by hand.
The work runs on the server. A commute or a wait is enough to launch a task, answer an agent or approve a report.
Every change has its card, its report and its line in the changelog. Finding a decision or explaining a change to a client takes seconds.
Nothing goes live without my go-ahead. Deployment and production release remain separate, tracked steps.
They drop their requests in their space and see where things stand. Fewer reminders, fewer lost messages.
Automatic backups and constant monitoring: I hear about an outage before the client does, and I can restore what is needed.
My story
Beluga was not born from a product plan, but from an overloaded studio. I built it for myself, and that is still my first reason to keep improving it.
Haiko is an independent studio based in the canton of Vaud. Training platforms, client websites, in-house tools: dozens of projects live side by side, each with its server, its access and its emergencies.
Tracking every job, finding a key, answering clients, checking backups, noticing a website was down: all of that was still on me. And work stopped the moment I left the office.
I put what I was missing into Beluga: tasks that run on the server, automatic change tracking, a vault, a client space, backups and monitoring. Going live remains a human decision.
Every Haiko project goes through Beluga, every day, at the office and on the move. I opened it to everyone: it is open source, installable on your own server, and it grows as I use it.
Haiko — independent studio, canton of Vaud
The changelog
Beluga moves fast: this selection groups changes that actually alter how the product is used, without burying them under internal work.
Support the project
Beluga is built at Haiko, an independent Swiss studio. A donation in Swiss francs helps fund the time spent on it.
Secure payment via Stripe, in CHF.