Skip to Content
OS OverviewArchitecture & Components

Architecture & Components

Onoots OS is a pnpm monorepo: 7 deployable apps, 7 shared packages, and 1 edge worker built on a curated set of external services. This page maps every component, color-coded by its role in the architecture.

ColorCategory
🔵 BlueInternal apps
🩵 CyanInternal packages & workers
🟣 PurpleData
🟠 OrangeArtificial intelligence
🔴 RedPayments
🟡 AmberStreaming & video
🟢 GreenInfrastructure & orchestration
🩷 PinkCommunications
🟤 BrownE-signature
🌊 TealMaps & geodata
⚪ GraySecurity & anti-bot
🟦 IndigoWeb3

🔵 Internal apps (apps/*)

AppRole
proptechReal-estate vertical (proptech.onoots.com): CRM, Buyer Desk, bilateral marketplace, swarm buying
supplyProcurement / supply vertical
aiPublic landing (products.onoots.com) + multi-product hub
platformSubscription & billing console (platform.onoots.com)
learnAcademy LMS (learn.onoots.com) with video on demand
liveLive events (live.onoots.com): WebRTC, HLS, Q&A, simulcast
mobile-buyerReact Native / Expo mobile app for the Buyer Manager

🩵 Internal packages & workers (packages/*, workers/*)

PackageRole
@onoots/coreShared multi-vertical engine (~70% reuse)
@onoots/billing-corePer-org token pool, plan gates, Stripe → notifications bridge
@onoots/buyer-core / @onoots/buyer-api-clientBuyer Desk domain logic and API client
@onoots/inventory-coreInventory engine
@onoots/jurisdictionJurisdiction packs (PE, CA-ON)
@onoots/swarm-runtimeTemporal worker for swarm buying workflows
workers/live-hlsCloudflare Worker serving signed HLS from R2

External services by category

CategoryServiceFunctionUsed by
🟣 DataSupabasePostgres + Auth + RLS + Storage — single database for the whole ecosystemall apps
🟠 AIAnthropic (Claude)AI agents via the AI SDK: BRA, guardrails, copilotsproptech · supply · ai
🟠 AIVercel AI SDK / GatewayModel abstraction layer (cheap / guard / reasoning tiers)proptech · supply · ai
🔴 PaymentsStripeSubscriptions, checkout, customer portal, webhooksplatform · billing-core
🟢 OrchestrationTemporal.ioDurable workflows for swarm buyingswarm-runtime · proptech
🟢 InfrastructureRailwayHosting for the Temporal workerswarm-runtime
🟢 InfrastructureVercelHosting & CI/CD for all Next.js apps + Analyticsall web apps
🟢 InfrastructureCloudflare Workers + R2Edge worker for signed HLS + live video segment storagelive
🟢 InfrastructureExpo / EASMobile runtime and buildsmobile-buyer
🟢 InfrastructureGitHubMonorepo, PRs, integration flowwhole repo
🟡 StreamingLiveKitLive WebRTC, egress, simulcast, SIP trunklive · proptech · supply
🟡 StreamingCloudflare StreamAcademy video on demand: TUS uploads, signed JWT, webhookslearn
🟡 StreamingYouTube (RTMP)Multi-platform simulcast destinationlive
🩷 CommunicationsResendTransactional emailproptech · supply
🩷 CommunicationsTwilioSMS / voiceproptech
🩷 CommunicationsWeb Push (VAPID)Browser push notificationsproptech · supply
🟤 E-signatureDocuSignContract e-signing (JWT grant + HMAC webhooks)proptech · supply
🟤 E-signatureDropbox SignAlternative / embedded e-signingproptech · supply
🌊 GeodataMapboxInteractive listing mapsproptech · supply
🌊 GeodataGoogle MapsComplementary maps & geocodingproptech
🌊 GeodataWalk ScoreWalkability score per propertyproptech
⚪ SecurityCloudflare TurnstileAnti-bot on public formsproptech · supply
⚪ SecurityGoogle reCAPTCHAAlternative anti-botproptech
⚪ SecurityVirusTotalUploaded-file scanningproptech
🟦 Web3EVM blockchain (viem)On-chain document anchoringproptech · supply
🟦 Web3Pinata (IPFS)IPFS document pinningproptech · supply

Architecture diagram

Users enter through the apps (blue); everything shares the internal packages (cyan) and Supabase (purple); each vertical leans on its category services.

In total: 26 external services and 15 internal components. Three categories carry deliberate provider redundancy — e-signature (DocuSign + Dropbox Sign), maps (Mapbox + Google Maps) and anti-bot (Turnstile + reCAPTCHA).

Last updated on