for founders

Get your Sunday back.

vinOS runs the busywork that eats your weekend — inbox triage, PR review, morning brief, evening recap. Agents run 24/7 on your laptop. 80% on a local model. Free.

Download vinOS 2.0.5 See a routine →

Three things that ship the day you install it.

Outcome first. Not features. Every one of these is a shipping routine in v2.0.5 — disabled by default, one vinos-routine enable away.

A brief on your login screen every morning.

Reads your inbox, calendar, and GitHub the moment you wake the laptop. Local model. Costs a penny.

day-brief · llama3.1:8b · 06:00

PR reviews while you're in a meeting.

Every 30 minutes. Local model triages, Claude only when a diff warrants judgment.

github-review · route = "auto"

An hour of focus with everything muted.

Super+F → DND on, notifications silenced, 25-minute timer visible.

focus-mode · Super+F

The proof — a routine you can read.

Every routine is a TOML file. No YAML DSL. No dashboard. Read it in a minute, edit it in five, share it with your team by committing it.

.vinos/routines/day-brief.toml toml

[routine]
name        = "day-brief"
schedule    = "0 6 * * *"      # daily · 06:00 local
agent       = "brief"
route       = "auto"           # 80% local · escalate on complexity

[model]
local       = "llama3.1:8b"    # ollama · default
premium     = "claude-3-5-sonnet"

[tools]
allow       = ["calendar", "inbox", "github", "weather"]

[out]
render      = "markdown"
sink        = "~/.local/state/vinos/brief.md"
open_on_login = true

[budget]
max_tokens  = 8000
max_dollars = 0.10             # per run · hard cap

Questions founders actually ask.

How much time back?

Depends how much of your Sunday is currently spent doing what a routine can do. If your Sundays look like inbox → PR review → weekly recap → planning for Monday, the shipping starter set covers all four. Expect the first month to be tuning schedules and prompts; steady state after that.

What if my API bill blows up?

Every routine has a [budget] block — max_dollars per run, max_dollars_per_day across the routine set. Exceed the cap and the runtime skips the call (behavior configurable: skip, degrade, or local_only). Hard-enforced by the runtime, not the model. The default starter set caps you at ~$3/day.

Do I need to be technical?

Yes, but not sysadmin-level. If you can flash a USB, edit a TOML file, and read a shell command's output, you're set. The starter routines ship enabled-but-idle: turn them on one at a time with vinos-routine enable day-brief.

Can my team share my routines?

Yes — routines are portable. Drop a .vinos/routines.yaml in your repo, commit it, and anyone on your team who's booted vinOS runs vinos-routine load . to install the same set on their machine. Versioned in git, reviewed in PR.

What about privacy?

Local-first. The default route sends most calls to a local Ollama model — your inbox contents, calendar events, and repo diffs never leave the machine unless a routine explicitly escalates to a frontier API (and even then, only the specific prompt is sent, not the full context). Set route = "ollama" on any routine to force local-only.

Boot into your agents.

Flash a USB. Boot any x86_64 machine. In fifteen minutes your first routine is running.

Download vinOS 2.0.5 Browse routines →

Uninstall: pacman -Rns vinos-*. No lock-in. MIT-licensed.