SMSEagle

SMSEagle Hardware SMS Gateway solution for every business. SMSEagle is a hardware SMS gateway for sending and receiving SMS messages directly to/from GSM/3G/4G network.

The device allows you to send SMS messages without the need of Internet connection. Just put your own SIM card inside the device, plug it in your local network and use built-in API to send/receive SMS messages. Many extension plugins allow you to easily integrate SMSEagle with NMS or Authentication systems.

SMSEagle Software v6.31 Is Live! Take more control over Digital Inputs/Outputs (Digital I/O), voice calls, and webhook‑...
01/06/2026

SMSEagle Software v6.31 Is Live! Take more control over Digital Inputs/Outputs (Digital I/O), voice calls, and webhook‑based integrations.

The biggest change in this release:
👉 Support for an external DI/DO extender, which is now available as a new accessory in our store.

What this means for you:
You can extend existing DI/DO workflows beyond the built‑in I/O ports by connecting external devices, making it easier to integrate additional signals.

v6.31 also adds new capabilities that simplify everyday operations:

✅ Incoming calls support - receive calls directly on the device
✅ Advanced TTS playback speed control - better readability of voice alerts
✅ Zabbix API ACK via webhooks - acknowledge incidents from external systems
✅ Incoming call triggers - use calls as automation triggers
✅ Single OID value support in SNMP Traps - more precise notifications
✅ WhatsApp support in cleanup folders – easier message management

In addition, this release includes multiple fixes and reliability improvements across calls, workflows, LDAP, plugins, and HA clusters - helping keep existing configurations stable and predictable.

Check the full list of changes and update your device ⬇️
https://eu1.hubs.ly/H0vM-wd0

Is your crisis communication physically separated? When an incident hits, the NIS2 Directive requires organizations to s...
23/05/2026

Is your crisis communication physically separated?

When an incident hits, the NIS2 Directive requires organizations to stay operational. That includes coordinating actions and communication when standard infrastructure is no longer available.

And this is where many setups break.

A common risk is a Single Point of Failure - when a monitoring system tries to send alerts over the same network that has just failed. At the exact moment an alert matters most, it never reaches the people who need to act.

This is why physical separation and Out‑of‑Band (OOB) communication are essential.

In crisis scenarios - such as ransomware‑driven network paralysis, DDoS attacks, or BGP configuration errors - IP communication is disrupted first. Email, dashboards, and internal alerts disappear along with the network.

💡 Example:

A ransomware attack paralyzes the internal network, cutting the IT team off from standard alerts. The monitoring system detects critical anomalies but can’t send notifications through the compromised infrastructure. Because an OOB channel doesn’t share any points of failure with the internal network, the alert still reaches administrators via the GSM network - within the first minute of the incident.

That short time window allows teams to isolate systems immediately and limit the impact.

This is what operational continuity looks like in practice: not preventing incidents, but making sure critical information reaches the right people when standard channels fail.

SMSEagle supports this approach as a hardware gateway, delivering the most critical parameters - such as server‑room temperature, UPS status, or intrusion attempts - directly to a mobile phone, without relying on IP connectivity.

The article linked below explains how OOB communication supports business continuity and incident response under NIS2 ⬇️

What if your MFA system stops you from fixing an outage? The NIS2 Directive requires the use of multi‑factor authenticat...
11/05/2026

What if your MFA system stops you from fixing an outage?

The NIS2 Directive requires the use of multi‑factor authentication (MFA).

However, cloud‑based systems or push‑notification solutions have a significant limitation: they need an Internet connection to deliver the code to the user.

During a DDoS attack or a routing failure, a paradox appears. An administrator has to log in to systems to restore connectivity, but can't do so because the MFA system can't send the code over a non‑working network.

So how can you avoid being locked out?

The solution is to move OTP code delivery into your own infrastructure. This is how the SMSEagle hardware gateway works: it sends 2FA codes via an Out‑of‑Band channel (outside the IP network).

That gives concrete technical benefits:

✔️ Authentication stays possible even when the network is completely isolated (air‑gapped).
✔️ External SMS brokers and cloud intermediaries are eliminated.
✔️ Data about code delivery and login attempts stays inside your infrastructure.

By using a local SMS gateway as the core of your MFA system, you regain full control over authentication data, in line with risk‑management requirements.

