Choose Your Setup
If you are trying to decide how to adopt Fluent, start here.
The Short Version
Use managed early access for the hosted path. The current sign-up flow will tell you whether to sign in right away or wait for an invite.
Run Fluent yourself for immediate access to the open-source runtime.
Two Ways To Start
Request Early Access For
- managed auth and setup
- no infrastructure to run
- the managed long-term path
- a small early-access pilot and staged rollout
Run Fluent Yourself For
- immediate access
- Docker or Node.js setup
- direct control over storage and updates
- a local or self-hosted environment
Which Assistant Should You Use?
ChatGPT
Choose ChatGPT for the public Fluent Meals rich-host path when your ChatGPT environment supports MCP Apps-style rendering.
Start here:
Claude
Choose Claude for a strong general conversational experience with Fluent as a connected MCP server.
Start here:
Codex
Choose Codex when your workflow already lives there and Fluent should connect into that environment.
Start here:
OpenClaw
Choose OpenClaw when that is already your assistant environment and Fluent should use the live ClawHub plugin path.
Start here:
Which Domain Should You Start With?
Meals
Start with Meals for the fastest obvious value from Fluent.
Good first reasons:
- planning dinners for the week
- generating a grocery list
- grounding meal decisions in inventory and household preferences
Recipe:
Style
Start with Style if your main question is "should I buy this?" or "what is missing from my wardrobe?"
Recipe:
Health
Start with Health to keep the assistant grounded in a real training block instead of improvising workouts from scratch every time.
Recipe:
Deployment Patterns For The Open-Source Runtime
Laptop
Best for trying Fluent quickly and keeping everything local.
Home Server
Best for using Fluent across devices on your own network.
VPS
Best for remote availability when reverse proxy, TLS, and security boundaries are comfortable territory.
Recommended Paths
Understand The Product
Use Fluent Now
Join Managed Early Access
Keep Self-Hosting Simple
- use Docker
- start with one assistant
- start with one domain
- do not try to perfect every preference before your first useful workflow
Decision Checklist
Use managed early access when infrastructure is the main thing to avoid.
Run Fluent yourself when direct control matters most.
Fluent is in early access, and the open-source runtime is available now. You can start an export or deletion request in Fluent; during early access, the Fluent team completes and verifies it.