A machine that stays on
A small Linux server (a VPS for a few francs a month) is plenty. That is what stays on, not your computer. Node.js version 22 or later, plus git.
Docs
Get it running, on your machine
Everything you need to install HaikoDev on your own machine: the file to download, the commands in order, how to update, and what to do when something breaks.
The download goes through the support window: the project is free, and your donation pays for the server and the time spent on it.
Getting started
The install in six commands
Copy them in order, in a terminal, on the machine that will host your board. Set aside an evening the first time.
git clone https://github.com/haikostudio/haikodev.git haikodev cd haikodev NODE_ENV=development npm install --include=dev npm run build node scripts/set-credentials.mjs npm start
The board then listens locally on port 7070. The full guide walks through every line, including the permanent service and the domain name.
Access to the repository
The repository is restricted: your GitHub account has to be invited, and your machine signed in.
An AI tool on your server
HaikoDev finds the AI tools already installed on your VPS. You can also add more from the settings, without rebuilding the installation.
Your own accounts
Connected tools are detected automatically. From the settings, you can add the ones you want to use.
Open sourceOn your own serverClaudeCodexCursorA memory that files itselfTokens countedOpen sourceOn your own serverClaudeCodexCursorA memory that files itselfTokens countedOpen sourceOn your own serverClaudeCodexCursorA memory that files itselfTokens countedOpen sourceOn your own serverClaudeCodexCursorA memory that files itselfTokens countedOpen sourceOn your own serverClaudeCodexCursorA memory that files itselfTokens countedOpen sourceOn your own serverClaudeCodexCursorA memory that files itselfTokens countedOpen sourceOn your own serverClaudeCodexCursorA memory that files itselfTokens countedOpen sourceOn your own serverClaudeCodexCursorA memory that files itselfTokens counted
Troubleshooting
When something breaks
The three failures that come up most often, each answered in one line.
The service starts, then stops
Nine times out of ten, a path or a user that does not match in the service file. The logs say so plainly.
The build stops on "tsc: not found"
The build tools were not installed: run the install again in development mode, then build.
GitHub refuses the clone
Either your machine is not signed in, or your account has no access to the repository yet. Check both, in that order.
Ready to install?
Download the archive, follow the six commands, and your board is running the same evening.