LONGTAIL FORGE ROADMAP
What is being finished now, what comes next, and what can wait.
This roadmap is directional, not a pile of dates pretending software development never changes. “Now” means active work. “Next” means decided direction. “Later” means wanted, but not worth derailing the current work for.
Things will move between sections as testing, feedback, security work, and real use expose better priorities. That is the point of having a roadmap instead of a prophecy.
NOW
Get the core product ready for people who did not build it.
The current work is less about adding another shiny module and more about making the existing system dependable, understandable, and safe enough for real preview use.
Preview hardening
Finish the rough edges that only show up when somebody other than the developer uses the product: permissions, onboarding paths, error handling, navigation, empty states, and the little failures that turn a useful tool into a support ticket.
Security and account controls
Continue tightening secure records, authentication, session handling, roles, workspace boundaries, and the permission model before broader access makes mistakes more expensive.
Reliable demo and self-hosted path
Keep the public sandbox useful, predictable, and resettable while the self-hosted deployment path matures into something a real person can install and maintain without knowing the project history by heart.
The workbench, projects, actions, tasks, notes, lists, files, knowledge, users, workspaces, and the surrounding context model are already the center of the product. The immediate job is making that center hold up.
NEXT
Expand the operational side once the foundation is boring in the best possible way.
Once preview stability stops consuming the oxygen in the room, the next work is about making Longtail Forge useful for more of the day-to-day business context that surrounds projects.
Support work
Bring support tickets and ongoing service work into the same context model as projects so small requests do not disappear into email while the larger client history lives somewhere else.
Inventory and structured records
Add practical inventory and catalog-style records for the kinds of assets, equipment, credentials, reference data, and operational details that need more structure than a note but do not deserve their own separate app.
A cleaner module system
Keep expanding the internal module registry so business-only features, optional capabilities, and future product areas can be enabled without turning the core application into one enormous inseparable blob.
This is also where the deployment architecture can keep maturing toward broader hosted use without forcing the hosted and self-hosted editions to become two different products.
LATER
Useful ideas that are allowed to wait their turn.
These are directions that fit the product, but they are not reasons to destabilize the work people already depend on.
Hosted SaaS polish
Turn the hosted option into something that feels managed instead of merely deployed: smoother onboarding, billing, account administration, backups, operational tooling, and the boring infrastructure work that makes SaaS actually SaaS.
Stronger external connections
Expand integrations with calendars, file providers, and other outside systems where connection genuinely reduces duplicate work instead of adding an integration badge to a feature list.
Deeper review and planning tools
Build out more deliberate planning, review, risk, blocker, budget, and history views where they help people understand the work without turning Longtail Forge into enterprise project-management cosplay.
NOT PLANNED
A roadmap is more useful when it also says what the product is not chasing.
Longtail Forge does not need to absorb every adjacent category of software to justify existing.
Not an everything-suite
The goal is not to replace accounting, email, cloud storage, CRM, chat, calendar, source control, and every other tool a business might use. When another system already does the job well, Longtail Forge should connect to it or stay out of the way.
Not built around surveillance
There is no product direction toward employee activity scoring, keystroke tracking, performative “productivity” metrics, or turning normal work into a management surveillance feed.
Not a deadline factory
The product should support planning without pretending every piece of uncertain work can be made accurate by putting a date beside it. Useful commitments matter; fake certainty does not.
If Longtail Forge needs to grow beyond these boundaries later, that decision should come from repeated real-world use rather than fear that another product has a longer feature matrix.
Want to see where the roadmap meets the actual product?
The demo shows what exists today. The changelog records what actually shipped. Longtail Forge Updates explains the meaningful recent changes in plain English. The roadmap is the part in between: the direction, with enough uncertainty left intact to stay honest.