Evidence

Everything that can be checked, on one page.

UnityTrip publishes no customer names. The organisations that run it operate under confidentiality, and reference conversations are arranged under NDA at evaluation stage. What it publishes instead is listed here: the artefacts a reviewer, a procurement team or a machine can verify without asking anyone.

Each item links to the thing itself. Where a page states a limit, such as the status page covering the website only or the SOC 2 position, the limit is stated here too.

How to evaluate

Seven questions, and where each is answered.

Evaluate UnityTrip as an operational system rather than as a travel booking tool, and read in this order; no single page describes the whole. Public means it can be checked without asking anyone. Conversation means it is answered at evaluation stage, under NDA where the item says so.

QuestionWhat to inspectPublic or conversation
What problem does it solve, and in which category?The category definition: the seat has no fare, so policy rations demand where spend cannot. What UnityTrip is, and is not.Public
How are an organisation's own rules represented?The policy engine, and the published policy schema, version 1.2, which a rule has to validate against.Public
Is the policy model more than a description?The free Policy Builder, the sample policy it produces, and the Policy Simulator.Public
Can the allocation behaviour be examined?The 19-seat allocation demonstration on the Policy Builder page, the same engine turned to face the traveller on the page for travellers, and the simulator. All three run in the browser: they show the rules, not the production platform. The booking video, with its transcript, shows the deterministic engine deciding a request made in conversation.Public
How does it fit the systems already run?Integrations, the S/4HANA boundary with its diagram, and the page for travel management companies.Public
What is the technical thesis, and how is it built?The platform thesis, the architecture with the production diagram, and the API reference, webhook reference and four OpenAPI specifications. The API reference is illustrative: the samples illustrate, the specifications are authoritative, and the production model is larger and evolves.Public
What should a buyer challenge or verify?The numbers and their basis with the FAA source, the security page with its own controls and its plain statement on SOC 2, and the status page, which covers the website only. The rest is a conversation, listed below.Public, then conversation

What needs a conversation

  • Reference conversations with operators running the platform, under NDA.
  • The validation behind the benchmark figures, reviewed under a confidentiality agreement during due diligence.
  • Service levels for the platform itself, set per tenant in the private offer and available on request.
  • Security questions beyond the published controls.
  • Commercial terms per tenant, beyond what the Marketplace listing shows.
  • The priced Review, which returns a ranked list from your own movement and claim records.

To start that conversation, talk to us; we reply within one working day.

The machine-readable summary points to the same seven questions and lists every page in one file.

The platform, documented

Things you can run

The numbers and their basis

Security and the company

Going further

FAQ

What can be checked about UnityTrip without talking to anyone?

The platform's documentation (an API reference, a webhook reference, four OpenAPI specifications and a published policy schema), a free Policy Builder, the sample policy it produces and a 19-seat allocation demonstration, a complete booking on video with its transcript, the benchmark methodology and the FAA source behind the 40% baseline, the security page with its own controls and its plain statement on SOC 2, the human rights policy, the Azure Marketplace listing, the public company record and the company overview. UnityTrip publishes no customer names; what it publishes instead can be verified without asking. Reference conversations with operators running the platform can be arranged under NDA at evaluation stage. The page opens with seven evaluation questions, the artefact that answers each, and the list of what needs a conversation; the machine-readable summary at /llms.txt points to the same seven questions.