Laurence
8fd9b694f8
Persists the branding/commercial/infrastructure work (previously only in chat and on the live site) into version control. What changed: - docs/naming.md: due-diligence and the decision to brand the product Nightjar (OpenScribe domain/GitHub/trademark collisions; alternatives screened; why Nightjar). - docs/hosted-service.md: the commercial model - plan tiers (Self-host / Cloud Starter / Cloud Pro / Private), indicative pricing, backend mapping, and the build-to-sell roadmap (metering, billing, provisioning, DPA). - docs/infrastructure.md: backend infra plan. Primary option = self-host on the 3x Minisforum MS-02 cluster (one with an RTX 3050 6GB) fronted by a Cloudflare Tunnel, with node roles, the 3050 capacity reality, caveats, and a Hetzner cloud fallback. Provision-later. - site/: reproducible marketing-site source - block content for all 11 pages (rebranded to Nightjar), the navigation, the Contact Form 7 config (honeypot), the ApisCP SOAP helper (tools/apiscp.php, no secret), and a README on how the WordPress site is built and managed via the API. - state/: DECISIONS (Nightjar rebrand, hosted service, MS-02 backend), PROJECT (brand + commercial section), TODO (rename decision, trademark, mailbox, pricing, hosted-service build, infra provisioning). Why: - User asked to save everything to the repo. Captures the product rebrand, the commercialisation plan, and the infrastructure decision so a cold session has the full picture. Notes: - The repo is still named `openscribe`; the product/brand is Nightjar. A full codebase rename is deferred (tracked in TODO + docs/naming.md). - No secrets committed: the ApisCP API key is read from a local scratch file, never the repo. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
1 line
3 KiB
HTML
1 line
3 KiB
HTML
<!-- wp:heading {"level":1} --><h1 class="wp-block-heading">Open source</h1><!-- /wp:heading --><!-- wp:paragraph {"fontSize":"large"} --><p class="has-large-font-size">Every part of Nightjar is open, from the circuit to the summary. Build it, improve it, keep it.</p><!-- /wp:paragraph --><!-- wp:heading --><h2 class="wp-block-heading">The ethos</h2><!-- /wp:heading --><!-- wp:paragraph --><p>The person who records the audio should own it. That principle runs through the whole project. Nothing depends on a service that can be taken away, and nothing traps your recordings in a format only one company can read.</p><!-- /wp:paragraph --><!-- wp:list --><ul class="wp-block-list"><!-- wp:list-item --><li><strong>Own your data.</strong> Audio and transcripts stay on your storage.</li><!-- /wp:list-item --><!-- wp:list-item --><li><strong>No lock-in.</strong> Open hardware, open firmware, open API.</li><!-- /wp:list-item --><!-- wp:list-item --><li><strong>Reproducible.</strong> Anyone can build the whole thing from the documentation alone.</li><!-- /wp:list-item --></ul><!-- /wp:list --><!-- wp:heading --><h2 class="wp-block-heading">What is open</h2><!-- /wp:heading --><!-- wp:list --><ul class="wp-block-list"><!-- wp:list-item --><li><strong>Firmware</strong> for the ESP32-S3 device: recording, storage, sync and the on-device API.</li><!-- /wp:list-item --><!-- wp:list-item --><li><strong>Server</strong> that ingests recordings and runs transcription and summaries.</li><!-- /wp:list-item --><!-- wp:list-item --><li><strong>Mobile app</strong> for Android and iOS.</li><!-- /wp:list-item --><!-- wp:list-item --><li><strong>Hardware design</strong> and a bill of materials you can order.</li><!-- /wp:list-item --><!-- wp:list-item --><li><strong>3D-printed case</strong>, parametric so it fits your exact build.</li><!-- /wp:list-item --></ul><!-- /wp:list --><!-- wp:paragraph --><p>The firmware and software are copyleft, the hardware is open-hardware licensed, and the documentation is share-alike. Improvements stay open for everyone.</p><!-- /wp:paragraph --><!-- wp:heading --><h2 class="wp-block-heading">Build one</h2><!-- /wp:heading --><!-- wp:paragraph --><p>Off-the-shelf parts, a printed case, and a server you run. An ESP32-S3 with memory, an I2S microphone, a microSD card, a battery and a charging circuit. The firmware builds with common tooling, the case prints in a couple of hours, and the server runs on anything from a home NAS to a small cloud box.</p><!-- /wp:paragraph --><!-- wp:heading --><h2 class="wp-block-heading">The code is opening soon</h2><!-- /wp:heading --><!-- wp:paragraph --><p>The public repository is being prepared for release. Register your interest and we will let you know the moment it opens, so you can build, fork and contribute from day one.</p><!-- /wp:paragraph --><!-- wp:buttons --><div class="wp-block-buttons"><!-- wp:button --><div class="wp-block-button"><a class="wp-block-button__link wp-element-button" href="/contact/">Notify me when it opens</a></div><!-- /wp:button --></div><!-- /wp:buttons -->
|