We publish an analysis of the role of local MFA in incident reporting in the article.

Link in the comments ⬇️

If your IT service provider relies only on cloud tools, an IP infrastructure failure on their end can cut you off from r...
29/04/2026

If your IT service provider relies only on cloud tools, an IP infrastructure failure on their end can cut you off from reacting.

How do you reduce this risk in practice?

Under NIS2, organizations have to implement measures proportional to the risk. In crisis communication, this usually means:

🔹 Shortening the chain of intermediaries in key processes.
🔹 Building alternative, independent communication channels.
🔹 Ensuring control over data and logs so you can show exactly what happened and when.

On‑premise solutions like SMSEagle gateways meet these requirements by limiting reliance on external communication services. They let you regain control over your critical alert channel.

💡 Example: During an incident, you decide to cut off part of your IT infrastructure from the outside network by air‑gapping it. Business systems, email, and messengers go down, but a local SMS gateway still works because it doesn't need the Internet to send alerts. This means your response procedure kicks off without delay and the tech team gets alerts instantly.

Reducing reliance on multi‑layered cloud services is a concrete step toward the operational resilience regulators require.

Because fewer intermediaries = higher security.

You'll find more details on securing your supply chain in our article.

Link in the comments ⬇️

The clock's ticking: you've got 24 hours. That’s how much time Article 23 of the NIS2 Directive gives you to send an ea...
24/04/2026

The clock's ticking: you've got 24 hours.

That’s how much time Article 23 of the NIS2 Directive gives you to send an early warning about a serious incident to CSIRT authorities.

The problem starts when those 24 hours begin without a working IP network.

DDoS attacks, ransomware, DNS failures - once they occur, standard communication channels go dark. Email, Slack, Teams, and web platforms are no longer available - and every minute matters.

So the real question is no longer whether you want to report an incident - but whether you’re still able to start the reporting process within those 24 hours at all.

This is where Out‑of‑Band (OOB) communication becomes critical.

OOB channels use communication paths that don’t share infrastructure with your primary IP network. They allow organizations to keep incident response moving while the clock keeps counting down.

In practice, this means using an independent OOB channel to support key Article 21 NIS2 requirements, including:

✔️ business continuity and crisis management
✔️ incident handling
✔️ secure emergency communication

OOB communication doesn’t replace formal CSIRT reporting channels, but it helps ensure that the 24‑hour deadline doesn’t collapse.

This is exactly where SMSEagle fits in. Our hardware SMS gateway operates over the GSM/LTE network. The device works on‑premise, doesn’t rely on the cloud, and doesn’t require Internet access to send alerts to staff and supervisory authorities.

We’ve published an article explaining how to build an incident‑reporting process that remains operational even when IP connectivity is unavailable.

You can find the article here ⬇️
https://eu1.hubs.ly/H0tQqwC0

The NIS2 Directive is the new EU cybersecurity standard mandating stricter security measures and rapid incident reportin...
17/04/2026

The NIS2 Directive is the new EU cybersecurity standard mandating stricter security measures and rapid incident reporting to protect essential services and strategic infrastructure.

It affects a wide range of organizations divided into Highly Critical and Important Entities - such as Energy, Transport, Banking, and Health, and Manufacturing, Food production, and Digital providers.

SMSEagle: your Partner in NIS2 Compliance

When traditional networks fail or cloud providers are compromised, SMSEagle ensures your communication remains resilient. Our hardware-based, on-premise solution aligns with the NIS2 Directive across four critical areas:

🔹 Fast & precise incident reporting: Deliver alerts via cellular networks even during total internet outages.

🔹 Supply Chain de-risking: Maintain 100% on-premise control, eliminating reliance on third-party cloud aggregators.

🔹 Secure Multi-Factor Authentication (MFA): Keep SMS OTP delivery within your physical infrastructure to protect sensitive credentials.

🔹 Business continuity: An independent "out-of-band" channel that stays operational when primary systems are down.

Coming soon: NIS2 deep-dive series

To help you navigate these requirements, we are launching a special series of posts over the coming weeks. Each entry will be dedicated to one of these four pillars, exploring exactly how SMSEagle helps you meet your legal obligations and secure your strategic operations.

Stay tuned for the first deep-dive!

