BootSignal

Positioning

BootSignal is an embeddable widget platform — one shared loader (bootsignal.js) adds widgets like comments and likes to any site. No build step, no backend. Sign-in (shared Google account), storage, and i18n (ko/en/ja) are included, with zero host code changes. More services keep getting added.

• Two formats — embed (script widgets: comments, likes…) and unlock (credit-gated content/paywall, coming). One site hosts multiple services.
• Self-serve registration — sign in, register a site (site-id) you own from the dashboard, and start embedding immediately.
• Shared sign-in — visitors sign in with Google to comment or like; the same account and credit wallet work across every family service.

Migrated from oos.kr (2026-05-31); prompt marketplace → comments → multi-service widget platform (comments + likes) (2026-06-07).

Pricing — Usage-Based

No subscriptions. Billing is based purely on comment usage.

• Each site gets a monthly free allowance of comments — nothing is charged within it.
• Beyond the free allowance, each comment debits credits per comment from the site owner’s shared wallet (mrlatte).
• Credits are topped up via Polar.sh, shared across all services, and never expire.

System Architecture

flowchart LR
    Tools["Tool catalog
(static data)"] --> Build["Astro build
(static)"]
    Build --> S3["S3 web/"]
    S3 --> CF["CloudFront
bootsignal.com"]
    CF --> User["Developer"]
    User --> Firebase["Firebase Auth
+ Firestore (credits)"]
    Polar["Polar.sh payment"] --> WH["Cloud Function
webhook"]
    WH --> Firebase

• Frontend: Astro 5 (static, /en·/ko) + React 19 (client-side auth & credits)
• Auth: Firebase Auth (Google)
• Credits/Unlocks: Firestore named DB bootsignal — users/{uid}/credits, unlocks/
• Payment: Polar.sh → Cloud Function webhook → credit top-up
• Hosting: S3 + CloudFront

Current Status

• Status: Live. Verifying credit checkout flow and product setup
• Next: Launch form + waitlist script-tag widgets to open the acquisition channel