No dates, because a date would be a guess.
Sourav Ukil builds netweft alone — the API, the dashboard, the worker and this site. A quarter-by-quarter roadmap from a team of one is a forecast dressed as a commitment, and this site does not print figures it has not measured. What can be stated honestly is what exists now, what will never exist, and the rules the next thing has to pass.
What exists today
What the next thing has to satisfy.
These are not aspirations. Every rule below is enforced somewhere in the codebase today, and a feature that breaks one gets redesigned rather than shipped with an exception.
- Nothing spends without quoting
- If an operation costs money, its price appears before it runs and credits are reserved at that price. A feature that spends without quoting is not shippable, whatever it does.
- Measurements are stored, not derived
- A measurement is written as an observation with the moment it was taken. Nothing is recomputed on read and presented as history, and no absence is stored as a zero.
- No invented metrics
- No figure in netweft is a score netweft invented. A number either came from a named provider, or is a direct observation, or is a documented rule applied to one — and the interface says which.
- Every capability has a machine surface
- Anything the dashboard can read, the HTTP API can read, and anything read-only over stored rows belongs on the MCP surface too. A capability that only exists behind the dashboard is half-built.
- The assistant never invents a figure
- The assistant answers from figures read back through tools. It cannot state a number the product did not measure, and a feature that would require it to is a feature that gets redesigned instead.
What netweft will not become.
These are not on a list waiting for a quarter. They are outside the product, and saying so is more useful than leaving them implied — a feature request answered in two years is a feature request answered badly.
- The work is link building
- netweft reads backlink data from a provider per request. It does not crawl the web, it holds no index of its own, and it cannot answer a question that requires one — such as which pages on the whole web link to a phrase.
- You need content tooling
- There are no briefs, no outlines, no optimisation scores and no writing assistant. The per-project assistant answers questions about the workspace's own stored figures, and is explicitly prevented from stating a number it did not read back through a tool.
- You need paid, social or local
- Organic only. Paid search, display, social and local are not in the product and are not planned into it.
- You need white-label client reporting
- Reports are the dashboard and the API. There is no white-label PDF, no client portal and no branded export.
- You need to evaluate for free
- There is no free tier and no free trial without a subscription started — a workspace with no subscription has no access. If the requirement is to evaluate without entering a card, netweft cannot meet it.
Something missing that is not on either list? It is probably neither built nor refused yet — say so, and it will be answered by the person who would have to build it. The guides are where decisions like that get written up after the fact, at netweft.com/blog.
The honest version of a roadmap is the present tense.
Everything on the list above is in the product today, priced on the rate card, and readable through the API.
There is no free tier. Three plans from $50 a month, each opening with a free trial.