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. The maintained runtime is Next.js Web and its satellite apps. Rust (apps/backend) and TanStack Start (apps/tanstack-web) are paused and not in
use. Docker setup is inactive and the Docker cron runner is retired. Retained
migration designs describe a possible future, not live traffic or a current
setup requirement. See the active runtime map.
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/webfor 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, or turn Meet notes into reviewed calendar and task follow-ups.
- AI & Automation – Learn how Mira, Nova, and Rewise support 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 underapps/ — 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
retains historical designs; both runtimes are paused and not in use.
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 inpackages/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 fits together
The Apps gateway links to standalone Next.js products. Each product owns its publications, permissions, and local route handlers; central API families remain in Web. Shared packages provide UI, internal API clients, authentication, and storage helpers. Supabase, Trigger.dev, and product-specific Cloudflare services support these apps according to their owning runbooks. Use the complete product directory and repository catalog to locate products and supporting services. Versions are derived from maintained source manifests and lockfiles; a source entry is not a deployment or entitlement guarantee. Private workspace pages remain authenticated and excluded from search indexing.Next Steps
- Walk through the Platform Features to see how the GTD-aligned dashboard works.
- Review the AI Structured Data guide to understand how we interact with models.
- Explore Component docs when you need reusable UI patterns.