Disruption is accelerating
Global IROP events have risen steadily over the past decade. Weather volatility, capacity constraints and infrastructure age mean recovery complexity is structurally increasing — not a temporary trend.
IROP · Structural
SoraLabs
Operational surface ·Live———18:04 LOC · V0.1 · 2026
Calm under
disruption.
Sora automatically coordinates passenger rebooking, comms and servicing when flights are disrupted —
across the systems your airline already runs on.
Scene · 01Terminal · 22:47 LOC
Somewhere tonight, a weather front is rewriting thousands of itineraries in real time.
22:47 LOC · PAX HOLD02 · Today
Operations still run on fragmented infrastructure.
When disruption cascades, recovery scales with operator effort.
5–8
Systems touched
12+
Handoffs per event
Hours
Recovery
Manual
Tooling
- 0passengers re-accommodated per major event
- 0 minmedian delay before a coordinated response
- 1 in 0operators describe peak as unmanageable
02b · Before & after
What recovery looks like today.
The same disruption event, handled by the operator's hands today — and by an orchestration layer designed to compress it into minutes.
Without Sora
Today
- Operator manually checks 5–8 systems to assess exposure
- Recovery options identified by hand, no ranked alternatives
- Passenger comms drafted and sent manually, per language
- VIP and connection passengers identified from memory or manual flags
- No single audit trail — coordination happens across email and phone
- Recovery time: hours
With Sora
Orchestrated
- Exposure resolved automatically at signal ingestion
- Ranked recovery plans generated in under 90 seconds
- Multilingual passenger comms drafted and queued, operator approves
- VIP and connection passengers automatically surfaced and prioritised
- Every action logged, attributable, recoverable
- Recovery time: minutes to operator approval
Scene · 02OCC · 02:14 LOC
Across the world, a small number of people are deciding what happens next.
OPS · NIGHT SHIFT03 · Orchestration
A flight is held.
The layer responds.
ElapsedT+00:00:00
Orchestration · Live
01 · SIGNAL02 · ANALYSE03 · PROPOSE04 · APPROVE05 · EXECUTE
PSS
INV
CRM
COMMS
GROUND
- 01T+00:00:00
Signal
A disruption enters the layer. Exposure resolves in seconds.
- 02T+00:00:42
Analyse
Rerouting and servicing paths evaluated in parallel.
- 03T+00:01:18
Propose
Ranked recovery plans, sequenced for the operator.
- 04T+00:01:55
Approve
Operator confirms. Every decision logged, recoverable.
- 05T+00:02:30
Execute
Synchronised across PSS, inventory, comms, ground.
Scene · 03Apron · T+02:14 LOC
The weather hasn't passed. The disruption has.
T+02:14 · RECOVERED04 · Product
The Operator's
Command Center.
One surface. Signal in. Plan out. Human approves.
occ.soralabs.live / disruption / sk903
Sora · OCC/Disruption
22:47 LOC
AI recommendation · T+00:01:18
Rebook 150 impacted passengers across the next three available recovery routes.
Confidence 0.00 · Aligned with SLA, crew legality and inventory across PSS, GDS and partner stock.
- Reroute eligible passengers138 · auto-paired
- Generate passenger communicationEN · SE · DA
- Flag VIP & status passengers12 · priority queue
- Prepare hotel & voucher workflowTier 2 entitlement
- Escalate exceptions to operator4 cases
Human approval required
← scroll →
Approve the plan to see execution
Representative interface · Interactive demo
05 · Architecture
An orchestration layer above existing airline infrastructure.
Sora Labs is designed to work alongside the systems airlines already run on. We listen, reason and orchestrate — we do not replace PSS, DCS or mission-critical core systems.
Existing airline infrastructure
Layer 1PSS
Passenger Service
DCS
Departure Control
INV
Inventory
CRM
Customer
COMMS
Email · SMS · App
GROUND
Airport ops
Mission-critical · Sora does not replace these
Sora Labs · Operational intelligence layer
Layer 2Signal · Reasoning · Orchestration
Operational outcomes
Layer 3Recovery
PNR re-accommodation
Servicing
Passenger comms
Coordination
Cross-system sequencing
Approval
Human-in-the-loop
06 · For Partners
Built for
PSS & ecosystem partners.
Sora Labs is designed to integrate into established airline ecosystems without replacing mission-critical core systems.
API-first integration
Non-destructive. Event-driven. No core system changes.
Enterprise deployment
Tenant isolation. Environment parity. Predictable rollout.
Operational coexistence
Runs alongside existing carrier workflows. Not competing.
Reasoning + audit layer
Adds intelligence and accountability to existing servicing.
Designed for integration with
Amadeus
Sabre
Navitaire
SITA
IBS Software
Sora Labs is not affiliated with or endorsed by these vendors. Integration is API-first and non-destructive to host systems.
Partner Briefing · Enterprise
A confidential briefing for infrastructure partners.
For Amadeus, Sabre, Navitaire and operational ecosystems exploring how Sora Labs integrates above existing PSS, DCS and servicing infrastructure.
06b · Design Partner
The Design Partner
Programme.
We are deploying with a small number of carriers in 2026.
Design partners are not beta testers. They are co-architects of the first operational deployments. We work inside your environment, alongside your OCC team, to configure and validate the orchestration layer against real disruption scenarios before any system touches production.
We are selective. We are looking for carriers and infrastructure partners who understand that the right first deployment matters more than speed.
Design Partner · 2026Cohort I
Co-architect the first deployment.
- Commitment
- 6–12 week co-design engagement
- Format
- On-site + remote operational sessions
- What you get
- Configured deployment, audit capability, direct founding team access
- Who it's for
- Airlines ≥5M annual passengers · PSS / DCS infrastructure partners
Currently reviewing: 3 of 5 remaining design partner slots
06c · Exposure
What disruption costs your operation today.
An estimate based on industry averages. Adjust for your operation.
400/ year
502,000
180passengers
50800
Coordination hours lost
312 hours / year
At 47-minute average delay before first coordinated action
Servicing cost exposure
€1.3M / year
Based on EU261 administrative burden estimates
Operator peak load events
88 events / year
Where operators describe workload as unmanageable
Estimates based on published IATA and EU261 industry data. Actual figures vary by carrier, network and disruption profile.
See how Sora compresses this →07 · Outcomes
Measurable recovery.
Designed to compress the time, effort and uncertainty of IROP recovery — for operators, for the airline, and for the passenger.
Faster recovery
Hours → minutes
Designed to reduce IROP handling from hours of manual coordination to minutes of AI-assisted operational approval.
Lower servicing load
Re-accommodation automated at peak
Built to automate repetitive PNR re-accommodation, communication and passenger servicing workflows during disruption peaks.
Better passenger outcomes
VIP, connections, accessibility flagged automatically
Helps operational teams coordinate recovery faster, reduce uncertainty and improve servicing when operations break down.
Target outcomes · Subject to deployment context
07b · Questions
Common questions from operations teams.
The honest answers to what airline operations and IT leaders ask us first.
No. Sora is read-first. Writes to PSS or DCS happen only after explicit operator approval, through your existing integration layer. No autonomous writes to core systems — ever.
08 · Trust
Enterprise-grade
operational trust.
Architected for the compliance, security and reliability expectations of airline operational control environments and enterprise travel infrastructure.
Enterprise security principles
Architected around least-privilege access, encrypted transport and segmented operational tenants.
GDPR-ready data architecture
PNR and passenger data handled under regional residency, retention and consent constraints.
Mission-critical uptime posture
Designed for the operational reliability profile of airline control environments.
Human-in-the-loop control
Every consequential action requires operator approval. No autonomous writes to core systems.
Full auditability
Every signal, recommendation and action recorded, attributable and recoverable.
Role-based operational permissions
Operator, supervisor and integration roles separated by environment and scope of effect.
SOC 2 readinessISO 27001 alignedNo autonomous writes to core systemsGDPR-ready data residency
09 · Principles
What we will never compromise.
- 01
A human approves every consequential action.
Sora does not execute. It proposes, sequences and prepares. The operator decides. This is not a limitation — it is the design. Airline operations are too consequential for autonomous action. We will never build a mode where Sora acts without approval.
- 02
We do not touch what we do not need to touch.
Sora reads broadly and writes narrowly. We observe across PSS, DCS and operational surfaces. We write only what the operator has approved, only through the integration paths the carrier controls. Non-destructive access is permanent policy, not a phase.
- 03
Every action is recoverable.
Every signal received, plan generated and action executed is logged, attributed and reversible. If something goes wrong — technically or operationally — the audit trail is complete. Accountability is not a feature. It is the operating model.
- 04
The airline's infrastructure is not ours to replace.
PSS vendors have spent decades building what airlines run on. We did not build Sora to compete with that investment. We built it to sit above it — extending what exists rather than displacing it. That philosophy guides every architecture decision we make.
“The first time we walked through the recovery sequence as a team, someone asked: why didn't we have this five years ago. That question is the whole brief.”
Head of Operations · European network carrier · Design partner
Identity withheld at partner's request · 2026
10 · Why now
The conditions for orchestration finally exist.
Three structural shifts that make an AI-native orchestration layer for airline recovery possible — and necessary — now.
Legacy infrastructure wasn't built for this
PSS and DCS were designed for schedule management, not real-time recovery orchestration. The coordination gap between systems creates the manual handoff problem that operators live every day.
Infrastructure · Gap
AI orchestration is finally production-ready
Large language model reliability, structured output and tool-use have crossed the threshold for mission-critical operational workflows. The conditions for a trustworthy orchestration layer now exist.
AI · Threshold
11 · About
Why Sora Labs
exists.
IROP recovery is one of the most demanding operational problems in travel. When disruption cascades, teams coordinate across PSS, DCS and control environments that were never designed to act as one.
Sora Labs is the AI-native orchestration layer for that moment — built by people who have been in the operations control room at 03:00 local time.
12 · Ground truth
Built by people who understand airline infrastructure.
Sora Labs is built around deep experience in travel infrastructure, enterprise integrations and operational recovery workflows across airline environments.
Christopher Magnani
Co-Founder · Strategy & Product
Two decades building and scaling enterprise digital products and mobile platforms across international markets.
Strategy, product & AI-native infrastructure
SuperStreams · The Mobile Life
Kenneth Andersson
Co-Founder · Infrastructure & Integrations
25+ years in enterprise technology and mobile platforms, with deep operational experience in airline and transportation systems.
Infrastructure, integrations & operational platforms
AirAsia Digital · Grab · The Mobile Life
We're hiring
Founding team · 2026
Building the operational layer for global airline disruption operations — and the people who run it.
- Open roles
- Founding engineers · Airline operations advisors · Integration partners.
- Where
- Stockholm · Remote (EU / SEA aligned).
Scene · 04Terminal · 04:38 LOC
A quieter layer running beneath the systems that already move the world.
GLOBAL · 24/713 · Long-term
The operating layer for
global airline operations.
Early Access · 2026Quiet conversations.
Quiet conversations.
Operational outcomes.
For airlines
Partnering with a small set of carriers shaping the first operational deployments.
For infrastructure partners
For Amadeus, Sabre, Navitaire and operational ecosystems exploring integration.
Ready to run a
quieter operation?
Early Access · 2026
Partnering with a small set of carriers in 2026. Infrastructure partners welcome for confidential briefings.
Stay close
Stay informed as we move toward deployment.