← Back to browse

LightInk

This project tries to mimic the 90s solar digital watches that run forever. But with newer technology (eInk/WiFi/BT/Lora/GPS, ...). The challenging part of this project is to minimize the ESP32 on time to sub "ms" levels while updating the display. This was done with re implementation of SPI in the...

Added May 1, 2026 · Last analysed May 1, 2026 · via · 78% unique tagline

StackScope is a free public catalogue of indie launches. We find launches on Product Hunt, Hacker News and similar feeds, then crawl each site to detect its tech stack and score it for launch readiness: DNS, security headers, SEO basics. This page is what we saw on 1 May 2026; the live site may have changed since.

LightInk looks production-ready overall, with complete legal pages and a thorough launch checklist. Visible gaps: missing several security headers, no sitemap, and incomplete email security.

Launched on Product Hunt on May 1, 2026. The site is hosted on Supply Frame in the United States. We've detected 10 technologies on this site, covering advertising, analytics, consent tooling, and DNS providers. The stack includes Usercentrics, Adobe Fonts, and Amazon Publisher Services.

If you own this site, refresh the snapshot and see the full fix list any time →

7.5
StackScope Score
Good
100/100 Launch Readiness
Launch ready
3/3 Legal
Complete
1/2 Crawl files
Partial
Vibe Score 0 · No AI signals
How much the site looks AI-generated. Informational pattern-match signal, not a verdict. Does not feed the StackScope Score. See which fingerprints fired →

Tech Stack (10)

Infrastructure
DNS AWS Route 53
Security HSTS (2)
Email
Business email Google Workspace (2)
Email marketing Mailchimp (2)
Build & Framework
Font Adobe Fonts
Video YouTube (2)
Analytics & Marketing
Advertising Amazon Publisher Services
Analytics Google Analytics (2)
Consent Usercentrics (4)
SEO Google Search Console

Infrastructure

Network
AS62698 · US
DNS
AWS Route 53
Authoritative nameserver
DNSSEC
Not enabled
DNS responses unsigned. Cache-poisoning vulnerable.
SSL Certificate
Let's Encrypt
Valid 13 Apr 2026 to 12 Jul 2026
Certificate as captured in this snapshot, not a live check.

Email Security

SPF ~all Soft-fail (~all). Common and accepted.
DKIM Detected via known email provider
DMARC Not published. Receivers fall back to permissive defaults.
MTA-STS mode=enforce Enforce mode. Strong, blocks plaintext fallback.
TLS-RPT Reporting endpoint configured. Receivers can tell you about TLS failures.

Storage (11)

Cookies (9)
NameLifetimeDetected as
amzn_consent 27d Amazon Publisher Services
hackaday.io.sid 23h -
supplyframeUserId 12mo -
VISITOR_INFO1_LIVE 5mo YouTube
VISITOR_PRIVACY_METADATA 5mo YouTube
YSC session -
_csrf session -
__Secure-ROLLOUT_TOKEN 5mo -
__Secure-YNID 5mo YouTube
Local storage (2)
KeySizeDetected as
ucData 2.2 KB Usercentrics
ucString 532 B Usercentrics

Readiness Breakdown How?

Custom title and meta description
Open Graph tags (title, image, description)
Twitter card meta tags
Canonical URL declared
Responsive viewport meta tag
Favicon present
Semantic HTML (nav, main, article)

AI Stance

No AI stance declared
llms.txt published
No AI bots blocked in robots.txt
? No directive declared
? None advertised

Well-Known Files

robots.txt
sitemap.xml
security.txt
llms.txt
ads.txt
humans.txt
Privacy Policy
/company/privacy
Terms of Service
/tos
Consent manager: Usercentrics
0% unique

Security Headers (3/6)

Permissions-Policy experimental (check browser support)
X-XSS-Protection deprecated (use Content-Security-Policy)

Performance

632ms response time
Faster than 25% of sites
7 third-party domains loaded

Build

Code splitting
11 JS files
1 CSS files
7 Third-party domains

Brand Colours

Something not look right? If a technology shown here is wrong or out of date, email [email protected] and we'll review it.