THINVENT TECHNOLOGIES · WWW.THINVENT.IN · SYSTEM REFERENCE
The website, drawn as a board
We build fanless computers, so here is our website drawn like one of our own boards:
every subsystem a module, every data flow a trace. Follow the teal signal — one visitor, from ad
click to delivered order, and back into the ad platform's brain.
data flow the closed loop detailed below
TEAL PULSES = ONE VISITOR: AD CLICK → PAGE → CONTACT → TICKET → CONVERSION REPORTED → THE AD LEARNS
245,638
SEO pages live
224
parts in productdb
20
languages
15
product families
12
customer case studies
U1
Product core: the SKU is a sentence
One database (224 parts, 10 categories) generates every page, price, datasheet and feed.
A product is a compatible combination of parts, written as a code the whole system can read:
EACH FIELD IS A REAL PART · PARTS DECLARE WHAT THEY ALLOW, PROVIDE AND CONTAIN · ONE VALIDATOR GUARDS PAGES, CHAT AND CHECKOUT
PRICE PATH — computed live, never stored
Part costslive from the ERP
→
Σ SKU costsummed per configuration
→
Pricing modelper product class
→
₹ web pricein the visitor's currency
ONE DATABASE, SIX SHELVES
/p/<sku>product page
/f/<family>configurator — adapter auto-picked by power budget
/gs/<sku>priced page for ads
/ds/<sku>.pdfdatasheet on demand
Merchant feed
Amazon listings
U2
The SEO factory
Nobody writes 245,638 pages by hand. A pipeline reads what people search, groups queries by
meaning, matches them to products, and builds a page per group — then reloads the live index.
QUERY SOURCES
Search Consolewhat we rank forAds search termswhat we pay forKeyword ideaswhat we could rank forLive site searcheswhat visitors type here
THE CONVEYOR
1
Combine
merge and dedupe all sources
2
Embed
every query becomes a meaning-vector
3
Understand
"16gb fanless pc" → RAM=16 + fanless
4
Cluster
similar queries share one page
5
Match
clusters → the SKUs that answer them
6
Build
245,638 query pages + sitemaps → Google
7
Knit + write
related-search links · AI descriptions
8
Go live
vectors loaded into the search index
RUNS ON RENTED CLOUD COMPUTE · INCREMENTAL · WEAK PAGES PRUNED BY REAL VISIT COUNTS
U3
Live search: milliseconds, not databases
Visitor typessearch box or /q/ page
→
Understandwords → filters (RAM, CPU, fanless…)
→Vector indexmeaning-based search in memory→
Resultsproducts + live prices + facets + related searches + autocomplete
A dedicated search service answers every keystroke without touching
the main site — and every search it sees becomes tomorrow's pipeline input.
U4
The ads robot: campaigns tuned by API
Google Ads APIthe account, programmable⇄
COLLECT · nightlyperformance + search terms → local evidence base
Built to orderparts → assembly → thermal test → OS → QC → packing
→Ship & tracklive courier status on your order page
PREFER A QUOTE? SKIP PAYMENT — A SALESPERSON PICKS UP YOUR REQUEST EITHER WAY
Fulfilment — from our own order history
Stage
Typical
Notes
Order confirmed → dispatched
about a week
larger or custom builds take longer — sales confirms at order time
Courier, metro cities
2–4 days
tracked door delivery
Courier, rest of India
up to a week
tracked door delivery
THE CHATBOT QUOTES THESE SAME NUMBERS — POLICY FROM MEASUREMENT, NOT WISHES
U9
The mailer: campaigns that clean up after themselves
Subscriber intakecustomers, enquiries, exhibitions — verified before use
→Campaignsthrottled, gentle sending→
Opens & clicksmeasured from our own server logs
→Suppressionbounces, complaints and unsubscribes removed automatically
Re-engagement mails go only to leads that went quiet — never to anyone
who opted out, complained, or bounced.
U10
Content, languages & case studies
20 languageshybrid translation systemDeepSeekdrafts page copyGeoIPcountry → currency10 currenciesdaily rates, billing in INREmbeddingsmeaning as vectors, everywhere
CASE-STUDY LINE
Real deploymentsactual customers and their installations
→AI draftsfrom first-party facts only→12 case studiespublished under /a/→
× 20 languagesthrough the same translation line
U11
Who runs what
Public web servernginx → Flask site · search service · livechat — behind CloudFront
ERP serverorders, manufacturing, finance, CRM back office, scheduled jobs
Rented computethe heavy SEO pipeline runs by the hour, then shuts down
StoresDynamoDB · Redis · S3 · shared storage
CloudFrontnginxFlaskDynamoDBRedisS3
J1–J22
The connector panel
Everything the website plugs into. Teal brings visitors and data in · blue moves operations
and money · amber is AI.
Google Ads API
collection · negatives · ad groups · conversion upload
Search Console
query data in · sitemaps out
Merchant Center
shopping feeds from productdb
Amazon SP-API
marketplace listings, valid configs only
LinkedIn API
lead conversions reported back
Razorpay
payments + instant confirmation
Courier APIs
live shipment status on your order page
Exotel
phone-call enquiries into CRM
Google Chat
the team is pinged on every lead
Email ingest
mailbox enquiries become tickets
Transactional mail
quotes, order updates, auto-replies
WhatsApp
one-tap contact, journey-tracked
Anthropic Claude
livechat engine + the agents that maintain this system
Amazon Bedrock
fallback chat engine · AI search assist
DeepSeek
drafts page copy at scale
Sentence-transformers
the embedding model behind search + SEO
AWS Textract
visiting-card OCR at exhibitions
AWS Translate
part of the 20-language system
MaxMind GeoLite2
country-level location → currency
Exchange rates
daily, 10 display currencies
CloudFront + S3
CDN, media, cache-busted assets
DynamoDB · Redis
system of record + the in-memory brain
GENERATED FROM THE CODEBASE · NUMBERS ARE LIVE MEASUREMENTS, NOT ESTIMATES
Logos are simplified marks of their respective owners, used to identify the
integrated services. More depth on each subsystem: see the technical documentation index.