Overview

Introduction

Satellite Labs runs a marketing site, Satellite OS, and a set of public HTTP endpoints for forms, waitlists, and billing. This documentation describes how those surfaces fit together and how to integrate safely from your own stack.

What you can build

• Public HTTP APIs for newsletter signup, careers applications, report waitlists, and tooling — all JSON over HTTPS with predictable error shapes.
• Webhooks for Stripe billing events that keep subscriptions and entitlements aligned with Satellite OS.
• First-party surfaces such as the marketing site and OS dashboard, which share auth, theming, and Supabase-backed data.

Architecture

Traffic enters through Vercel Edge / Node runtimes. Route handlers under src/app/api validate input, apply rate limits where configured, and call Supabase or Stripe. Nothing here is a separate microservice — each endpoint is colocated with the Next.js app for simpler operations and reviews.

Client-only dashboards (OS, Studio) use the Supabase client with row-level security; public docs focus on the routes you can call from servers or edge workers you control.

Environments

Next steps

Read the API reference for request/response schemas, then Webhooks if you are extending billing or fulfillment flows that originate in Stripe.