Current beta architecture
A Firebase-first system with Gemini-powered execution.
Orbit is intentionally built as a real beta stack, not a slide-deck architecture. The system today runs on Firebase Auth, Firestore, Cloud Functions, hosted web delivery, and a Gemini-powered AI layer that drives @Nex through dynamic prompts, context injection, and safe backend routing.
Identity
Firebase Auth
Phone login, onboarding, profile state, and build-specific app identity are driven through Firebase authentication and app-side profile synchronization.
Realtime data
Firestore
Chats, groups, shared tasks, Haven signals, workflow submissions, and business metadata are persisted in Firestore with explicit security rules around membership and access.
Execution
Cloud Functions
Backend callables handle Nex routing, Haven role access, task enforcement, workflow bootstrap, and secure business-side decision logic.
@Nex AI layer
Gemini is the capability core. Orbit is the router.
Orbit does not train a base model from scratch. Instead, @Nex uses Gemini with dynamic system prompts, structured context windows, and backend execution rules so the same intelligence layer can behave as a conversational assistant in Vesta and a more disciplined operator in Vesta Business.
That means the app can stay broad and helpful like a frontier model while still executing within company rules for tasks, roles, Haven flows, and workflows.
Business execution
Shared tasks, Haven, and workflow foundations.
Vesta Business extends the platform with reviewer-controlled Haven lanes, shared task state, role-aware workflow contracts, and business-specific admin surfaces. This is the layer designed to compete with startup team tooling, not just consumer messaging.
Early workflow categories include travel request, leave, reimbursement, purchase, and IT access. The beta foundation is already typed and secured so the execution engine can grow without redesigning the data model later.
Readiness signals
Public product presence
Orbit already has a live domain, public product pages, downloadable Android betas, and separate personal and business experiences.
Cloud-native stack
The application already depends on managed authentication, serverless backend functions, hosted web output, and AI-assisted product functionality.