By SOS Services · 4 regulatory authorities

For the hangar floor, not the audit binder.

FAA, EASA, CAAC, SACAA workflows first-class — not bolted on. Built for carriers who can't afford a seven-figure SAP rollout, or a missed inspection.

Join AMRO Pro pilot See the platform →

FAA · EASA · CAAC · SACAA · Multi-tenant · Audit-ready

AMRO Pro — multi-regulator work order workspace

Regulator-readable from day one

4: Regulatory authorities; FAA · EASA · CAAC · SACAA
100%: Audit trail per WO; every state change is sourced + logged
0: Operator data lock-in; export your records any time
In pilot Target: Design partner program; targeting Q3 2026 launch

FAA · EASA · CAAC · SACAA — first-class Built on Logic Nexus · multi-tenant Audit trail per work order Pilot Q3 2026 · with regional operators

Target = honest pre-launch design goal, not a present-day claim.

What's inside AMRO Pro

Eight modules that connect a maintenance manual to a regulator-ready record.

MPD Tracking

planning

Maintenance Planning Document as a first-class data model, not a PDF

• Tasks, intervals, applicability rules stored as structured data
• Revision diff between MPD versions in one screen
• Applicability filters by aircraft type, serial, fleet, registration

Work Orders

execution

Task-level sign-off — every step traceable to a named technician

• Task-level sign-off with named technician and license-category check
• Auto-linked to the MPD task and revision that authorized the work
• Findings + corrective actions captured as structured data

Parts Traceability

inventory

Chain-of-custody from PO to installation, airworthiness intact

• Serial-numbered rotables treated as first-class entities, not Excel rows
• 8130-3 / EASA Form 1 / CAAC AAC-038 attached to receipt records
• Movement history (PO → bond → shelf → install → removal) preserved forever

Multi-Regulator Workflows

compliance

FAA, EASA, CAAC, SACAA — first-class, not bolted on

• Authority-aware sign-off chains — B1, B2, C category mapping per authority
• Authority-specific form templates (8130-3, EASA Form 1, CAAC AAC-038, etc.)
• Per-authority deadline rules baked in (AD compliance windows, reporting cadence)

Airworthiness Directives

compliance

AD compliance without a spreadsheet of doom

• AD library ingested from FAA / EASA / CAAC / SACAA bulletins
• Per-aircraft applicability evaluated against fleet master data
• Compliance status tracked through linked work orders

Task Templates

execution

Reusable check sequences, version-controlled per fleet

• Build templates from MPD tasks or custom checklists
• Per-fleet, per-aircraft-type, per-operator template scoping
• Version every template — applied checks reference the template version they used

Fleet Master Data

platform

One source of truth for aircraft, fleet hierarchy, locations, technicians

• Aircraft master with registration, MSN, fleet, base, regulator
• Fleet groupings for MPD scoping and reporting roll-ups
• Location hierarchy (line / hangar / base) for movement tracking

Audit & Evidence Exports

compliance

Hand the inspector a folder, not a war story

• Pre-built export bundles per authority (FAA, EASA, CAAC, SACAA)
• Bundle scoped by aircraft, date range, AD set, or arbitrary query
• Each export includes a chain-of-custody document for every artifact

Built for four regulators from day one: FAA, EASA, CAAC, SACAA. Not "FAA with a translation layer." Authority-aware forms, deadlines, sign-off chains.
Provenance, not paperwork: Every task signed off has a digital chain — who, when, against which MPD revision, against which AD. Inspectors get evidence, not stapled binders.
Multi-tenant, multi-MRO: Independent MROs serving multiple operators share a platform without sharing data. Each operator's records are their own.
Parts traceability that holds up: Chain-of-custody from purchase order to installation, with airworthiness tags preserved. No more spreadsheets-of-truth that crumble during an audit.
Modern engineering: Express microservice, React frontend, Postgres with RLS. The same stack powering modern SaaS — applied to a field that's been stuck on Oracle Forms.
No license-by-airframe pricing: Per-tenant SaaS pricing. Add an aircraft, the math doesn't break. Add a regulator, the platform doesn't need a re-implementation.

Pricing

Per-aircraft, transparent.

Indicative pilot pricing. Final tiers publish at GA — design-partner operators lock in this rate for 24 months.

Operator

₹29,000 / month / aircraft

For regional carriers running their own maintenance.

✓Work orders + MPD + parts traceability
✓Single regulator (FAA / EASA / CAAC / SACAA)
✓Audit-trail bundles per work order
✓Up to 50 mechanic seats / aircraft

Start pilot

How we build AMRO Pro

All engineering posts ↗

MRO

When an MRO outgrows spreadsheets

The specific failure modes that arrive when work orders, parts, and airworthiness records all live in Excel. Why the next step usually isn't SAP.

Read on sosservices.online →

Engineering

Multi-tenant RLS at studio scale

How AMRO Pro isolates MRO operators sharing a platform. The 905-migration drift incident. The zombie connections that blocked an ALTER TABLE.

Read on sosservices.online →

Sibling product

Aviation AI Pro — flight data analytics

ARINC 717 parsing, multi-vendor DLU decoding, approach scoring, DGCA-ready exports. AMRO's safety-data cousin in the studio.

Visit aviation.sosservices.online →

Sibling product

Sthira — retail investing, built calm

Goal-based SIPs and pre-authorized rebalancing for layman investors. The LLM explains. It never trades.

Visit sthira.sosservices.online →

For the hangar floor, not the audit binder.

What's inside AMRO Pro

MPD Tracking

Work Orders

Parts Traceability

Multi-Regulator Workflows

Airworthiness Directives

Task Templates

Fleet Master Data

Audit & Evidence Exports

Why AMRO Pro instead of a 1990s MRO suite

Per-aircraft, transparent.

How we build AMRO Pro

When an MRO outgrows spreadsheets

Multi-tenant RLS at studio scale

Aviation AI Pro — flight data analytics

Sthira — retail investing, built calm