Edge Computing: Local Processing for Sites the Internet Cannot Be Trusted To Serve
Edge computing means running rules, alarms and data capture on a device at the site itself, instead of depending on a constant cloud link. GullySystem builds this for locations where connectivity is weak or a delay is not acceptable.
What Edge Computing Means in Practice
Instead of sending every reading to a distant server before anything can happen, an edge gateway sitting at the site itself makes the immediate decisions and only sends summaries onward.
A Gateway at the Site
A small device on your premises that reads sensors and controllers directly, evaluates rules locally, and stores results even when nothing beyond the site is reachable.
Local Rule Execution
Threshold checks, simple control logic and alarm decisions run on the gateway itself, so a slow or broken internet link does not stop the equipment from being watched.
Selective Cloud Sync
Only summarised or important data is sent onward, which reduces the connectivity cost at sites paying for limited or metered data.
When a Cloud-Only Setup Fails a Site
- A rural or remote location has connectivity that drops for hours at a time, and a cloud-only system goes blind exactly then.
- A control action, such as stopping a pump at a set level, needs to happen in a second, not after a round trip to a distant server.
- Sending every raw reading to the cloud costs more in data charges than the insight is worth.
- A site cannot risk equipment behaviour depending on an internet connection it does not control.
How an Edge Deployment Is Built
Gateway Selection
A device sized to the number of connections, the protocols involved and the site's power situation, rather than a single fixed model used everywhere.
Offline Buffering
Readings and events are stored locally through an outage and uploaded in order once the link returns, so the record has no gap when connectivity comes back.
Deliberate Outage Testing
Before go-live, the connection is disconnected on purpose to confirm alarms still fire, data is still stored, and any control actions still run without the cloud.
Where Edge Computing Is Worth the Extra Layer
It adds a device and some complexity, so it earns its place where the alternative genuinely matters.
- Sites with unreliable or metered connectivity
- Processes where a control decision cannot wait for the cloud
- Locations where a connectivity outage happening during an incident would be the worst possible time to lose the record
Frequently asked questions
Is edge computing necessary if our site has good internet?
Not always. Where connectivity is reliable and no decision needs to happen instantly, a simpler cloud-only setup can be enough. Edge computing earns its cost at sites where the link cannot be trusted or a delay is not acceptable.
What happens to the data captured while the connection is down?
It is stored on the gateway itself and uploaded in the correct order once the link returns, so the record stays continuous instead of having a hole where the outage occurred.
Can the gateway control equipment directly, not just record readings?
Yes, within agreed limits. Outputs such as stopping a pump or closing a valve can be driven from the gateway, always with a manual override and a logged record of the action.
How is this tested before we rely on it?
The connection is deliberately disconnected before go-live to confirm alarms still sound, readings are still stored, and any control logic still runs without the cloud, rather than taking offline behaviour on trust.
Does an edge gateway need a reliable power supply?
It needs power planned around the site's own reliability, which can include a battery backup for the gateway and critical sensors so a power interruption does not also take down the monitoring.
What decides the cost of an edge computing setup?
The number of devices the gateway must read, how much local rule logic is required, the connectivity options available at the site, and whether battery backup or redundant gateways are needed.
Tell us what you need.
Send a short brief and one of our engineers will come back to you — usually the same day.
- No obligation
- We reply the same working day
- Your details stay private