# Roadmap > No dates and no promises. What netweft does today, what it will not do at any point, and the rules the next thing has to satisfy before it ships. Source: https://netweft.com/roadmap No dates. One person builds netweft, and a quarter-by-quarter roadmap from a team of one is a forecast dressed as a commitment. ## What exists today - [Keyword research](https://netweft.com/features/keyword-research): Keyword research tool: volume, CPC, competition, difficulty and intent for a keyword or a seed, with twelve months of history, saved to a project. - [Rank tracking](https://netweft.com/features/rank-tracking): Keyword rank tracking on a daily, weekly or monthly schedule or on demand, with every check stored as a snapshot rather than recomputed. - [Site audit](https://netweft.com/features/site-audit): Technical SEO site audit: a crawl that honours robots.txt, finds broken links and redirect chains, and ranks every issue by severity. - [Domain and backlinks](https://netweft.com/features/backlinks): Backlink checker and domain overview: links, referring domains, ranked keywords and top pages for your domain or anyone else's. - [AI visibility](https://netweft.com/features/ai-visibility): AI visibility tracker: how often AI answers on Google and ChatGPT name your domain, which sources they cite, and your share against competitors. - The machine surface: an OpenAPI 3.1 document over the whole HTTP API, and an MCP server under a scoped key. See https://netweft.com/mcp. ## What the next thing has to satisfy ### 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 ### 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.