Menu
OverviewThe living system that keeps your operation correctFeaturesHow it observes, corrects and evolves your operationIntegrationsConnect every tool into one living modelSecurity & TrustYour operation stays private and under your controlHow gija worksThe loop that catches drift and corrects itThe Genome ModelHow your tools, workflows and signals become one living modelDrift DetectionCatch drift before it becomes failureAgents & PlaybooksAgents that fix what they can and bring you the rest
Product teamsKeep roadmaps, specs and tickets in sync as priorities shiftEngineeringCatch config and pipeline drift before it shipsOperationsAutomate the busywork that keeps the business runningCustomer SuccessSpot churn signals and act before accounts slipReduce driftCatch drift before it compounds into failureReclaim your timeHand the manual upkeep to agents and win back the hoursStay in controlContinuous controls and a plain-language record of every actionScale without the chaosGrow the operation without growing the mess
DocumentationGuides and references to get buildingConceptsWhat drift, the genome and operators actually meanBlogField notes on operations, drift and automationChangelogEverything new, as it shipsAboutWhy this exists, from the founderCustomer StoryBuilding on Supasprinkles from day oneHelp CenterAnswers, troubleshooting and supportStatusReal-time platform health and uptime
Appearance
Resources · Status
Platform health, in the open.
We watch your operation for drift. This page is where you watch ours: every part of Supasprinkles, with history back to the first early-access build.
Platform
The workspace and demo at gija.supasprinkles.com
90 days agoToday
API & webhooks
Programmatic access and outbound events
90 days agoToday
Genome engine
Model builds, reconciliation and drift detection
90 days agoToday
Integration sync
Third-party connections reading and writing
90 days agoToday
Operators & approvals
Agent runs, playbooks and the approval queue
90 days agoToday
Digests & notifications
Morning digests, email and Slack delivery
90 days agoToday
Past incidents
Genome rebuilds delayed after large integration backfillsApril 28–30, 2026Resolved
Workspaces connecting large toolsets saw genome rebuilds queue for up to a few hours; drift detection kept running against the last completed model, and no data was lost. The permanent fix shipped in v0.8.4 on April 30, which made rebuilds after a backfill dramatically faster.
That is the only incident so far. History begins March 18, 2026, when early access launched.