Platform Detection
How LobsterHoney auto-detects your hosting platform and framework.
When you add a domain to LobsterHoney, the system automatically detects your hosting platform and framework. This detection drives the deployment instructions you see on the Deploy page -- ensuring you get configuration tailored to your exact stack.
What Gets Detected
Platform detection analyzes your domain to identify two things:
- Hosting platform -- where your site runs (Vercel, AWS, Cloudflare, Netlify, Heroku, DigitalOcean, or custom infrastructure)
- Framework -- what your site is built with (React, Next.js, Django, Rails, WordPress, and others)
Detection uses server-side analysis of response headers, DNS records, and infrastructure signatures. No agent or script is installed on your site for detection.
Supported Platforms
| Hosting Platform | Detection Method |
|---|---|
| Vercel | Server headers, CNAME records |
| AWS (CloudFront, EC2, ECS) | Server headers, IP ranges |
| Cloudflare | CF-Ray header, DNS |
| Netlify | Server headers, CNAME |
| Heroku | DNS records |
| DigitalOcean | IP ranges |
| Custom | Fallback when no platform signature is found |
Supported Frameworks
| Framework | Typical Stack Profile |
|---|---|
| Next.js | nextjs_vercel |
| React (SPA) | react_node_aws |
| Django | django_gcp |
| Rails | rails_heroku |
| WordPress | wordpress |
The detected framework determines which stack profile is used for trap selection. Stack profiles control which traps are most relevant for your technology stack.
Manual Override
If auto-detection is incorrect or your setup is unusual, you can manually select your platform and framework from the platform picker on the Deploy page. Manual selection overrides auto-detection immediately and updates your deployment instructions.
Platform detection runs once when you add a domain. If you migrate to a different hosting provider, update your platform selection manually on the Deploy page.
How Detection Affects Deployment
Your detected platform determines:
- Which deployment format is shown (script tag, proxy config, or both)
- Platform-specific instructions and file paths
- Which proxy configuration format is generated (Nginx, Cloudflare Worker, Vercel rewrites, etc.)
- Which trap types are recommended for your stack
See Also
- Beacon Setup -- deploying via script tag
- Proxy Mode -- advanced proxy deployment
- Managing Traps -- how stack profiles affect trap selection