Repository navigation
Research: boats.dev #1815
Description
Relocated from dezren39/darwin-nix#506 on 2026-10-28 - it was filed in the wrong repo; developing-today/code is its home. Original content follows, verbatim.
Problem
Drew named boats.dev in the 2026-10-20 program dump with no context beyond "we'll need to look into boats.dev". Research item: identify what it is and whether it fits the basement cluster + cloud program.
Source: idea register 2026-10-20 (goal stand-up-lab-cluster-talm-talos-cozystack-postgres-rustfs, open question 3).
Acceptance / first steps
- Identify boats.dev: product/company, what it does, pricing model (if any), current status.
- Note candidate fits with the program — cheap/free compute, storage, or especially egress (our scarce resource), dev tooling, or cluster software — or state plainly that none exists.
- Write findings back here and into the register; ask Drew where he saw it if the identification is ambiguous.
Open questions
- Where did Drew encounter boats.dev / in what context? (Asked in the register; research proceeds regardless.)
Acceptance criteria
- boats.dev is identified: product/company, what it does, pricing model if any, current status.
- A fit / no-fit judgment for the basement cluster + cloud program is recorded (compute, storage, egress, dev tooling, cluster software) — plainly stating if no fit exists.
- Findings are written back to this issue and to the 2026-10-20 idea register; if identification is ambiguous, Drew is asked where he saw it.
Activity
dezren39 commentedon Oct 28, 2026
Comments carried over from dezren39/darwin-nix#506 (verbatim, in order):
dezren39 - 2026-10-26T19:40:53Z
🤖 Intake review — fleet monitor, 2026-10-26 run
Still live: research not yet done; the body records that Drew named boats.dev on 2026-10-20 with no context beyond 'we'll need to look into boats.dev' (idea register, goal
stand-up-lab-cluster-talm-talos-cozystack-postgres-rustfs, open question 3).Related: dezren39/darwin-nix#508 (program epic) — any fit would land in that program; egress is the fit criterion to weight first, per the program's scarce-resource constraint.
Notes / risks: single-sitting research item (effort/s). The main risk is ambiguous identification — the body already prescribes the fallback: ask Drew where he saw it.
Suggested approach: identify, judge fit against the program (especially egress), write back to the issue and the register in one pass.
dezren39 - 2026-10-27T03:26:17Z
Answered (2026-10-25)
boats.dev research is done: it is a container-hosting service with no free tier - 7-day trial, then $20/mo prepaid; egress is uncharged. Recorded in the cluster program's idea register (2026-10-25) as a candidate for throwaway/test workloads, tracked under #1091. Left open for Drew to close.
dezren39 - 2026-10-28T20:02:39Z
Triage / research findings (task 2399, 2026-10-28): no site exists at the literal name; the nearest match is identified in full below, but it only partly matches Drew's own description — so this needs Drew's confirmation before anyone acts on it.
The literal name
boats.dev(plural) does not resolve — fetching https://boats.dev/ fails at DNS/connect, and no search result anywhere points at a product on that domain. There is no boats.dev product to identify.Nearest match: boat.dev (singular) — "boat"
boat host), CLI + HTTP API + Python/TypeScript SDKs. Agents (Claude Code, Codex, OpenCode) run inside; a harness outside can prompt/observe them. Sources: https://boat.dev/ and https://www.everydev.ai/tools/boat (fetched 2026-10-28).Why this is not a clean identification
Drew's register addendum (2026-10-25, idea register for the lab-cluster goal) describes boats.dev as "a container-hosting service with a free tier — a candidate for free container capacity". boat.dev is VM hosting (not container hosting) with a trial (not a free tier). The name and timing fit; the category and pricing model only half fit. It may be the same service loosely described, or a different service entirely.
Fit judgment (for boat.dev, if it is the one)
Ask
@drew — where did you see "boats.dev", and is boat.dev (boat, YC agent sandboxes) the service you meant? If yes, say so here and the register entry can be updated and closed out; if no, a hint about where it appeared will pin the right one. Escalating as
user/escalatedwith the research attached, per the issue's own acceptance step ("ask Drew where he saw it if the identification is ambiguous"). Register write-back is held until the identification is confirmed, so the register doesn't record the wrong service.developing-today commentedon Oct 28, 2026
CODE-749
dezren39 commentedon Nov 3, 2026
agent-note:v1
state: triaged (coverage pass)
Coverage pass 2026-11-03: reviewed in the fleet-wide per-issue pass (drift / overlap / already-handled / stale / blockers / ordering). Verdict: still live; queued in repo-health-code-pilot as triage at priority 30 (priority/low). If this is already handled at current main, the triage closes it with evidence; if it needs splitting, the triage files the split.
Found via: coverage pass 2026-11-03
dezren39 commentedon Nov 3, 2026
agent-note:v1
state: triaged — task 7735, lane code-d, 2026-11-03 (picked up and triaged this shift; this comment was rate-limit-blocked in-run and is posted via the action outbox, entry OB-2026-11-03-055)
Triage findings: boats.dev identification (researched 2026-11-03)
Verdict: identification is AMBIGUOUS — no live product exists at the literal name, and the closest match does not fit the description on file. Drew's answer to the open question (where did you see it?) is the blocker; see the ask at the end.
1. Literal
boats.dev— nothing there2. Closest match:
boat.dev(singular) — "Boat", by ASCII3. Why this stays ambiguous
Drew's own 2026-10-25 addendum in the 2026-10-20 idea register describes boats.dev as "a container-hosting service with a free tier — a candidate for free container capacity." That matches neither the literal domain (nothing there) nor boat.dev (VMs, not container hosting; trial, not a free tier). So either the name was pluralized/misremembered, or the service has since pivoted/renamed, or it is a different service entirely that is not findable under this name today.
Blocker / ordering
task 7735 completes as
triagedon this evidence.