One stop for every sensor, and every assistant that needs it.
Sensor orchestration for remote and autonomous platforms. Radar, AIS, cameras, LiDAR and met-ocean sensors run as one live system. Your engineers configure it. Your AI assistants query it, extend it and watch over it.
Plug in
Pick a sensor from the catalogue or describe a new one. LilyPadOS brings it online without touching the rest of the system.
Fuse
Radar tracks, AIS identities and camera frames line up on one timeline and one map. A vessel with its AIS switched off stands out on its own.
Ask
Your AI assistant connects over MCP. Ask which sensors dropped out overnight, pull last week’s tracks, or add a camera to USV 03.
Anywhere sensors work without a person beside them.
- Uncrewed vessels & sea drones
- Every sensor on the hull reporting through one control path, with health checks that act before a mission fails.
- Ports & coastal security
- Radar, AIS and cameras on one map. Contacts with no AIS flagged the moment they appear.
- Offshore wind & met-ocean
- Survey platforms that capture for months between visits and deliver clean data ashore.
- Counter-drone & perimeter
- Radar and camera tracks fused into one picture of what’s moving, and where it’s heading.
- Environmental monitoring
- Weather, water and air sensors on remote masts and buoys, over whatever link is available.
- Research platforms
- New instruments added between field seasons, without rewriting the data pipeline.
Everything between the sensor and the decision.
- Sensor catalogue
- Marine radar, AIS, cameras, LiDAR, IMU, GNSS and met-ocean rigs, ready to drop in.
- Systems of systems
- A sensor, a vessel, a fleet. Nest them as deep as the mission needs and run them as one.
- Self-healing
- A failing sensor restarts on its own. Its neighbours never stop capturing.
- Store and forward
- Compressed capture over satellite, cellular or Ethernet, delivered to your own cloud.
- Mission control
- Every system’s health and stream on one live screen, from the sensor up.
- AI-native control
- An MCP server for Claude and other assistants, with permissions set per action.
For engineers
- One config file describes the whole deployment
- API and CLI for everything the console does
- Runs on Linux edge hardware you already own
- Your data stays in your cloud
For AI assistants
- Typed tools over the Model Context Protocol
- Read health, query captures, draft changes
- A human approves every write by default
- Every action lands in the same audit trail
Proven where it’s hardest: two years unattended at sea.
LilyPadOS grew out of offshore acquisition software that has run for years without a visit, and the radar, AIS and camera fusion we built for maritime surveillance. The hard lessons came from salt water, not slides.
- offshore deployments of 12 to 24 months, still in production
- 6
- offshore deployments of 12 to 24 months, still in production
- sensor types across 5 protocols on one onboard computer
- 10
- sensor types across 5 protocols on one onboard computer
- reported uptime at sea
- 98%
- reported uptime at sea
Open where it counts.
Open interfaces, open data formats, and your data in your own cloud. We license the engine per deployment and stand behind it with support.
Asked so far
How do I get LilyPadOS?
LilyPadOS ships as part of an engagement with FrogLeap. We take on a small number of integration partners at a time. Tell us about your platform and we’ll say honestly whether it fits now or later.
Does it run offline or air-gapped?
Yes. It runs on your hardware with no cloud dependency. When a link is available it forwards data on; when it isn’t, it stores and waits.
Which sensors does it support?
Anything that talks serial, Ethernet or a vendor SDK. The catalogue covers marine radar, AIS, cameras, LiDAR, IMU, GNSS and met-ocean sensors, and we add drivers with each partner.
Which AI assistants can connect?
Any assistant that speaks the Model Context Protocol, Claude included. Reads are open to the assistant; writes wait for a human to approve them unless you change that.
Where does my data live?
On your hardware and in your cloud account. FrogLeap never holds your sensor data.
How is it licensed?
The licence comes with the engagement, support included. Interfaces and data formats stay open, so you can always take your data and leave.
How partners work with us.
- STEP 01
Bring us your platform
A vessel, a drone, a mast, a vehicle. Tell us the sensors, the link and what the data has to do.
- STEP 02
First data in weeks
We deploy LilyPadOS on your hardware and bring your sensors online, one after another, on a live dashboard.
- STEP 03
We build the rest
Fusion, dashboards, AI tooling and the integrations your customers need. The licence comes with the engagement.
Bring us your hardest platform.
Tell us what you’re sensing, where, and over what link. We’ll reply within one working day and say plainly whether LilyPadOS fits now.
- [email protected]
- Phone
- +44 7570 882808