Palladium is our compliance and safety management system for AOC holders — safety, compliance, documents and training in one place, on a dedicated instance per AOC. The software carries no licence fee, and it was built from real operational experience rather than requirements gathered secondhand.
We build for problems we've lived through ourselves, not requirements gathered secondhand.
Where data sensitivity matters, we deploy a dedicated instance rather than pooling clients on shared infrastructure.
Our software reads from the tools you already use rather than asking you to start over.
Ongoing correctness and maintenance is treated as part of the product, not an afterthought.
An occurrence closed without a recorded investigation is a finding waiting to be written. Report, investigate and close, with the trail attached.
Corrective actions that close without verification are the findings auditors reopen. Track each one against the procedure it concerns, through to evidence of closure.
A crew member flying on a superseded manual is a compliance failure you cannot see coming. Controlled versions, distributed by role, with read confirmation recorded.
A currency that expires unnoticed grounds an aircraft or, worse, does not. Currency and competency tracked by crew member and role, with alerts before expiry.
Your safety occurrences, compliance findings and crew records do not sit in a database with another operator's. Every AOC runs on its own instance — not a shared database with row-level permissions. Given what this data is, we did not think that was a reasonable thing to ask you to accept.
Palladium reads from the scheduling and flight-data sources you already use rather than asking you to re-enter data. Every source maps into the same underlying flight-data model, so reporting and compliance logic behave the same way regardless of where the data came from. At launch: Leon. Additional sources are being added on request.
Both are in build and neither ships silently. If either one sits on your critical path, tell us your timeline and we will sequence against it.
Starting with Smart OFP, connecting flight planning data directly into the canonical record.
EU ETS, UK ETS, Swiss ETS, CORSIA, ReFuelEU, and per-flight luxury tax calculations.
Screens from a working instance, populated with a fictional operator so nothing real is on show. This is the system as it is today, not a mock-up of where it is going.
Documents awaiting read, occurrences awaiting triage, findings still open, credentials expiring. The Accountable Manager can see the state of the management system without asking anyone to prepare a report.
Reported, triage, investigation, risk assessment, closed. Each entry carries its type, the department it belongs to and its risk score, and the whole register exports to CSV when your inspector wants it.
Internal, external and regulatory audits tracked in one register, each with its findings attached. Audits and findings export separately, so the evidence pack for an inspection is a download rather than a fortnight of assembly.
Users carry their operational role — Safety Manager, Compliance Manager, Training Manager, Captain, Cabin Crew — and the system's permissions follow from it. Behind the settings sit single sign-on, virus scanning on uploads, a configurable risk matrix, scheduled backups and an audit log of who changed what.
There is no per-user charge, no per-aircraft charge, no annual licence and no upgrade tier holding back the part you need. Two costs, both stated here.
Because a compliance system is only worth something once it is genuinely being used, and a licence fee is the main thing standing between a small operator and using one. We would rather Palladium ran inside a lot of operations than earned a margin inside a few.
The honest catch: we are a small team, so we onboard at the pace we can actually support. If we are at capacity we will say so rather than take your setup fee and leave you waiting.
Four containers on Docker Compose. If you would rather not think about any of this, we host it — but you are never locked into that, and these are the numbers so your IT people can judge for themselves.
Root or sudo access on the host is required for the setup — installing Docker, creating the storage volumes and bringing the stack up. If you would prefer we did not hold it, provision the host yourself, run the install with us on a call, and keep the credentials.
After that, host-level access is needed only for updates, restores and moving the instance. Everything else — users, roles, workflows, backups, signature updates — is done from inside the application by your own administrator.
The database itself stays modest. What grows is uploaded content — controlled document versions, occurrence attachments, training evidence — and the backup archives, which are the largest consumer at scale. Size the disk for those, not for the row count.
Microsoft Entra ID for single sign-on, and Microsoft 365 for outbound email. Both are optional; neither is required for the system to run.
Written for the person in the room who has to be convinced, not for search engines.
Spreadsheets are not the problem — producing evidence from them is. The finding auditors write most often is not that a corrective action was missed, it is that the record of the investigation, the verification and the closure cannot be assembled in the order and the timeframe they asked for.
If your team can pull three random occurrences end to end in ten minutes, you may genuinely not need this. Our audit-readiness checklist is a fair way to find out before spending anything.
No. Every AOC runs on its own instance — a separate deployment, not a shared database with row-level permissions. Another operator's breach or misconfigured query cannot reach your occurrence data because your records were never in the same place.
The full detail is on the data and security page.
For a single AOC, expect two to four weeks from go-ahead to running live, depending mostly on how much historical data you want brought across and how quickly your manuals can be loaded.
We do the setup. What we need from you is time from the people who own the procedures — realistically a few hours across those weeks, not a project team.
Open items — live occurrences, findings still in corrective action, current manual versions, active currency records — are migrated so nothing in flight is dropped.
Closed historical records can be imported for the retention period you are working to, so the audit trail does not begin on the day you switched systems. That import is part of onboarding, not a chargeable extra.
Yes. Access can be granted as read-only and scoped to a period, so an inspector or external auditor sees the evidence without being able to alter it, and without anyone emailing PDFs around.
Every access is recorded in the audit log alongside everything else.
A fair question to ask a company releasing its first product — and a fairer one to ask a company giving it away. You should ask it of every vendor holding your compliance records.
The software carries no licence fee; the business is not a charity. Revenue comes from setup, from hosting the instances of operators who would rather we did, and from the advisory practice alongside it. There is no funding round behind this that needs repaying at your expense, which is precisely why the software does not need a licence fee attached to it.
More importantly, you are not dependent on the answer. Your data is exportable in full, encrypted, at any time and at no cost — you never need our permission or our continued existence to hold your own records. If we ceased trading, instances stay available for a wind-down period long enough to migrate, and we would hand you the export rather than switch anything off.
Not to run it — Palladium is hosted, so there is nothing for you to install or maintain.
They will want to look at the security page, and if you run identity centrally they will be involved in connecting single sign-on. That is usually the extent of it.
Each AOC gets its own instance, for the same isolation reason. There is no licence fee whatever the number, so what scales is the setup and the hosting — and for a group deploying several at once, the setup is quoted for the group rather than charged per instance.
The software has no licence fee, no per-user charge and no per-aircraft charge — permanently, not as an introductory rate.
You pay a one-off setup fee of no more than €500, and you pay for hosting — either to your own provider if you self-host, or to us if you would rather not. Full breakdown, and the server requirements if you want to run it yourself.
Because the alternative you are running today is a spreadsheet with no audit log, no access control, no backup schedule and no version history — and it is also version one, maintained by whoever last touched it.
That said, the honest answer to a new product is evidence, not argument: look at the actual screens, put it against a real audit, and form your own view. It costs you nothing but the time.
If your organization needs software built by people who understand your operation — inside or outside aviation — talk to us about what you're trying to solve.
Bring your current compliance headache — we'll show you how it maps onto Palladium, plainly.
We read every enquiry personally and reply within one business day. If we are not a fit, we will tell you.