Lunor Flow
Plan together. Talk together. Execute together.
A workspace where the task, the deadline, and the conversation about both live on the same record.
- product
- Lunor Flow
- surface
- Flow
- category
- Workspace
- backend
- Not attached
- status
- In Development
This page describes the intended product. Nothing here accepts a payment, sells a ticket, opens a workspace, sends a campaign, or answers a support conversation.
The problem
The work is in one tool. The decision was in another.
Teams already have a project tracker and a chat app. The failure is the gap between them. A deadline moves in a channel, the task still shows the old date, and the file everyone needed is in a third place.
Switching tools is not the cost. The cost is reconstructing what was agreed, who owns it, and whether it is late.
The approach
Plan together. Talk together. Execute together.
Lunor Flow is the workspace being built for that gap. Projects, tasks, channels, files, and deadlines sit together, so a conversation can stay attached to the work it is about.
It is under development. This page is the description of the product, not a login. There is no workspace to join from this site.
Capabilities
What the module does.
Projects
A named body of work with an owner, a status, and the tasks under it.
Tasks
Assignee, deadline, and state — open, in progress, blocked, done.
Channels
Team conversation that can be tied to a project instead of floating free.
Threads on the work
Discussion stays on the task it refers to.
Files
The document sits with the project, not in a separate drive nobody links.
Deadlines
Dates live on the task, so a change in chat is a change to the record.
Workflows
Repeatable steps for work the team does more than once.
One record
Conversation and execution are the same workspace, not two exports.
How it works
The workflow, step by step.
- 01Open a project
Name it, give it an owner, and put the tasks under it.
- 02Assign the work
Each task has a person and a deadline.
- 03Talk where the work is
The channel and the task thread stay on that project.
- 04Keep the file with it
Documents attach to the project instead of being re-sent.
- 05Close it
Done means the task and the conversation agree.
Specification
At a glance.
- Unit
- Project, task, channel, file
- Task states
- Open, in progress, blocked, done
- Conversation
- Channels and threads on the work
- Line
- Plan together. Talk together. Execute together.
- Access
- No workspace on this site
- Status
- In development — no published date
Security
A workspace holds other people's conversations. This site holds none of them.
- No accounts, channels, or files exist for Lunor Flow on this site
- The intended product keeps project membership explicit
- Nothing here reads a team's existing chat or task tool
- Production data, if the product ships, stays in that product — not in this marketing site
Full posture, including what we deliberately do not claim, is on the security page.
Use cases
Where it gets used.
A delivery team
Tasks, deadlines, and the discussion about them in one place.
A project with too many tools
Replace the gap between the tracker and the chat, not every tool at once.
Repeated work
A workflow for the steps a team runs every week.
FAQ
Questions asked before adopting this module.
Can my team use Lunor Flow now?
No. It is under development. This page is the product description. There is no workspace to create and no invite to send.
Does it replace chat and project management?
That is the point of the product: tasks, projects, channels, files, and deadlines together, so the conversation and the work stay connected. It is not available to switch to yet.
Will it connect to the other Lunor products?
Where a team is already running Lunor infrastructure, Flow is being designed so the work around that project can live beside it. No integration is live.
When does it ship?
No date is published. Status stays in development until there is a workspace a real team can use.
Other modules
Same Console, same project record.
Next step
Tell us if you need this one.
Modules move up the sequence when a real project needs them. If this is the one blocking you, that is useful information.