FAQ
Straight answers.
What HoneyBox is, what it isn’t, and how it fits a home lab or small office.
Does HoneyBox require the cloud?
No. HoneyBox is fully standalone. Management and logs stay on your local network and SD card. There is no mandatory cloud account or telemetry pipeline.
What services does it emulate?
FTP, SSH, Telnet, SMTP, DNS, POP3, IMAP, HTTPS, SMB, MySQL, RDP, VNC, and HTTP. You can enable or disable ports from the web UI.
Where are logs stored?
On the device’s SD card. You can review them via the LAN UI or by reading the card directly.
Can I get email alerts?
Yes — optional email alerts can be configured locally. You’re not forced into a vendor notification cloud.
How does HoneyBox compare to StingBox?
Both are plug-and-play honeypot appliances. StingBox leans on a cloud dashboard and cloud-delivered alerts (email, SMS, voice). HoneyBox is local-first: logs on your SD card, LAN web UI and PWA, optional SMTP/webhooks you control — no mandatory vendor cloud. See the full breakdown on the Compare page.
Is this a firewall or IDS replacement?
No. HoneyBox is a decoy and visibility tool. Keep your firewall, updates, and least-privilege practices. HoneyBox shows you who’s knocking — it doesn’t replace prevention.
Is it safe for a small office?
Yes when placed thoughtfully (ideally segmented). It’s designed for home labs and small offices that want local visibility without a cloud IDS contract.
How do I manage it from my phone?
Use the companion PWA while connected to your LAN. Link: app.localhoneypot.com.
Who makes HoneyBox?
SiloCity Labs in Buffalo, New York. See About.