Skip to main content

​
Tuturuuu Platform Overview

The Tuturuuu platform combines proactive AI, unified applications, and automation tooling to help every visionary move from ambition to execution. Use this section to understand how each layer works and where to dive deeper.
Tuturuuu is mid-migration. The Next.js apps/web platform (port 7803) is being replaced by apps/tanstack-web (TanStack Start) plus a dedicated Rust apps/backend API. Most docs still describe the live apps/web shape, which remains valid today. See the TanStack Start and Rust migration for the runtime contract and what moves where.

​
Explore the Platform

  • Applications – Tuturuuu ships as a catalog of standalone web apps that each run on their own host, may serve product APIs locally, and can fall back to apps/web for unmatched or explicitly central route families. Browse the Applications catalog covering Calendar, Finance, Drive, Chat, CMS, Inventory, Storefront, and the Apps gateway.
  • Experience Apps – See how Tuturuuu Calendar, Tuturuuu Tasks, Tuturuuu Meet, and the Command Center Dashboard deliver daily flow. Start with the Command Center Dashboard.
  • AI & Automation – Learn how Mira (our Jarvis), Aurora, Nova, and Rewise power intelligent workflows in the AI Overview.
  • Shared Components – Reuse building blocks from the Component Library.
  • Personalization – Tailor the workspace using Themes and Language settings.

​
Satellite Apps And Central API Ownership

Beyond the experience surfaces, Tuturuuu is organized as a fleet of satellite apps under apps/ — calendar, finance, drive, chat, cms, inventory, storefront, and more. Each runs as its own standalone host on its own canonical domain. Satellites may own their product APIs locally; unmatched or explicitly central route families can fall back to the live apps/web platform. apps/web remains authoritative only where a route family has not been hard-cut over to a satellite or another approved owner. Use the satellite app ownership guide for local route, proxy, and auth boundaries. The TanStack and Rust migration guide tracks the separate frontend and backend cutover model. The Apps gateway (apps.tuturuuu.com) sits in front of the routable apps as a launcher and redirect layer — it surfaces app cards and redirects to each app’s canonical domain rather than reverse-proxying them.

​
Offline Runtime Ownership

Tuturuuu owns service-worker registration, precache-manifest generation, worker compilation, navigation fallback, and runtime cache strategies in packages/offline. Applications consume OfflineProvider; the live Web app builds the worker through createOfflineRoute and getOfflineTurbopackConfig. The worker continues to use /serwist/sw.js as a compatibility URL so existing browser registrations upgrade in place. Do not add Serwist packages to an app or depend on that project’s release schedule. Extend the shared internal runtime and its focused tests instead.

​
How It All Fits Together

The AI- and automation-layer model above (Mira/Aurora/Nova/Rewise) is the conceptual organizing picture. In the running platform these flow through the central apps/web API alongside the satellite apps; the migration to apps/tanstack-web plus the Rust apps/backend is reshaping where this API boundary lives.

​
Next Steps

  1. Walk through the Platform Features to see how the GTD-aligned dashboard works.
  2. Review the AI Structured Data guide to understand how we interact with models.
  3. Explore Component docs when you need reusable UI patterns.
Looking for development workflows? Jump to the Build section. Ready to level up your skills? Explore Learn.