// OPERATIONAL DOMAINS

Where generic software
stops working.

Cloud analytics and off-the-shelf IT software struggle when physical safety, patient privacy or autonomy are on the line. These are the six domains we build for, and what changes in each.

SECTOR 01

Healthcare & Clinical Medical Devices

RUNTIME: SciBor Embedded Compute Engine
COMPLIANCE POSTURE: HIPAA § 164.312 · Zero PHI Egress
LOCAL REACTION: < 1μs Query Response

Hospital Wi-Fi is not a clinical instrument

A bedside monitor, an infusion pump or a surgical display can't lean on hospital Wi-Fi. Send raw biometric waveforms to a third-party server and you take on regulatory liability under HIPAA and GDPR. Worse, ingress latency delays the alarm during a rapid decompensation.

What the bedside monitor does instead

SciBor puts an in-process columnar database on the monitor itself. Streams land in local RAM, and rolling National Early Warning Scores (NEWS2) update in sub-microsecond time through embedded DBSP. The waveforms stay on the device. Only cryptographically signed clinical alerts cross the hospital LAN, and only when authorized.

// CLINICAL DATA BOUNDARY POSTURE
TELEMETRY LAYER EXECUTION LOCATION PRIVACY & COMPLIANCE POSTURE
High-Rate Waveforms (ECG/PPG) Local Device RAM Ring Buffer Zero cloud egress; evaluated in-process
Rolling Vital Indices (NEWS2) DBSP Materialized View Calculated locally in < 1μs; zero WAN dependency
Clinical Summary Alerts Local Hospital LAN / EHR Bridge Authenticated HL7/FHIR delta sync only
100%
On-Device Data Residency
< 1μs
Local Alert Evaluation
Zero
Raw PHI Cloud Transmission
SECTOR 02

Robotics & Autonomous Edge Systems

DEPLOYMENT: SciBor In-Process Columnar Engine
OFFLINE OPERATION: 100% Autonomous Execution
CONTROL CYCLE: < 1.0ms Closed-Loop Reaction

When the warehouse eats the signal

AMRs, warehouse fleets and robotic manipulators work in metal-dense buildings and underground tunnels where wireless coverage is erratic. Tie their telemetry and predictive analytics to a cloud service, and the robot stops — or navigates blind — the moment that link drops.

Querying its own history, on the robot

SciBor embeds a high-throughput columnar store and stream processor inside the robot controller process. Joint torque, motor thermal gradients and kinematic positions land in pre-allocated RAM buffers. From there the robot queries its own rolling history in microseconds, adjusting velocity envelopes and making preventative stops with no uplink at all.

// KINEMATIC TIMING BUDGET BREAKDOWN
INGESTION
< 100μs
Atomic ring buffer
DBSP DERIVATIVE
< 350μs
Torque variance check
ACTUATOR RAMP
< 250μs
Velocity slew update
TOTAL LOOP
< 1.0ms
Within 120 FPS window
120 FPS
Kinematic UI Streaming
0 ms
Network Query Dependency
SIMD
Hardware-Vectorized Batching
SECTOR 03

Web, Desktop & Mobile Software (SciBor Light)

RUNTIME BUNDLE: < 48 KB (Wasm + Gzip)
SCRIPT PRIVACY: First-Party In-Process Linked
STORAGE MODEL: Bring-Your-Own-Cloud (Zero SaaS Tax)

You're paying twice for your own telemetry

Drop in Google Analytics, Segment, or PostHog and you've pulled 150KB+ of code you don't control into your bundle. It fights your UI thread for CPU. And more than 40%+ of desktop users never run it at all — ad-blockers and Safari Intelligent Tracking Prevention see to that. Then the invoice arrives: per-event pricing that charges you more for growing.

One linked library instead of four script tags

SciBor Light is a dependency-free stream processor compiled into your application binary or web bundle. Telemetry batches into Apache Arrow columnar tables in RAM, off the main thread. The client computes its own aggregations, there are no third-party script tags left to block, and compressed columnar batches flush straight to your own cloud storage.

// In-process telemetry registration with zero external script tags
import { SciBorClient } from '@macrodataware/scibor-light';

const telemetry = new SciBorClient({
  bufferCapacityBytes: 2 * 1024 * 1024, // 2MB pre-allocated ring buffer
  flushIntervalMs: 5000,
  storageDestination: 'https://telemetry.yourdomain.internal/v1/arrow-sync',
});

// Record structured telemetry with zero main-thread UI allocation
telemetry.record('session_latency', {
  route: '/dashboard/analytics',
  renderDurationMs: 8.4,
  memoryUsedMb: 42.1,
});
< 48 KB
Gzip Runtime Bundle
100%
Ad-Blocker Invisibility
BYOC
Zero Per-Event SaaS Taxes
SECTOR 04

