Problem
Currently, existing users who navigate to flowfuse.com must manually click the "Sign In" button to get to app.flowfuse.com, creating unnecessary friction in the user journey.
Quite a number of unique visitors clicked "Sign In" from the homepage in a 7-day period (late October 2025), suggesting these users just wanted to access their environment, not view marketing content.
Current Behavior
- User types
flowfuse.com or clicks a bookmark
- User sees marketing homepage
- User manually clicks "Sign In"
- User is redirected to
app.flowfuse.com
Desired Behavior
Similar to GitHub's approach:
- User navigates to
flowfuse.com
- JavaScript detects if user is logged in (via API call to
app.flowfuse.com)
- If logged in, automatically redirect to
app.flowfuse.com
- If not logged in, show marketing homepage as normal
Proposed Solutions
Short-term: Homepage Auto-redirect
Add JavaScript to the homepage that:
- Checks if the user is logged in by making an API call to
app.flowfuse.com
- Redirects logged-in users to
app.flowfuse.com
- Shows marketing content to non-logged-in users
Technical Feasibility: Confirmed feasible by @knolleary in Slack discussion (Oct 28, 2025)
Long-term: Subdomain Strategy (Optional)
Consider adopting GitLab's approach with an about.flowfuse.com subdomain:
- Move marketing content to
about.flowfuse.com
flowfuse.com becomes the app entry point
- Provides cleaner separation between marketing and product
- Makes docs/pricing accessible without losing app access
Considerations
-
Navigation from App: If homepage redirects logged-in users, we need better links from the app back to:
- Documentation
- Pricing information
- Other website resources
-
Performance: API call to check login status should be fast and not delay page load significantly
-
Privacy: CORS and cookie policies need to support cross-subdomain authentication checks
Examples
- GitHub: Detects logged-in users on homepage and redirects to app
- GitLab: Uses
about.gitlab.com for marketing, gitlab.com for the app
Related Discussion
Original Slack thread in #design (Oct 28, 2025): https://flowfuse.slack.com/archives/C03387T7UFP/p1761662521430019
Acceptance Criteria
Problem
Currently, existing users who navigate to
flowfuse.commust manually click the "Sign In" button to get toapp.flowfuse.com, creating unnecessary friction in the user journey.Quite a number of unique visitors clicked "Sign In" from the homepage in a 7-day period (late October 2025), suggesting these users just wanted to access their environment, not view marketing content.
Current Behavior
flowfuse.comor clicks a bookmarkapp.flowfuse.comDesired Behavior
Similar to GitHub's approach:
flowfuse.comapp.flowfuse.com)app.flowfuse.comProposed Solutions
Short-term: Homepage Auto-redirect
Add JavaScript to the homepage that:
app.flowfuse.comapp.flowfuse.comTechnical Feasibility: Confirmed feasible by @knolleary in Slack discussion (Oct 28, 2025)
Long-term: Subdomain Strategy (Optional)
Consider adopting GitLab's approach with an
about.flowfuse.comsubdomain:about.flowfuse.comflowfuse.combecomes the app entry pointConsiderations
Navigation from App: If homepage redirects logged-in users, we need better links from the app back to:
Performance: API call to check login status should be fast and not delay page load significantly
Privacy: CORS and cookie policies need to support cross-subdomain authentication checks
Examples
about.gitlab.comfor marketing,gitlab.comfor the appRelated Discussion
Original Slack thread in #design (Oct 28, 2025): https://flowfuse.slack.com/archives/C03387T7UFP/p1761662521430019
Acceptance Criteria
flowfuse.comhomepage are automatically redirected toapp.flowfuse.com