← Back to browse

Baack

Api first DXP and headless CMS

Developer Tools

Added May 13, 2026 · Last analysed May 13, 2026 · via

StackScope records what new websites are built with, the week they launch. Most we find ourselves, by watching public internet infrastructure for brand-new sites; the rest come from Product Hunt, Hacker News and PeerPush. We crawled this one for its tech stack and scored it for launch readiness: DNS, security headers, SEO basics. This page is what we saw on 13 May 2026; the live site may have changed since.

Every technology below links to its own page: which other new sites launched with it. Vendors and agencies watch those pages with Stackdar and hear about new adopters the week they ship, from £15 a month.

Baack is partway there, with clean crawl signals. What needs work: missing several security headers, incomplete legal pages, and tracking cookies set before any opt-in.

Launched on Product Hunt on May 13, 2026. The site is served through AWS CloudFront. The crawl picked up 12 technologies on this site, covering analytics, auth, CDN, and cloud. The stack includes Foundation, Google Sign-In, and Amazon Web Services.

For context, it's a rare Foundation sighting, just 3 in our data.

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

5.2
StackScope Score
Fair
64/100 Launch Readiness
Well prepared
2/3 Legal
Partial
2/2 Crawl files
Complete
Vibe Score 8 · Few 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 (12) · Scale-up stack

Infrastructure
CDN AWS CloudFront
Cloud Amazon Web Services
DNS Namecheap DNS
Security Google reCAPTCHA (2)
Email
Business email Google Workspace
Email marketing HubSpot
Build & Framework
Auth Google Sign-In
CSS framework Foundation
Font Google Fonts
JavaScript library jQuery
Package CDN Google Hosted Libraries
Analytics & Marketing
Analytics Google Analytics (3)

Email Security

SPF Not published. Your domain can be spoofed in phishing emails.
?
DKIM Not detected at common selectors. Your provider may use a custom one.
DMARC Not published. Receivers fall back to permissive defaults.
?
MTA-STS Not deployed. Mail to your domain can be downgraded to plaintext en route.
?
TLS-RPT Not configured. You won't hear about silent SMTP TLS handshake failures.

Storage (2)

Cookies (2)
NameLifetimeDetected as
_ga 1y Google Analytics
_ga_5GRVSSW4YB 1y Google Analytics

Readiness Breakdown How?

Custom title and meta description
Responsive viewport meta tag
Favicon present
Semantic HTML (nav, main, article)
Page title is 65 characters (advisory) Google only shows about 60 characters of the title in search results; aim for 50–60 to keep the whole thing visible.
- Open Graph tags (title, image, description)
- Canonical URL declared
- Twitter card meta tags

Vibe Score Breakdown How?

SignalPoints
AI writing signals +3
Round-number metric claim +5

This score is based on structural patterns and is not definitive. Many legitimate sites may trigger signals, and AI-built sites may go undetected. It should be treated as an indicator, not a verdict.

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 (105 URLs)
security.txt
llms.txt
ads.txt
humans.txt
Privacy Policy
/privacy
? Terms of Service not detected
? Consent manager not detected
Analytics set tracking cookies on our visit, with no opt-in step.
54% unique

Security Headers (0/6)

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

Performance

214ms response time
Faster than 61% of sites
8 third-party domains loaded

Build

Code splitting
10 JS files
4 CSS files
8 Third-party domains
Something not look right? If a technology shown here is wrong or out of date, email [email protected] and we'll review it.