18
Docker services ready
Infrastructure already in place for orchestration, realtime, and execution.
Phase 1A
FlowMind turns your AI stack into a collaborative operating system.
Replace the generic landing wrapper with a sharper product story: domain assistants, realtime workflow collaboration, plugin extensibility, live debugging, snapshots, deploy templates, and transparent usage-based pricing.
Replace wrapper UI with a workflow operating surface
Ship collaboration, debugging, plugins, and deploy templates in phases
Keep the existing Next.js, FastAPI, Redis, and Postgres core in place
Next.js 16FastAPIPostgres + RedisSocket.IO
Brand relaunch with a clearer value proposition
FlowMind reframes the current stack around collaboration, extensibility, observability, and transparent economics.
Collaborate
Presence, shared graph state, and team-safe editing for the existing builder.
Inspect
Breakpoints, snapshots, and diffs reveal where automation logic is actually failing.
Extend
Domain agent factories and plugin primitives turn the platform into an ecosystem.
18
Docker services ready
255+
Backend services and routes
255+
Backend services and routes
Depth exists today; the relaunch makes the capabilities legible.
32
Integrated tools
A plugin story becomes credible because the platform is already extensible.
10k
Free tokens each month
Usage-based pricing starts transparent instead of hiding behind a plan wall.
Competitive map
Seven competitive features, wired into the product
The landing page should not promise vapor. Every headline below maps directly to a concrete phase in Plan2026 and to infrastructure that already exists or clearly extends from it.
1B
CRDT collaboration
Shared workflow editing with Yjs, presence, and offline recovery directly in the existing builder.
Yjs + @xyflow + Redis awareness
1C
Domain-specific AI assistants
Legal, finance, and biotech agent factories with schema validation, glossaries, and constraints.
LangChain + Qdrant domain depth
2A
Open plugin SDK
Custom nodes, widgets, data sources, and lifecycle hooks delivered through an extensible registry.
Plugin manifest + sandboxed loading
2B
Live AI debugger
Breakpoint control, variable inspection, and step mode surfaced over the existing execution engine.
Monaco + execution event stream
2C
Versioned workflows
Immutable snapshots, diffs, branch-aware history, and fast reverts for every saved workflow.
JSON snapshots + visual timeline
3A
One-click deploy templates
Prebuilt stacks for assistants, support bots, and document processors that launch from a gallery.
Compose templates + health checks
3B
Semantic suggestions
Recommend the next node or branch based on current graph context and indexed capability metadata.
Qdrant retrieval + ranked rationale
Architecture
Architecture built on what you already own
This relaunch works because the infrastructure is already deeper than the public story. The new landing page should make the progression obvious: keep the stack, add the missing surface area, and convert hidden depth into visible product confidence.
Existing stack
Keep the platform assets that already exist.
FlowMind starts from the current product depth instead of rebuilding a shallow AI shell.
- Next.js 16 frontend with Shadcn UI, Radix, Tailwind, and Framer Motion
- FastAPI backend with orchestration, execution, auth, billing, and cost tracking
- Socket.IO, PostgreSQL, Redis, LangChain, LangGraph, and template infrastructure
New FlowMind layer
Add the missing competitive surface area.
The relaunch packages collaboration, extension, visibility, and deployability into a coherent product story.
- CRDT sync and presence
- Domain agent factory
- Plugin SDK and registry
- Debugger overlay and workflow versions
- Deploy templates and semantic suggestions
User outcome
Present a workflow operating system, not another wrapper.
The result is a product that feels deeper on first visit and stronger under real production load.
- Shared editing without lock contention
- Faster debugging and safer iteration
- Transparent usage-based pricing
- A clearer roadmap for ecosystem expansion
Why this story lands
FlowMind feels credible because the roadmap is attached to working infrastructure.
Existing depth becomes visible on first impression
Usage-based pricing undercuts flat-plan wrapper products
The roadmap turns hidden infrastructure into defensible product categories
Pricing
Usage-based pricing that mirrors actual work
FlowMind does not need to imitate flat-plan AI wrappers. The product already has cost tracking primitives, so the landing page should frame pricing as transparent, metered, and friendly to teams that scale unevenly.
Starter
$0forever
A generous entry point for teams validating an orchestration workflow before they commit volume.
10,000 tokens / month included
- 5 workflows
- 2 collaborators
- Core builder and assistant orchestration
- Usage dashboard and cost visibility
Builder
$0.01per 1K input tokens
Pay only for the work the platform performs, with output billed separately and no artificial seat cliff.
$0.03 per 1K output tokens
- Volume-based usage billing
- CRDT collaboration and version history
- Plugin SDK access
- Debugger and deploy templates
Enterprise
Customcontract
For teams that need sandboxing, governance, migration help, and negotiated capacity commitments.
Private deployment and roadmap alignment
- Private environments
- Governance and permission controls
- Implementation support
- Custom metering and billing terms
Feedback
Signals from design partners
These are the recurring asks that make the relaunch direction credible. The message is consistent: teams want orchestration depth, visible collaboration mechanics, and pricing that follows usage instead of forcing a category illusion.
“We do not need another chat shell. We need shared graph editing, breakpoints, and a pricing model that maps to actual usage.”
Platform lead
Fintech automation team
“The combination of domain-aware agents and workflow snapshots is what makes an AI builder feel production-ready instead of experimental.”
Research operations manager
Biotech workflow program
“If plugins are real and deployment templates are opinionated, the product stops being a demo and starts becoming a platform.”
Founder
Developer tools studio
Final call to action
Replace the wrapper. Keep the depth.
Phase 1A makes the product story match the platform underneath it. FlowMind becomes the public face for a roadmap that already has credible technical roots.
Default homepage becomes FlowMind
Nura remains preserved at /nura
Pricing shifts to a usage-based narrative
The roadmap is visible section by section