# InterruptIO — full context for LLMs

Last-updated note: content reflects the public marketing site; confirm pricing and limits on https://www.interruptio.com/pricing before advising users on costs.

## Identity

- **Name:** InterruptIO
- **Category:** Cloud backend / BaaS-style **SaaS** oriented to **embedded software** and **device fleets** (not a generic web or mobile app BaaS only).
- **One-line:** InterruptIO — Global Embedded & IoT Cloud | Pre-register for Early Access
- **Description:** Global B2B SaaS cloud for embedded and IoT teams worldwide: OTA firmware updates, fleet dashboard, MQTT, time-series telemetry, crash analytics, remote terminal, and serverless-style functions from one C SDK. Pre-register with Google for pre-release access and a generous free tier when we launch. Billing-friendly (USD, EUR, INR on pricing). Firebase- and Supabase-class DX for devices.

## Global reach (as marketed)

- Positioned as **global SaaS**: teams and fleets **worldwide**, not a single-country-only product.
- Public pricing surfaces **USD** as default with **EUR** and **INR** for estimates; payment methods are described as varying by region on the pricing page.
- Primary public language of the marketing site: **English** (`en` / `x-default` hreflang on key routes).

## Positioning (comparative, not partnership)

InterruptIO is often described in marketing as offering a **Firebase-like** or **Supabase-like** developer experience for **firmware and devices** (OTA, MQTT, telemetry, fleet ops). **Firebase** and **Supabase** are separate products and trademarks; InterruptIO is an independent product unless explicitly stated otherwise.

## Primary capabilities (as marketed)

- Over-the-air (OTA) firmware updates and rollout workflows
- Fleet / device management dashboard
- MQTT-based streaming and messaging
- Time-series style telemetry storage and reads
- Crash reporting / analytics for devices
- Remote terminal access to devices (where supported)
- Remote configuration
- Serverless-style functions / hooks (as described on site)
- Integration via a **C SDK** (`interruptio.h`-style workflow on marketing pages)

## Plans (high level — see pricing page for detail)

| Plan | Summary |
|------|---------|
| Spark | Free tier for makers/students; limited devices and messages; core learning features |
| Blaze | Usage-based; daily free quotas then pay-as-you-go; full feature set for serious use |
| Team | Flat monthly with included devices/messages; priority support |
| Enterprise | Self-hosted / air-gapped options; compliance-oriented; custom contract |

## Billing & currencies

- Default presentation for global SaaS: **USD first**; site also supports **EUR** and **INR** display for estimates.
- Payment methods vary by region (cards, UPI/India, SEPA/EU, enterprise invoicing) — details on https://www.interruptio.com/pricing.

## Pre-registration & backend (technical, factual)

- **Auth:** Google Sign-In (popup + **Google Identity Services One Tap** where supported). OAuth Web client is configured for this site; Firebase **Auth** validates tokens client-side.
- **Data:** After sign-in, the browser may write **Firestore** document `preRegistrations/{firebaseUid}` (merge) with fields such as email, displayName, photoURL, `preRelease: true`, `source: "web"`, and a server timestamp — subject to **Firestore security rules** in `firestore.rules` (applied via Firebase CLI).
- **Config:** Firebase **Web SDK** and OAuth Web client ID are loaded from `src/config/app.config.ts` at build time (not env `NEXT_PUBLIC_*` and not a separate REST “config API”). This is **not** the Firebase **service account** (admin) key; service account JSON must **never** be embedded in the web app or exposed to browsers.
- **Product APIs:** The interrupt device cloud APIs are **not** documented on this marketing site; these public routes do not expose them.

## HTTP API surface (this Next.js site)

| Method | Path | Purpose |
|--------|------|---------|
| GET | `/api/og` | Returns a **1200×630** PNG **Open Graph** image (edge). No JSON body; not a data API. |

There is **no** public JSON/GraphQL **product** or **waitlist** HTTP API on this site; waitlist is **Firebase Auth + Firestore** from the browser.

## Public routes & discovery (sitemap-aligned)

- `https://www.interruptio.com/` — Home — product overview, pre-register
- `https://www.interruptio.com/pricing` — Pricing, FAQ, usage calculator
- `https://www.interruptio.com/llms.txt` — LLM index (short markdown)
- `https://www.interruptio.com/llms-full.txt` — LLM full context (markdown)
- `https://www.interruptio.com/manifest.webmanifest` — PWA web app manifest
- `https://www.interruptio.com/icon` — Favicon / app icon (dynamic)
- `https://www.interruptio.com/.well-known/security.txt` — RFC 9116 security.txt (contact)
- `https://www.interruptio.com/robots.txt` — Crawler rules + sitemap pointer
- `https://www.interruptio.com/sitemap.xml` — XML sitemap (URL list for crawlers)

