We make technology behave.
Grant us the right access – APIs, consoles, top-level reads – and Secure builds a working understanding of your estate: what’s there, how it behaves, what state it’s really in. Understanding becomes control; control makes change safe. You own the infrastructure. We mind it.
born in cyber – every design starts from the threat model, not the feature list
if a task doesn’t need judgement, it doesn’t need a person – we script the repetition away
the tooling that runs our own estates, every day – we’re customer zero
open exports, your hardware, documented handover – leave whenever you like
You can’t control what you don’t understand.
Most estates aren’t short of tools. They’re short of a single, current, honest picture – what’s out there, how it’s configured, what changed and why. Without that, every change is a gamble and every alert is noise.
The diagram is three years old
The estate lives in one engineer’s head and a Visio file from two reorganisations ago. Nobody is quite sure what’s actually out there.
It worked when it was installed
Undocumented changes pile up until configuration and reality disagree. The estate still runs – and nobody can say exactly why.
Too fragile to change
Everyone agrees it should be better. Nobody dares touch it, because nobody can predict what breaks. So it stays as it is.
Alerts you’ve learned to ignore
Hundreds of messages in a dozen device dialects. After the tenth false alarm, people stop reading – and the eleventh is the real one.
Tuesday, 03:12. Nobody got woken up.
A gateway power supply starts sagging in the small hours. Fourteen sensors go quiet, the LoRaWAN network server (LNS) floods with join failures, and an off-the-shelf NMS would have paged a human for each of them.
Secure reads the storm as one incident, names the component, checks it against the baseline, and queues the fix for the morning – with the overnight evidence already written up.
Show us the APIs. We’ll show you your estate.
Secure reads what you grant – vendor and cloud APIs, consoles, SNMP, flows, syslog, your LNS – read-only by default, least privilege always. From the firewall to a sensor on a lamp post: if it can be read, it can be understood.
Switching & Wi-Fi
Port health, PoE budgets, spanning tree surprises, AP client experience and rogue-AP detection.
WAN, VPN & links
Circuit utilisation, latency and jitter baselines, tunnel health, failover that actually fails over.
Firewalls & edge
Rule hygiene, session anomalies, certificate and firmware currency – watched with a security eye.
Servers & services
Host vitals, service reachability, disk and cert expiry forecasts, backup job verification.
Cloud & SaaS
Tenancy health, API quotas, spend anomalies and the dependencies your services quietly stand on.
LoRaWAN fleets
Gateways, join health, RF noise, airtime and duty cycle, battery forecasts, device identity and key hygiene – the estate most NMS tools cannot see at all.
AI that reads. Engineers who decide.
The model does the reading, mapping and explaining. Changes to your estate are made by engineers, under change control, with an audit trail – the AI proposes, a human disposes.
The estate, modelled
Reads configs, APIs and telemetry into one living model – what exists, how it connects, what depends on what. The picture nobody quite had, kept current.
Learns normal, flags weird
Thresholds are guesses; baselines are evidence. Secure learns each element’s rhythm and surfaces deviations – including the quiet kind that precede failures.
Plain-English incidents
Every incident closes with a written narrative: what broke, why, what was done, what to change. Readable by a director, not just an engineer.
Sees failures coming
Battery curves, disk growth, certificate expiry, duty-cycle creep – the predictable failures get scheduled as maintenance instead of arriving as outages.
Change, drafted
Each finding arrives with a proposed change drawn from your estate’s history. Engineers approve, amend or reject – and the system learns from that, too.
Security-tinted ops
An outage and an intrusion can look identical in minute one. Anomalies are treated as guilty until explained – a habit we brought from cyber security.
We speak LoRa natively.
Thousands of battery devices, gateways on rooftops, a network the client actually owns – LoRaWAN estates are wonderful – and, in our experience, almost always a blind spot. Secure treats them as first-class infrastructure: same model, same baselines, same understanding as the rest of your estate.
The network behind the bins
Secure is the network layer behind BinSense, whose smart-waste deployments run on LoRaWAN networks the council owns – designed, secured and, where wanted, operated by Secure.
That model is the point: the authority keeps the asset, chooses who runs it, and can host any compliant vendor’s sensors on it – bins today, gullies, air quality and damp monitoring tomorrow. No vendor cloud holding your infrastructure hostage.
BinSense and Secure are part of the same group (CIaaS Limited) – we say so plainly.
The DfE standards, implemented.
The Department for Education publishes digital and technology standards that schools and colleges are expected to meet – covering cyber security, filtering and monitoring, and the network itself. We help schools, colleges and trusts get there and stay there: a gap review against each standard, a costed plan in plain English, and monitoring that shows it still holds next term.
Cyber security standards
Firewalls properly configured, accounts on least privilege with MFA, patching current, backups tested – mapped to the DfE’s cyber security standards, not a checklist of our own invention.
Filtering & monitoring
The filtering and monitoring standards met with systems you choose – deployed properly, tested regularly, and reported in a form a designated safeguarding lead can actually read.
Switching, wireless & broadband
Network, cabling and Wi-Fi assessed against the DfE’s connectivity standards – then watched in the same console as everything else, so compliance outlives the audit.
Understand. Control. Change.
That’s the offer, in order – start where it hurts. Every tier includes the living estate model and a monthly report written in plain English – no figures we can’t stand behind, no contract theatre.
Understand
For estates nobody fully trusts on paper – we build the picture.
- Estate read via APIs & granted access – read-only, least privilege
- A living model – topology, configs, dependencies, baselines
- Risks, gaps and quick wins, written in plain English
- Findings walkthrough with your team – and a proposed route to better
Control
The estate kept in a known state – we find, we fix, you sleep.
- Everything in Understand, kept continuously current
- Drift caught, incidents understood – response under agreed times
- Patching, config management & change control with audit trail
- Vendor liaison – we sit on hold so you don’t
Change
Managed change to a better state – designed, executed, evidenced.
- Change programmes – consolidation, migration, automation – de-risked by the model
- Design & commissioning of networks and systems you own – incl. council LoRaWAN
- Security architecture from day one, not bolted on
- Handover documentation – built to be operable by anyone
On pricing: it depends on your estate, so we won’t print a number we’d have to caveat into meaninglessness. The 30-minute review ends with a written scope and a fixed quote – and if Secure isn’t the right fit, we’ll say so.
Born in cyber security. It shows.
Guilty until explained
Anomalies get investigated like incidents, not snoozed like notifications. Most are innocent. The habit is the point.
Least privilege – even for us
Collectors are read-only by default and connect outbound only. Write access exists where you grant it, logged when we use it.
Evidence, not vibes
Every incident closes with a written narrative and every monthly report shows its workings. If we can’t evidence it, we don’t claim it.
UK-based, UK-hosted
Your telemetry stays in UK regions, and the people reading it are here too – a phone call, not a ticket queue in another timezone.
Asked by every IT manager. Answered straight.
What does Secure actually do?+
Three things, in order. Understanding – grant us APIs and top-level read access and we build a living model of your estate. Control – baselines, drift detection and change control keep it in a known state. Managed change – we design and execute the route to a better estate, and evidence it. We’re a solutions practice, not a product – networks, LoRaWAN, AI, cloud, or the kit you already own.
Is Secure an NMS?+
No. An NMS hands you dashboards and alerts and leaves the understanding to you. We use monitoring instruments where they earn their keep, but the offer is the understanding itself – a current, honest model of your estate – and the control and managed change that follow from it. If you want a tool to watch, there are plenty. If you want the estate to get better, talk to us.
How does Secure connect to our network?+
Through access you grant, and nothing else – vendor and cloud APIs, read-only credentials, SNMP, flows, syslog, and your LNS for LoRaWAN. A lightweight collector sits inside your estate and connects outbound only – no inbound holes in your firewall. Read-only by default; write access exists only where Control or Change work needs it, granted by you, logged when used.
Where does our data live – and what do you actually see?+
Telemetry is processed and stored in UK regions, encrypted in transit and at rest. We see device health and traffic metadata, not your payload content. Retention is agreed in the service definition, and our privacy notice covers the rest.
Is the AI making changes to our network?+
No. The AI reads, correlates, explains and proposes. Changes are made by engineers under change control with a full audit trail – and only under Control or Change engagements, only with the access you’ve granted. The day we let a model push config unsupervised is the day we deserve to lose your business.
Do you only do LoRaWAN?+
No – switches, Wi-Fi, firewalls, WAN, servers and cloud are the bread and butter. LoRaWAN is the speciality because most mainstream tools have no native LoRaWAN visibility, and because our group builds council-owned LoRaWAN networks that deserve a current, honest model – not a dashboard nobody reads.
Can you help our school meet the DfE digital standards?+
Yes. We run a gap review against the DfE’s digital and technology standards – cyber security, filtering and monitoring, switching, wireless, broadband and cabling – and give you a costed plan in plain English. If you want, we then implement it and keep the estate monitored, so when a governor asks “are we still meeting the standards?” the answer comes with evidence.
What happens if we leave?+
You take everything: the estate model and its documentation, full telemetry export in open formats, the collector uninstalled cleanly. What we build is handed over with documentation written to be operable by anyone. Lock-in is a business model; it isn’t ours.
Who is behind Secure?+
Secure is the solutions and network arm of CIaaS Limited, a UK group founded from a cyber-security background. It grew out of running the group’s own deployments – including the council LoRaWAN networks behind BinSense (council smart waste) – and offers the same tooling and engineers to estates like yours. Where our companies work together on your project, we say so plainly – you’ll never discover the relationship in the small print.
Thirty minutes. Bring the estate you have – we’ll talk about the one you want.
A review with an engineer, not a salesperson: what you run, where it hurts, where we’d start. You leave with a written scope and a fixed quote – and if it’s not a fit, we’ll say so.