# About netweft

> What netweft is, how it is built, and the claims this site deliberately does not make.

Source: https://netweft.com/about

## Why netweft exists

Most SEO tools answer a question and hand you a number without telling you what the number cost to produce or when it was true. netweft was built the other way round: an observation is stored with the moment it was taken, and the price of producing it is visible before it is produced.

## How it is built

- A Hono API on Cloudflare Workers with an OpenAPI 3.1 document, a TanStack Start dashboard, and a Cloudflare D1 schema shared through Drizzle.
- Cloudflare Workflows run audits and rank checks; a cron starts the scheduled ones.
- The cache (Workers KV) and the rate limiter (Workers Rate Limiting) fail open. If either cannot answer, every lookup misses and every request is allowed; that is the intended degraded behaviour rather than a failure mode.
- Sign-in is Google, GitHub, or an email and a password confirmed by a six-digit code. Search Console and GA4 connect per project, with read-only scopes requested at connection time.
- Payments run on Polar. Credits meter every vendor lookup, crawl and AI call.

## Who builds it

Sourav Ukil, founder and engineer. Sourav builds netweft on his own — the API, the dashboard, the worker and this site. The guides here are working notes from that build, not marketing written around it. There is no team page because there is no team. If something on this site is wrong, one person wrote it and one person will fix it: hello@netweft.com.

## What we will not claim

This site carries no customer logos, testimonials, user counts, benchmarks or uptime figures, because none have been measured. Sample data is labelled where it appears. Prices and credit costs are read from the product's own catalogue at build time rather than typed into a page.