4 guides
netweft is four Cloudflare Workers over one D1 database: static marketing and dashboard sites, a Hono API with Workflows and a cron, and an analytics relay. Six decisions shaped it: a provider port, reserve-then-settle credits, stored snapshots, one-statement D1 guards, a read-only MCP surface and no free tier.
netweft's cache and rate limiter fail open: a cache that cannot answer is a miss, and a limiter that cannot count lets the request through, so the product keeps working, more slowly and more permissively. Choosing that up front is what stops a performance dependency becoming an availability one.
netweft reserves credits at the rate card's price before a paid call goes out, then reads the real charge off the response and settles against it. The reservation is a ceiling, so a cheaper operation releases the difference, and a workspace that cannot cover it is refused before anything is bought.
netweft's SEO data provider is an interface with two implementations: DataForSEO for real data, and a mock serving deterministic fixtures with no credentials. Nothing above the port knows which answered, so the product runs offline, every test is deterministic, and credit accounting is identical on both paths.
May we set cookies to see how netweft is used? Session recordings never capture what you type. Nothing is stored until you answer, and declining still counts the visit, without a cookie. Privacy