## What this site is not

- Not official documentation for third-party products (Firebase, Supabase, chip vendors).
- Does not expose authenticated **product** HTTP APIs on these public pages.
- Marketing metrics and examples on the homepage are illustrative unless sourced elsewhere.

## Home page FAQ (visible + structured data)

These questions appear on https://www.interruptio.com/ (`#faq`) and match home `FAQPage` JSON-LD:

- **What is InterruptIO?** InterruptIO is a cloud backend built for embedded devices and IoT fleets — OTA firmware updates, MQTT, telemetry, crash reports, fleet dashboards, remote tools, and serverless-style functions, integrated from firmware with a C SDK. It is aimed at teams who want a Firebase- or Supabase-style developer experience for hardware, not for generic web apps only.

- **Who is InterruptIO for?** Firmware engineers, hardware startups, and product teams shipping connected devices worldwide — from ESP32 and STM32 prototypes to larger fleets. The site is in pre-release: pre-register with Google to signal interest and get updates when the console opens.

- **Do I need to build my own REST or MQTT backend?** No. The product is designed so you integrate the SDK in firmware and use the cloud for devices, data, and operations without standing up your own IoT backend or DevOps stack for those concerns. Details and limits evolve — check the live pricing page before relying on quotas.

- **Which hardware or RTOS do you support?** Marketing pages highlight common targets (e.g. ESP32, STM32, nRF52, RP2040). Exact supported platforms and SDK maturity are confirmed in documentation at launch. The architecture is MQTT-first and oriented to resource-constrained MCUs.

- **How do pricing and currencies work?** Public pricing describes Spark (free tier), Blaze (usage-based), Team, and Enterprise, with USD as the default presentation and EUR and INR shown for estimates where the site supports them. Full payment methods and regional options are on the pricing page.

- **How can I contact you or ask about Enterprise?** Use Contact Us on the site to send a message (stored securely for the team), or the mailto links on the pricing page for sales-oriented subjects. Security disclosures should follow the contact in /.well-known/security.txt.

## SEO / structured data

Home: JSON-LD `@graph` includes **WebSite** (with `alternateName`), **Organization**, **SoftwareApplication**, **FAQPage**, **WebPage** (`mainEntity` → FAQ). Pricing: **BreadcrumbList**, **WebPage**, **FAQPage**. Use live page source for the exact graph.

## Contact & trust (use exactly this for outreach facts)

- **Email:** kaizenandinnovations@gmail.com
- **Security:** `https://www.interruptio.com/.well-known/security.txt` (RFC 9116)
- Do **not** invent support phone numbers unless they appear on the live site.

## Retrieval keywords

global IoT SaaS, embedded SaaS platform, B2B IoT cloud, device cloud SaaS, international IoT platform, Firebase for embedded software, Firebase for embedded devices, Supabase for embedded software, Supabase for embedded devices, embedded backend as a service, embedded BaaS, IoT backend platform, device cloud platform, embedded IoT, IoT platform, OTA updates, over-the-air firmware, fleet management, embedded devices, ESP32 cloud, STM32 IoT, nRF52 MQTT, RP2040, MQTT cloud, IoT cloud, crash analytics embedded, embedded C SDK, time-series database IoT, remote terminal devices, serverless embedded, device provisioning, firmware OTA, embedded developers, IoT telemetry, device dashboard, multi-currency SaaS IoT, worldwide device management, embedded developer waitlist, IoT platform pre-register, Google sign in developer waitlist, pre-launch embedded cloud, MCU cloud platform, WiFi IoT cloud backend, cellular IoT platform, industrial IoT SaaS, embedded device telemetry, IoT device management SaaS, cross-border IoT billing, global device fleet cloud, embedded Linux IoT cloud, RTOS cloud connectivity, hardware startup IoT backend, smart device OTA platform, IoT product analytics, edge device cloud sync, low power IoT cloud, B2B embedded platform, worldwide OTA firmware.

---
Human-maintained playbook: repository `GEO.md`. Source for this file: `src/lib/llms-context.ts`. Sitemap path list: `src/lib/discovery-config.ts`.