What AutoSugges is
A list intelligence, LOV and autocomplete platform. You own a list — countries, products, clinics, anything people pick from — AutoSugges compiles it into immutable, version-addressed runtime artifacts and serves them from Cloudflare's edge, so a keystroke never waits on a database.
Lists are the platform; autocomplete is the visible part. Underneath, every list has a canonical owner, publishing is explicit and reversible, and a client is guaranteed to never see data mixed from two versions.
The engineering position, and why
The runtime never touches PostgreSQL
The autocomplete hot path is locked out of the database entirely. Every list is compiled ahead of time into ranked, prefix-addressable buckets, so a query is a Cloudflare KV read, not a live query plan. Speed is a property of the architecture, not a tuning exercise applied after the fact.
Tenant isolation is structural, not a promise
Row-level security is enabled and forced on every table your data lives in — not the weaker default Supabase applies automatically, which only covers its own default schema. Credential material and internal ledgers live in a second schema no API role can reach at all, so a policy mistake in it cannot leak anything.
Artifacts are immutable and version-addressed
A publish produces a new, hash-addressed artifact; nothing already running is overwritten out from under it, and activation happens only after the new version verifies. Rollback is switching a pointer back, not un-doing a write.
The decisions are locked and traceable
AutoSugges is built against a written register of locked architectural decisions — what the runtime may and may not depend on, how caching and metering are ordered, what a publishable key does and does not expose. Decisions get made once, in the open, and the product is built to match them rather than the other way around.
Who builds it
AutoSugges is built by AKHBaig, independently. There is no company entity, no office, no funding round and no team behind it — a fact worth stating plainly rather than dressing up, because it is exactly the kind of thing this page would otherwise be tempted to imply without saying. What stands in for the usual trust signals is architectural: your data stays in your own tenant, the controls that protect it are documented rather than asserted, and the artifacts you depend on do not change under you.