Electric Power Transmission & Substations

CORE PROTOCOL: IEC 61850 MMS / GOOSE
SYNCHROPHASORS: IEEE C37.118 (120 FPS)
BREAKER REACTION: < 4ms Trip Time

Four milliseconds to be right

Substations are absorbing more volatility as renewable generation comes online, and their digital relays are a target for command injection. One false trip command can cascade through the busbars. An unverified phase drift can do the same — regional blackout inside seconds.

Where the trip decision is made

RooTrust evaluates synchrophasor PMU measurements (IEEE C37.118) at 120 frames per second inside the relay microkernel. GOOSE messages come off raw Ethernet in under 4ms, and every trip command is checked against the physical substation topology before a breaker coil energizes.

// SUBSTATION PROTECTION COMPARISON
CAPABILITY CONVENTIONAL RELAYS ROOTRUST MICROKERNEL
GOOSE Message Handling IP software stack; 10–25ms delay Raw Ethernet zero-copy; < 4ms deterministic
Actuator Safety Envelope Software credential validation only Physical topology interlocks + HSM signatures
Memory Allocation Dynamic C/C++ heap allocation #![no_std] Rust; zero heap allocation on hot path
120 FPS
PMU Synchrophasor Sampling
< 4ms
Breaker Trip Evaluation
IEC 61850
Native GOOSE / MMS Parsing
SECTOR 05

Crude & Refined Products Pipelines

REGULATORY: API 1130 · 49 CFR Part 195
SURGE PROTECTION: Joukowsky Pressure Limiting
BLACKOUT FAILOVER: 30-Day Autonomous Safe State

Why a valve must not close quickly

A transcontinental pipeline runs for thousands of kilometers through terrain with nobody in it. Its remote block valves talk over an intermittent satellite link. Slam one shut too fast and the fluid's kinetic energy becomes an acoustic pressure surge — water hammer — strong enough to rupture a weld.

Slew rates, enforced in firmware

RooTrust runs microkernels directly on the block valve RTUs. The firmware enforces a maximum valve slew rate calculated from Joukowsky's equation (ΔP = ρ · c · Δv). When the satellite link fails, edge nodes read their own acoustic sensors and pressure gradients and perform a controlled mechanical shut-in on spring-return actuators, with no upstream oversight.

// HYDRAULIC SURGE MITIGATION SPECIFICATION
ACOUSTIC WAVE SPEED (c)
~1,100 m/s
Crude oil acoustic transit
SLEW RATE CLAMPING
ΔP ≤ P_design
Controlled ramp profile
OFFLINE AUTONOMY
30 Days
Continuous blackout survival
0 Heap
Allocations on Hot Path
0.01%
Pressure Variance Sensitivity
30 Days
Air-Gapped Blackout Autonomy
SECTOR 06

Municipal Water & Wastewater Works

CORE PROTOCOL: OPC UA / Modbus RTU
STANDARDS: AWWA Guidance · Ten States
INTERLOCK: Chemical Feed Physical Ceilings

When the SCADA password is the only lock

Water treatment plants run on tight budgets and legacy Modbus PLCs. They are also a target — intruders go after the chemical feeders, trying to override sodium hydroxide or chlorine dosing. You're staking drinking water on a password.

A ceiling the pump cannot cross

RooTrust enforces parameter limits at the RTU output layer. Chemical metering pump stroke lengths and pulse-width frequencies are bounded in firmware. Compromise the admin account or the SCADA HMI workstation and the chemical feed still cannot exceed its statutory drinking water safety limit — because the limit is not in the software.

// CHEMICAL FEED PHYSICAL INTERLOCK CEILINGS
CHEMICAL FEEDER STATUTORY SAFETY BOUND ROOTRUST HARDWARE ENFORCEMENT
Sodium Hydroxide (Caustic Soda) Target pH 7.2 – 7.8 (Max 8.5) Pump stroke locked to 10% maximum travel
Chlorine / Sodium Hypochlorite Max Residual ≤ 4.0 mg/L PWM frequency clamped at microkernel register boundary
Coagulant (Alum / Ferric) Turbidity < 0.3 NTU Dosing rate tied to raw water flowmeter pulse invariant
100%
Hardware Interlock Enforced
AWWA
Cybersecurity Guidance Compliant
Modbus RTU
Legacy PLC Drop-in Retrofit

Tell us about your operation

You'll reach engineers who have worked in your kind of plant or clinic.

Book a technical call