# Nightjar hosted service (commercial) How 12 Hobbies Studio commercialises the open-source project: a managed backend so people can use Nightjar without self-hosting. The device and app stay open; the studio runs the transcription, summaries, storage and API. Status: **marketing site live, service in preparation.** No billing/signup yet; the site captures leads (register interest). Pricing below is **indicative**. ## Plan lineup (live on the site) | Plan | Price (indicative) | AI backend | Notes | |------|--------------------|-----------|-------| | **Self-host** | Free, forever | your own | full source + docs, community support | | **Cloud Starter** | from GBP 6/mo | commercial API | 10 hrs audio/mo, 10 GB, email support | | **Cloud Pro** | from GBP 18/mo | commercial API | 40 hrs/mo, priority, 100 GB, team sharing | | **Private** | from GBP 39/mo | self-hosted open models | audio never touches a 3rd-party AI; DPA | The Cloud tiers use best-in-class commercial AI (cheap per-minute, good margin). The Private tier processes everything on our own hardware (see `docs/infrastructure.md`) for a privacy / sovereignty guarantee. All hosted data kept in the EU/UK. ## Placeholders to confirm before launch - **Contact mailbox:** the site's forms/CTAs use `hello@12hobbies.studio` - create that mailbox or change it. - **Real pricing + quotas:** the numbers above are indicative. - **Trademark clearance** for "Nightjar" (see `docs/naming.md`). ## Roadmap to actually sell it (not built yet) - Metering (hours of audio, storage) per account. - Signup + billing (e.g. Stripe) wired to plan entitlements. - Provisioning: create a tenant, route jobs to the right backend (commercial vs Private node), enforce quotas. - Provision the backend infra (`docs/infrastructure.md`) at first beta / paying users. - Data-processing agreement + retention policy for the Private tier. ## Marketing site Built in WordPress on ApisCP (`howler.qsplace.co.uk`), served at `nightjar.12hobbies.studio`. Reproducible content and build notes are in `site/`.