Planner
Rule-based local planner (AI NOT_CONNECTED)No language model is connected. Plans come from a local rule-based planner and are labeled that way. They are not presented as AI output.
Execution workspace
Write what you want to achieve in plain language. Nirflow turns it into an editable plan with milestones, tasks, dates and budget assumptions. Nothing is created until you approve it.
Every outward action follows this path. No step is skipped.
You describe the goal, deadline and budget.
Milestones, tasks and budget assumptions, dated.
Change titles, dates and owners inline.
Records are created only after you confirm.
External actions run after a permission check.
Each result is checked and logged.
Three steps, each one under your control.
For example: “Help me launch an online business in 30 days with a budget of $1,000.” Plain language is enough.
Review the proposed milestones and tasks on a timeline. Adjust any title, date or owner before anything is saved.
Approval creates the goal, milestones, projects and tasks in one step. Progress is counted from tasks you actually complete.
The system proposes, you decide. Any action that leaves Nirflow passes a permission check and waits for your approval.
Progress and insights come only from your real data. When there is no data, you see an empty state, not a sample chart.
Workspace boundaries are enforced on the server. You can export your data as JSON or delete your account.
Platform administrators see counts and metadata only. Goals, tasks, notes and plan text are never shown to them.
Nirflow is in Phase 1. Here is what is connected today and what is not.
No language model is connected. Plans come from a local rule-based planner and are labeled that way. They are not presented as AI output.
Checkout is a local simulation. No card details are requested and no money moves.
These integrations are not connected yet. Each one is switched on only after it is verified end to end.