We’re introducing a new hardware revision of the NXS‑9700‑5G. Revision 5 (Rev.5) will replace the previous Revision 4 (R...
09/04/2026

We’re introducing a new hardware revision of the NXS‑9700‑5G. Revision 5 (Rev.5) will replace the previous Revision 4 (Rev.4).

Why did we make the change?

The introduction of Rev.5 is driven by component availability constraints related to parts previously used in the Rev.4 production process. To ensure product continuity, long‑term availability, and supply chain stability, we have updated selected hardware components while maintaining full product functionality.



What’s new in Rev.5?

The new hardware revision includes the following updates:

🔹 New 5G radio module compliant with 3GPP Release 17
🔹 Updated antenna configuration: 2x omnidirectional antennas replacing the previous MIMO antenna
🔹 Newer Linux kernel version: Linux 6.12



Compatibility and functionality

The changes introduced in Rev.5 are minor from a user and system perspective. Both Rev.4 and Rev.5 platforms are fully compatible and functionally equivalent, ensuring the same features, performance, and supported use cases. No software or configuration changes are required when migrating from Rev.4 to Rev.5.



Availability

Starting April 2, 2026, all new orders of NXS-9700-5G devices will be fulfilled with the Rev.5 hardware revision.

Customers do not need to take any action, the transition will happen automatically as part of our standard production process.

We are happy to inform you that the latest software update for SMSEagle is now live. Version 6.30 introduces several fun...
04/03/2026

We are happy to inform you that the latest software update for SMSEagle is now live. Version 6.30 introduces several functional improvements and new tools designed to give you more direct control over your device and communication workflows.

This release focuses on practical enhancements to system automation and security. Key updates include:

💠New Allow/Deny List: We have replaced the traditional blacklist with a system that allows for bi-directional control of both incoming and outgoing SMS traffic.
💠Modbus TCP Support: The system can now read values directly from registers in devices like PLCs or sensors and automatically trigger SMS alerts when specific conditions are met.
💠Configuration Wizard: A new step-by-step guide is available to help with initial software setup, including SIM card configuration and basic system settings.
💠Expanded Workflow Triggers: New automation options have been added for message delivery statuses (Sent, Error, Delivery Report) and dynamic routing for email-to-SMS recipients.
💠Extended API Endpoints: The API now supports programmatic Digital I/O control and provides real-time health checks for services like MQTT, SNMP, and HA-clusters.
💠IP Access Rules: You can now define specific IP addresses or ranges that are permitted to access the web GUI and API.

In addition to these major updates, we have included numerous usability refinements to make your daily work smoother and more efficient.

You can find the full description of all new features and improvements on our blog, link in comments!

A new SMSEagle accessory is coming soon. It’s built for NXS and MHD devices and is designed to expand your digital input...
19/02/2026

A new SMSEagle accessory is coming soon. It’s built for NXS and MHD devices and is designed to expand your digital input and output capabilities significantly. More ports. More flexibility. More control over external devices.

If you work with industrial automation, monitoring systems, or security infrastructure, this one is for you.

Stay tuned. Full details coming soon.

In regulated banking environments, reliability and control over message delivery are critical. Raiffeisen Bank uses SMSE...
05/02/2026

In regulated banking environments, reliability and control over message delivery are critical. Raiffeisen Bank uses SMSEagle to send operational SMS alerts from monitoring systems and deliver OTP messages with full local control.

No public cloud. No external SMS providers. Just predictable delivery, on-premise infrastructure, and compliance-ready communication.

See how SMSEagle supports secure banking workflows.
Link to the case study in the comments.

Adres

Ulica Piątkowska 163
Poznan
60-650

Godziny Otwarcia

Poniedziałek 08:00 - 17:00
Wtorek 08:00 - 17:00
Środa 08:00 - 17:00
Czwartek 08:00 - 17:00
Piątek 08:00 - 17:00

Strona Internetowa

Ostrzeżenia

Bądź na bieżąco i daj nam wysłać e-mail, gdy SMSEagle umieści wiadomości i promocje. Twój adres e-mail nie zostanie wykorzystany do żadnego innego celu i możesz zrezygnować z subskrypcji w dowolnym momencie.

Skontaktuj Się Z Firmę

Wyślij wiadomość do SMSEagle:

Skróty

Udostępnij