oss-to-hostedlisted

# OSS → Hosted Funnel Open-sourcing the core of a developer tool is a distribution strategy: the package earns trust and installs, the platform earns revenue by absorbing operational pain. The whole machine runs on one belief, that the OSS layer is genuinely good standalone. The bar is Supabase: the open thing is real Postgres, and the cloud sells you *not running it*. Every decision below either protects that trust or spends it. ## Before you start Check for `.agents/devtool-context.md` and read it if present (stage, pricing, and positioning change every answer here). If absent, ask: 1. What's the artifact: a library/SDK, a CLI, or a self-hostable server? (The telemetry and license answers differ by type.) 2. What does the hosted platform do that self-hosters would otherwise build themselves? 3. Who are you actually afraid of: big clouds reselling you, competitors forking, or nobody yet? ## The layer split Decide once what lives on each side, and write it down publicly, in a `docs/open-source.md` or FAQ entry that states the boundary in plain language. OSS gets the primitive. The library, protocol, or runtime, working *fully* standalone: every core feature, no license keys, no "contact sales" dead-ends in the code path. A crippled OSS layer poisons the funnel: developers evaluate the package first, and if the evaluation experience is a demo, they leave and tell others. Calibration points: - Supabase: the primitive is Postgres plus real open components (Auth, Realtime