Many seats, one mission.
FL33T is the tiny-team / household fleet story: shared boards and handles without everyone logging into a single landlord account. Each member keeps their own Apple identity; shared orchestration can call a self-hosted FL33T backend when you outgrow the kitchen table. Visual chrome is still honest placeholder — this manual tracks intent, not shipped pixels.
- Fleet-shaped chores AiMANAC can trigger once both apps trust the same host profile.
- Same customer-owned server posture as other “bring a brain” siblings — no Everplay-operated fleet cloud.
- iCloud per seat where Apple-managed shared state belongs; backend for heavier coordination when you opt in.
AiMANAC can nudge fleet chores once FL33T and your host are paired. Until the standalone app and backend kit ship, treat this page as the public contract for posture and pricing — not a feature checklist.
FL33T is the household / micro-team fleet app, with an optional self-hosted backend when you outgrow solo. Discord is where multi-seat operators compare deployment patterns and the maintainer answers first-run questions.
Support
JWT secret alignment with aimanac-rs, fleet member roster questions, Apple-identity-per-seat pairing snags, fl33t-server deploy on Railway? Ask in Discord.
Invite link pendingFeedback
Household / team workflow ideas, shared-fleet UX patterns, capability-token scope requests — feedback goes through Discord, openly.
Invite link pendingDirect contact until the invite link lands:
info@llmtech.net.
- FL33T server deployGHCR pull-first;
JWT_SECRETmust match your aimanac-server. - Fleet co-host specPull fl33t-server beside aimanac on one VM.
- AiMANAC baseOrchestration console for fleet nudges when integrated.
- BROILRAnother dedicated-surface sibling pattern.
- Self-deploy specHost layout discipline shared across siblings.
- Railway deployStep-by-step wizard for the fl33t-server container.