The open-source tool from Haiko Studio

Beluga is the vibe coding tool I built at Haiko: you describe what you want, AI agents build it on your server, and you stay in control of what goes live. I made it for myself. Today my whole studio runs on it.

beluga.haikostudio.cloud

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.

01

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.

02

Tasks that run on the server

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.

03

Every change tracked and archived

Each card keeps its plan, its report and its checks. The changelog writes itself, day after day, in plain words.

04

Code versions managed for every project

Every project has its repository, and every task its own copy of the code. I always know what changed, and I can roll back.

05

Project management and notes

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.

06

A vault for every key

Passwords, keys and server access live in a shared vault. Agents find what they need on their own, without anyone typing it in again.

07

Messaging with my clients

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.

08

Tailor-made backups

The websites I manage are backed up automatically, with a recipe fitted to each one. That lets me offer the service to my clients.

09

Website monitoring

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.

It gets framed

Request

The card is born here with its conversation. The need, configuration and understanding are refined without touching code; a start can also be scheduled.

It gets prepared

Plan

The complete plan is written and reviewed here. The card stays at this stage until you approve it and start the work.

It works

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.

It gets read

Report

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.

It waits for you

To deploy

Approved cards form the next batch. Deployment can stay manual or be automated per project; production remains a separate, tracked stage.

It gets filed

Archived

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.

9services brought together in one tool for everyone
0computers to leave on: everything runs on the server
3AI engines behind the same interface: Claude, Codex, Cursor
5interface languages

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.

The studio

An independent studio, in the canton of Vaud

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.

The problem

The AI wrote the code, I did everything else

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.

The answer

One tool for everyone

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.

Today

All my work runs on it

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.

  • A project can now span several repositories, each with its own settings, tracking and grouped release
  • A deployment’s progress is visible at a glance, and the project list is lighter on phones
  • Sending a video or file in the conversation now shows its upload progress
  • Claude accounts are now used in order, spreading the load instead of draining the first one

  • Each agent step — question, memory, tool — now appears in its own illustrated box, easier to read than a wall of text
  • The in-depth plan becomes the default setting for a new card

host it yourself

Pull the project, install it on your server, plug in your accounts. The whole code is yours, and the guide skips no step.

Support the project

A donation to keep Beluga going

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.