Self-hosting guide
Get Writtt running on your own PC.
You don't need to be a programmer. This guide walks you through two paths: the easy one (just download and install) and the nerdy one (build it yourself from the source code).
Pick the path that feels right for you. Both end with the same result: Writtt, running on your machine, owned by you.
Easiest path — recommended
Just download and install
We compile Writtt and make it available as a ready-to-use file for every operating system. Click the button for your system, run the installer, and you're done. No terminal, no commands.
For the curious — build from source
Compile it yourself
Building from source means you read every line of code before running it. No surprises. This takes about 10–20 minutes if it's your first time.
A terminal (also called Command Prompt or console) is a text window where you type commands. Don't worry — you'll just copy and paste the commands below. Here's how to open it on your system:
🪟 Windows
Tecla Win + R
→ digita "cmd"
🍎 macOS
Cmd + Espaço
→ "Terminal"
🐧 Linux
Ctrl + Alt + T
ou busca "Terminal"
What you'll need to install first
Install Wails (the build tool)
After installing Go, open your terminal and paste this. It downloads the Wails tool that will compile everything:
go install github.com/wailsapp/wails/v2/cmd/wails@latestDownload the Writtt source code
This command copies all the code from GitHub to your computer (into a folder called 'writtt'):
git clone https://github.com/marcelomatz/writtt.git
cd writttInstall the JavaScript dependencies
Writtt's visual interface is built with React. This step downloads the visual building blocks it needs (fonts, icons, layout tools). It may take 1–2 minutes:
npm installRun Writtt (preview mode)
This launches Writtt directly from the source code. Use this to verify everything works before building the final file:
wails devBuild your own binary
When you're happy with the preview, run this to create a self-contained file you can copy anywhere:
wails buildWhy go through all this?
Pre-built binaries are convenient, but they require trust. When you build from source, you verify the binary instead of hoping it's clean.
Writtt has zero network calls at runtime — no telemetry, no pings, nothing. Building it yourself lets you confirm that claim directly in the code before you ever run it.
Questions, contributions, or issues — everything lives on GitHub.
View source on GitHub