Governed support records
Individual roles and MFA controls, independent publication of customer policies, protected recordings, and previewed retention with legal holds.
Inspect Customer Care ↗Trust & deployment
Know where the data goes. Know who decides.
Review the hosting approach, inspect the controls of your chosen product, and establish the operating commitments for your environment.
Deployment and responsibility
Our platform. Your defined operating scope.
FlightAtom uses its own private application platform, WingLayer. Establish the deployment details and responsibilities for the product you are evaluating.
| Buyer question | Public information | Define for your deployment |
|---|---|---|
| Hosting | FlightAtom operates its own private platform for application deployment, named WingLayer. | Product environment, hosting region, data residency, and isolation arrangements. |
| Access | Product roles and review controls are described below. | Identity provider, user roles, administrator access, and access-review responsibilities. |
| AI data handling | AI use varies by workflow. MENTHOR recommendations use rules and keywords; PINAX analytics are deterministic; EPHOR manages oversight and approvals. | Model providers, data sent to each service, provider retention and training terms, and permitted use. |
| Backups and recovery | Recovery arrangements belong to the selected deployment. | Backup frequency and retention, restore-test evidence, recovery time and recovery point objectives. |
| Export and deletion | Records and exports differ by product; the product tour identifies the record being managed. | Export formats, retention schedule, deletion process, and treatment of backups. |
| Support and maintenance | Scope the operating responsibilities alongside the product implementation. | Support channels and hours, incident escalation, maintenance windows, and response commitments. |
Inside the products
Controls you can inspect.
Start with the application controls relevant to your records and decisions, then confirm their configuration in the evaluation environment.
Access and approval authority
Tenant and role controls, multi-factor authentication, identity federation, and user provisioning. Corrective-action completion and independent verification retain separate evidence and decisions.
Inspect Aurora ↗Investigation integrity
Application-layer encryption protects restricted safety records. Role checks, short-lived sessions, and cryptographically chained audit records support access control and traceability.
Inspect Trace AI ↗Document release control
Author separation and independent-review checks govern approval. Signed workflow versions and immutable release manifests preserve release evidence; assignments and acknowledgments connect it to readers.
Inspect FOLIO ↗Source access
Document and collection permissions constrain retrieval; citations expose the passages behind an answer.
Inspect DELPHI ↗Revision-specific decisions
Organizational roles and approval snapshots preserve the package revision behind a reviewer decision.
Inspect EPHOR ↗Trust & deployment
Follow the data through the AI workflow.
An application platform and an AI service are separate parts of a deployment. Identify each provider and the information it processes.
Document and investigation context
DELPHI retrieves permitted source material. Trace sends bounded investigation context to its configured DELPHI service and retains the resulting evidence in Trace.
Explore the workflow ↗Voice and document processing
Trace voice interviews use configured telephony and realtime services. FLIGHT AI uses vision extraction for document review. Map these data flows in the evaluation.
Explore the workflow ↗Explicit rules and decisions
MENTHOR event-to-course recommendations use rules and keywords. PINAX computes operational measures. EPHOR preserves authorized oversight decisions.
Explore the workflow ↗Trust & deployment
A practical route to technical review.
Begin with the product and representative records. Establish the documentation and acceptance evidence needed for the deployment.
Inspect access in context
Demonstrate the permitted user, restricted user, and approving role against the same workflow.
Trace a record
Follow its source, changes, review, export, and proposed retention or deletion treatment.
Agree the evidence before rollout
Use a written evaluation plan to record controls, exceptions, ownership, and acceptance decisions.
Explore the workflow ↗Questions & answers
Before you book a demo.
What is WingLayer?
WingLayer is FlightAtom's own private platform for application deployment. The selected product and implementation scope determine the environment and operational arrangements.
Does private hosting mean AI data stays within WingLayer?
No. Some workflows use configured external model, telephony, or processing services. Identify the providers, data flows, retention terms, and permitted use for the product before deployment.
Are hosting regions and support commitments the same for every product?
Hosting region, access, backups, recovery, retention, and support commitments are established for the selected deployment and documented in its agreed scope.
See FlightAtom in action
Request a demo Start with your workflow.
A focused walkthrough, with the people and decisions that matter to your team.