Early Access
This page explains what early access means right now and how to think about using Fluent before wider availability.
Current Status
Fluent is in early access and open source.
Today:
- request early access is open
- product access is invitation-based
- early access is currently free
- the open-source runtime is available for inspection, self-hosting, and builder workflows
What Early Access Is For
Early access is for:
- managed authentication
- managed storage and updates
- a cleaner setup path than self-hosting
- the same assistant-first product shape without running the infrastructure themselves
What Requesting Early Access Means
Requesting early access is a way to express interest while rollout is still controlled.
Depending on where rollout stands, that can mean:
- joining a waitlist or interest list
- getting invited into a limited access group
- being contacted when Fluent is ready for a wider audience
What Early Access Includes
Fluent early access currently includes exactly this:
- small-cohort access to a Fluent account
- sign-in at the provisioned Fluent access point
- managed auth, storage, and updates for that account
- connecting ChatGPT, Claude, Codex, OpenClaw, or a generic MCP client to Fluent
- approving scopes and using Fluent from inside your assistant once access has been provisioned
- export and deletion requests, completed by the Fluent team during early access
What Early Access Does Not Include
Fluent early access does not currently include:
- unlimited open public account creation
- guaranteed immediate access after you submit sign-up interest, unless the current form tells you to continue right away
- paid access as a required first-use path
- automatic import from a self-hosted runtime
- instant self-serve completion of export, deletion, or account closure
- a standalone Fluent end-user app where the main interaction happens outside your assistant
What You Should Expect Today
Do not treat an early access request as a promise of immediate self-serve access.
Right now, the correct expectation is:
- access may still be staged
- early access is currently free
- the current access flow on meetfluent.app tells you whether to sign in right away or wait for an invite
- if paid managed access is introduced later, billing and account management happen on meetfluent.app rather than inside an assistant
- you can start an export or deletion request in Fluent; during early access, the Fluent team completes and verifies it
For retention, export, deletion, and migration expectations, use Privacy & Data.
Should You Request Early Access Or Run Fluent Yourself?
Use managed early access for:
- the hosted Fluent path
- managed auth and setup
- a small staged pilot
Run Fluent yourself for:
- immediate access
- self-hosting or local tooling
- direct control over storage and deployment
Use Choose Your Setup for a more explicit comparison.
What Happens Once You Have Early Access
The expected shape is:
- Sign in to your Fluent access point
- Connect your assistant
- Approve the relevant scopes
- Reconnect if your client has stale auth or an older registration
- Start inside the assistant itself
Depending on the assistant, Fluent may also show a Home overview with account status and readiness across Meals, Style, and Health before you dive into a specific workflow.
The first useful check remains:
"What are my Fluent capabilities?"
For a public example before you have early access, try the Meals demo walkthrough. It shows how planning, approval, groceries, and follow-up fit together without requiring a private account.