

LLiDA · Low Level integrated Database Architecture
LLiDA. An offline-first real-time database, with live synchronisation.
LLiDA is the real-time time-series database developed by SkyDynamics for safety-critical and mission-critical systems. It works on the device, in RAM, on disk and at processor level, and keeps every connected node synchronised. It is the data layer AeroBrain reasons over.
What it is
The data is on the device. And every node holds the same record.
LLiDA captures real-time data, such as the data of an aircraft's avionics, as time series. It works in RAM, on disk and at processor level, on RISC-V, ARM and other architectures, from a low-level microprocessor computer to a server. Values are available to the layers above without a round trip to a server, and nodes synchronise live over secured or common networks.
- A database on a server
- Needs the link
- LLiDA
- Works on the device, syncs between nodes
Real-time time series
Avionics and sensor values are captured as they are produced, each channel read on a fixed period, so timing is known in advance.
Live synchronisation
Nodes exchange data live over secured networks or common networks, so the aircraft, the edge device and the ground hold the same record.
High reliability and assurance
Developed to the rules used for flight software, including MISRA C and the objectives of DO-178C.
LLiDA is SkyDynamics technology and part of AeroBrain. Performance figures depend on the hardware and the function: they are set with the customer and shown for each product.
LLiDA at the edge
On board, on the edge, on the iPad. Five features, one database. Choose one to see it work.
The figure follows avionics data from the sensor to the people who use it: sampled on the aircraft, held by LLiDA nodes that cover for each other, passed across a cryptographic boundary, and read on the crew's and engineers' iPads, where it can be searched by meaning.
Aircraft avionics
Safety-critical, on board
- Engine 2 vibration0.62 ips
- Exhaust gas temperature624 °C
- Hydraulic pressure3011 psi
Sampled on a fixed period
LLiDA nodes
Each holds the record
- Avionics computerARMIn sync#8224
- Edge unitRISC-VIn sync#8224
- Ground serverServerIn sync#8224
Cryptographic boundary
Identity proven by key
- Crew iPadKey verified
- Engineer iPadKey verified
- Unknown deviceRefused: no key
User devices
Through the LLiDA plugin
LLiDA plugin
Engine 2 vibration0.62 ips
Semantic search, on the iPad
engine vibration rising in icing
- Engine 2 vibration, last 10 minutes0.94Live time series
- High engine vibration procedure0.89Operator QRH
- Engine anti-ice operation0.81FCOM
On the device · Low latency · Low energy
LLiDA plugin
Engine 2 vibration0.62 ips
Every value with its time, on board.
Avionics channels are sampled on a fixed period on the aircraft and held as time series in RAM and on disk, so the layers above read them without a round trip to a server.
Time series on board
Each channel is read on a fixed period on the aircraft itself, so a reading exists at a known time without asking a server for it.
Nodes that cover for each other
There is no master copy. Each node keeps the record, so losing one node does not lose the data or stop the reads.
The iPad joins through a plugin
Crews and engineers see the on-board values on the device they already carry, and the function on board never waits for that device.
A key, or no connection
Every platform proves its identity cryptographically before it is admitted. An unknown device stays outside.
Search by meaning, locally
Vector and semantic search plugins answer "show me what looks like this" on the device, without a cloud service.
Evidence for AI
Each value keeps its source and time, so an AeroBrain answer built on it can be replayed and audited.
Illustrative figure: readings, scores and device names are invented. Timing, latency and energy figures depend on the hardware and the function: they are set with the customer and shown for each product.
Specifications
LLiDA at a glance. Every feature on one sheet.
The features of LLiDA as SkyDynamics states them. Figures for timing, latency, memory and energy depend on the hardware and the function: they are set with the customer and shown for each product.
| Criterion | LLiDA |
|---|---|
| Full name | Low Level integrated Database Architecture |
| Type | Real-time time-series database, offline first, with live synchronisation |
| Data model | Time series: every value stored with the time it was measured, channel by channel |
| Sampling | A fixed period per channel, set before the system runs |
| Storage | RAM for the working data, disk for the record, and a layer at processor level |
| Processors | RISC-V, ARM and other architectures, from a microcontroller to a server |
| Synchronisation | Live between nodes, over secured networks or common networks |
| Resilience | No single point of failure: every node holds the record; a stopped node is isolated |
| Security | Admission by cryptographic identity; data between nodes and devices protected cryptographically |
| User devices | Device plugin for crew and engineer iPads, across a defined boundary |
| Search | Vector and semantic search plugins on the device, designed for high speed, low latency and low energy |
| AI | The real-time data layer of AeroBrain; each value keeps its source and time for audit |
| Development | MISRA C and the objectives of DO-178C |
| Standards that frame it | DO-330, DO-278A, DO-326A; ECSS, IEC 62304 or IEC 61508 per programme |
| Deployment | On the device, at the edge, on premises, air-gapped; ground records in the EU, Switzerland or on premises |
| Use | On its own, or with the other AeroBrain technologies |
Certification is granted for a specific product on specific hardware, with the authority, and is shown for that product.
How it works
The life of a value. From the sensor to the audit record, in six steps.
Every value in LLiDA follows the same path, on every node. Nothing on the path needs a server to be reachable.
Sampled
The channel is read on its fixed period. The value is stored with the time it was measured.
Held in memory
The newest samples stay in RAM, where the functions above read them at once.
Written to disk
The record is kept on disk on the same node, so it survives the working window in memory.
Synchronised
Connected nodes exchange the record live, over secured or common networks.
Read where it is needed
By the function on board, by AeroBrain, and by crews and engineers through the iPad plugin.
Kept as evidence
Each value keeps its source and time, so a decision made on it can be traced afterwards.
Architecture
Low level, by design. What "Low Level integrated Database Architecture" means.
LLiDA is built close to the hardware, so that the same architecture can run on a microcontroller beside a sensor and on a server on the ground. These are its parts.
Time series as the data model
Every value is stored with the time it was measured, channel by channel. That is the shape of avionics and sensor data, so nothing has to be converted on the way in.
Fixed sampling periods
Each channel has its own period, set in advance. The system knows when a value will exist before it runs, which is what real-time functions need.
RAM, disk and processor level
The working data lives in memory for fast reads, the record lives on disk, and the lowest layer works at processor level. One architecture covers all three.
RISC-V, ARM and other architectures
The same database runs from a low-level microprocessor computer near the sensor to an avionics computer and a ground server.
Live synchronisation between nodes
Nodes exchange data as it is written, over secured networks or common networks, so the aircraft, the edge device and the ground hold the same record.
No single point of failure
Every node holds the record. A node that stops is isolated, and the other nodes keep serving the data.
Plugins
Extend it where the work is. Plugins for devices and for search, on top of the same record.
The core of LLiDA stays small and assured. Plugins connect it to the devices people carry and add search for on-device AI, without changing what runs on board.
Device plugin for iPads
Connects the crew's and the engineers' iPads to the LLiDA nodes on board, so on-board values reach the device directly. It closes the gap between safety-critical systems on the aircraft and the devices people use, while the function on board does not depend on the device.
Vector search plugin
Stores and compares vectors, the numeric form AI models give to text and signals, to find the nearest matches to a question on the device itself. Designed for high speed, low latency and low energy.
Semantic search plugin
Finds readings and passages by meaning, not only by exact words: "engine vibration rising in icing" finds the live trend, the procedure and the related limits.
AeroBrain retrieval
The AeroBrain RAG engine retrieves over LLiDA time series and approved manuals together, and each piece of evidence keeps its source and its time.
Learn more
Security
No key, no connection. Cyber security built into how platforms connect.
A database that reaches from the aircraft to an iPad must decide, every time, who is allowed in. In LLiDA that decision is cryptographic.
Cryptographic identity
Platforms connect only through their cryptographic identity. A device that cannot prove its key is refused.
Protected between nodes and devices
Data exchanged between nodes, and between nodes and devices, is protected cryptographically.
A boundary, not a bridge
User devices join across a defined boundary. The safety-critical function keeps running on its own nodes whatever happens on the device side.
Secured or common networks
Synchronisation runs over secured networks or common networks; the cryptographic layer is what makes a common network usable.
Framed by DO-326A
The airworthiness security process frames how synchronisation over networks is assessed for an aircraft programme.
Where the record is kept
On the ground, records can be hosted in the EU, in Switzerland or on your premises.
Offline first, with sync
Work without a connection. Synchronise when there is one.
The same principle runs through SkyDynamics products: the data a person needs is on the device they hold, and it synchronises with the other devices and the ground when a link exists.
On the aircraft and the edge
LLiDA holds the working data in memory and the record on disk on the node itself, so the function does not wait for a server.
AeroTechLog
Crew members make entries and read aircraft data without a connection. The data synchronises when the connection returns, and company iPads sync directly with each other, without internet.
aeroEBT instructor app
Instructors grade offline in the simulator. The session synchronises automatically, with signatures and records.
OpsEye
OpsEye keeps working on the workstation with local storage during a network outage and syncs when the connection returns.
Where it runs
One architecture. From a microcontroller to a server, and on to the iPad.
| Criterion | Processor | Role |
|---|---|---|
| Microcontroller | RISC-V | Low-level computer close to the sensor |
| Avionics computer | ARM | On the aircraft |
| Ground system | Server | Operations and maintenance |
| Crew and engineer iPads | Through the device plugin | The on-board values where people work |
Links between nodes run over secured networks or common networks.
Where it applies
Built for data that cannot wait. Six fields LLiDA is designed for.
Choose a field to see what LLiDA holds there and why its design matters. These are the fields the technology is designed for, not a list of deployments.
1 of 6
Avionics
Real-time data on the aircraft, for next-generation avionics.
Engine, systems and flight parameters are captured as time series on the avionics computer or on a microcontroller close to the sensor.
- Each channel sampled on a fixed period
- Values read without a round trip to a server
- The data AeroBrain reasons over in real time
ARM · RISC-V · DO-178C objectives
2 of 6
Maintenance
Aircraft data for the engineer at the aircraft.
Engineers read the on-board values on their iPad through the device plugin, and maintenance control on the ground holds the same record.
- On-board values on the engineer's iPad
- The same record at maintenance control
- Trends kept with their time, for later analysis
iPad plugin · Ground server
3 of 6
Operations control
Fleet data that is there when the network is not.
Operations and maintenance control on the ground hold the record synchronised from the aircraft and the edge, and keep it when a link drops.
- Ground nodes holding the synchronised record
- No single node whose loss stops the data
- Evidence for decision support, each value with its time
Live sync · Failover
4 of 6
Defence and mission systems
Disconnected and air-gapped operation.
Mission systems keep their data on the node and connect only to platforms that prove their identity cryptographically.
- Works with no connection at all
- Admission by cryptographic identity
- Synchronisation over secured networks when allowed
Air-gapped · Cryptographic identity
5 of 6
Space operations
Links that come and go, on constrained processors.
Spacecraft and ground segments exchange data only when a link exists. LLiDA keeps the data on the node and synchronises when the link is there. The software standards and evidence for a space programme are agreed with the customer.
- Data held on the node between links
- RISC-V and ARM processors
- Standards such as ECSS-E-ST-40C and ECSS-Q-ST-80C agreed per programme
Intermittent links · Edge
6 of 6
Medical and other safety-critical devices
Monitoring at the point of use.
Devices that measure and advise at the point of use need their data local, timed and auditable. The same architecture can be specified for them, at the assurance level each requires.
- Measurements with their time, on the device
- Evidence for auditable AI advice
- Framed by IEC 62304 or IEC 61508 where they apply
On device · Auditable
Each deployment is specified with the customer and its assurance level.
How it differs
Not a server database on a small computer. A different design, for a different job.
Server time-series databases are built for data centres and dashboards. LLiDA is built for the node where the data is produced and the function that depends on it.
| Criterion | Server time-series database | LLiDA |
|---|---|---|
| Built for | Collecting metrics in a data centre | Safety-critical and mission-critical functions on the node |
| Where the function reads | From a server, over the network | From memory on its own node |
| If a server or node stops | Depends on the cluster set-up | The other nodes keep serving the record |
| Smallest target | A server or a virtual machine | A RISC-V or ARM microcontroller |
| People's devices | Through a web dashboard | iPads through a device plugin, admitted by key |
| Search for AI | Usually a separate vector service | Vector and semantic search plugins on the device |
| Development rules | General software practice | MISRA C and the objectives of DO-178C |
A general comparison; individual products differ. LLiDA figures depend on the hardware and the function and are set with the customer.
A worked example
One event, end to end. Engine vibration rises in the climb, in icing conditions.
An illustrative example of how LLiDA carries one event from the sensor to the crew, the ground and the audit record. The values and the event are invented.
On the sensor
A RISC-V microcontroller beside the engine samples vibration on its fixed period and writes each value with its time.
On the avionics computer
The ARM avionics node holds the newest samples in RAM. The trend above the normal band is visible as it happens.
To AeroBrain
The RAG engine retrieves the live trend with the procedure and limits that apply, each with its source and time.
On the crew iPad
Through the device plugin the crew see the reading beside the options. A semantic search for "vibration in icing" finds the related passages on the device.
If a node stops
Should the edge unit stop during the event, it is isolated and the other nodes keep serving the record.
On the ground
Maintenance control holds the same record, synchronised over a secured link, and the crew's decision is kept with the evidence.
Assurance
Engineered so the evidence exists. The standards that frame LLiDA.
LLiDA is developed to high-assurance practice. Certification is granted for a specific product on specific hardware, with the authority, and is shown for that product.
MISRA C
The coding rules for C in critical systems, followed in LLiDA's C code.
The objectives of DO-178C
Requirements, design, code, tests and evidence traceable in both directions.
DO-330
Tool qualification, for tools whose output is relied on without further checking.
DO-278A
Ground-based systems: the ground side that the aircraft synchronises with.
DO-326A
The airworthiness security process: synchronisation over networks.
ECSS, IEC 62304, IEC 61508
Space, medical and other safety-critical fields, agreed for each programme.
What it is for
The data layer of AeroBrain. Real-time data for AI that has to be audited.
Evidence for AeroBrain
Real-time data from the aircraft's avionics is captured by LLiDA; the RAG engine retrieves over it and over the operator's approved manuals, and each piece of evidence keeps its source and its time.
Learn moreSafety-critical AI
How AeroBrain is built for safety and mission-critical work, and who decides in each use.
Learn moreAviation data hosting
Where records are kept: in the EU, in Switzerland or on your premises.
Learn more
Further reading
Go deeper. Each subject, on its own page.
Safety-critical database
What a database must do for avionics, mission-critical and space operations, and eight questions for any vendor.
Learn moreSafety-critical AI
What makes AI safety-critical, and why AeroBrain uses a small language model.
Learn moreAeroBrain
The four technologies together, with the avionics use case stage by stage.
Learn moreAssurance and standards
MISRA C, Rust, Ada SPARK, DO-178C and the related standards, in one table.
Learn moreTrust centre
Where data lives, who approves what, and the boundaries of the AI.
Learn moreGlossary
Time series, offline first, live synchronisation and the other terms, explained.
Learn more
LLiDA: questions engineers ask
What is LLiDA?
LLiDA (Low Level integrated Database Architecture) is a real-time time-series database developed by SkyDynamics for high-reliability and high-assurance systems. It works in RAM, on disk and at processor level, on RISC-V, ARM and other architectures, synchronises live over secured or common networks, and is developed to safety-critical rules such as MISRA C and the objectives of DO-178C.
Is there an offline-first database with synchronisation for safety-critical systems?
LLiDA is built for that. The working data is held in memory and the record on disk on the node itself, so values are available without a round trip to a server, and connected nodes synchronise live over secured or common networks, from the aircraft to the edge device and the ground.
Which processors does LLiDA run on?
RISC-V, ARM and other architectures, from a low-level microprocessor computer to an avionics computer and a server. The same architecture covers the working data and the stored record.
Does LLiDA have a single point of failure?
It is designed not to. Every node holds the record; if one node stops, it is isolated and the other nodes keep serving the data.
Can crews and engineers see LLiDA data on an iPad?
Yes, through the LLiDA device plugin. The iPad connects to the nodes on board across a cryptographic boundary, so on-board values reach the device directly while the safety-critical function keeps running on its own nodes.
How does LLiDA handle cyber security?
Platforms connect only through their cryptographic identity, so a device that cannot prove its key is refused, and data between nodes and devices is protected cryptographically. For an aircraft programme, DO-326A frames how synchronisation over networks is assessed.
Does LLiDA support vector search and semantic search?
Yes, through plugins that run on the device. They find the readings and passages closest in meaning to a question and are designed for high speed, low latency and low energy, for high-assurance AI at the edge.
Can LLiDA be used for space operations?
It is designed for operations of that kind: data held on the node between links, synchronisation when a link exists, and RISC-V and ARM processors. The software standards for a space programme, such as ECSS-E-ST-40C and ECSS-Q-ST-80C, and the evidence are agreed with the customer.
How does LLiDA relate to AI?
LLiDA is the real-time data layer of AeroBrain. It captures the aircraft's avionics data as time series; the AeroBrain RAG engine retrieves over that data and over the operator's approved manuals, and each piece of evidence keeps its source and its time, so an answer can be audited.
How does LLiDA relate to DO-178C?
LLiDA is developed to safety-critical rules such as MISRA C and the objectives of DO-178C. Certification belongs to a specific product on specific hardware and is shown for that product.
Can LLiDA be used on its own, without the rest of AeroBrain?
Yes. Each AeroBrain technology can be used alone; LLiDA can be the database of a system that has no AI at all, and AeroBrain can be added later on the same data.
Do SkyDynamics applications work offline?
Yes. AeroTechLog works offline at the aircraft and synchronises when the connection returns, and company iPads sync directly with each other. The aeroEBT instructor app grades offline in the simulator and synchronises automatically. OpsEye keeps working on the workstation during a network outage.
What does LLiDA stand for?
Low Level integrated Database Architecture. "Low level" because it is built close to the hardware, down to processor level; "integrated" because the same architecture covers the working data in RAM, the record on disk and the synchronisation between nodes.
Is LLiDA a vector database?
LLiDA is a real-time time-series database. Vector and semantic search are added through plugins that run on the device, so the same record can be searched by meaning for on-device AI.
How do we evaluate LLiDA for our system?
Start with a technical briefing: the signals, the processor, the network and the assurance level. SkyDynamics then shows how LLiDA holds and synchronises that data, and which evidence comes with it.
Bring your data and your hardware.
Tell us the signals, the processor and the time budget. We show how LLiDA holds and synchronises them.
We respond within one business day.
