Harbor is a launcher binary, a JSON config, and a one-line CLI push. No SDK, no build step, nothing to host. Here's the whole thing, end to end.
Ship harbor-launcher.exe next to your game. It replaces your current launcher, or sits in front of a bare exe.
Point it at your game executable, name it, theme it, turn modules on. One file, checked into your repo.
Write a patch note in markdown and run harbor push. It lands in every player's launcher before their next session.
Web app coming soon{
"app_id": "paracosm/dierobot",
"game_exe": "./Windows/DieRobot.exe",
"branding": {
"game_name": "Die Robot",
"studio_name": "Paracosm",
"play_button_text": "Play"
},
"modules": [
{ "type": "patch_notes", "enabled": true },
{ "type": "news", "enabled": true },
{ "type": "dev_comments", "enabled": true }
],
"theme": {
"accent_color": "#FF6B00"
}
}Harbor is configured by a single file in your repo. You version it like code, review it like code, and ship it like code. No SDK. No build step.
Modules, theme, play button, and social links are all declared in harbor.config.json. Push it with the Harbor CLI today. A web app for non-engineers is coming soon.
Read the docs →Every module is a self-contained tab in the launcher. Turn on what you need. Anything you don't enable never ships in the binary.
Ship notes in markdown. Players see what changed before they hit Play.
Announcements, blog posts, and livestream reminders. Your studio channel.
Short, signed notes from the team. The changelog, in human terms.
In-launcher questions with open, multiple-choice, and NPS formats.
Collect player emails and tester interest with one click, gated by branch or key.
Invite, OAuth link, and live server stats, right in the launcher.
Let players pick the next feature, boss, or cosmetic.
New modules land every few patches. Tell us what you'd put in front of your players.
The full integration is in the Quickstart. Or skip ahead and email us about your game.