Alastor. Interactive API for border authorities.
Every passenger vetted at check-in. Every flight watched until it lands.
The demo is password protected and holds synthetic data only. No password? Ask your Alef10 contact, or write to contact@alef10.ai.
200 msor less per message
One check-in, one answer
Alastor sits between the airlines and the State. It answers each check-in on the State’s own rules in well under a second, puts every flight and flagged passenger in front of the officers who act on them, and keeps the history investigators need, with the controls the law asks for.
- IATA / WCO PAXLST, CUSRES and PNRGOV
- 200 ms or less per message
- Runs on your own network
- 01AirlinePassenger and document data, sent at check-in
PAXLST - 02AlastorThe State’s own system, or Alastor’s decision engine
State rules - 03AirlineThe answer, per passenger, before boarding
CUSRES
- Board
- Do not board
- Selectee
Three jobs, three speeds.
The same passengers, seen by the system in seconds, by officers in hours and by analysts over months. Each person sees only what their role and the law allow, and every look is in the audit.
Secondsbefore boarding
Clearance
Each check-in is answered board, do not board or selectee, on the State’s rules. This is the interactive API answer the airline waits for.
- The State’s own system, or Alastor’s decision engine and workflow designer
- Changes approved with four eyes, live without a restart
- Data errors answered per passenger, never guessed
Hoursbefore arrival
Screening
Officers see the day’s flights and act on the people who matter, before the flight lands.
- Flight board: booked, checked in, awaiting an officer, cleared, boarded
- Passenger list beside the seat map; who travels with whom
- One work list: decisions by deadline, alerts, overrides sent to the airline
Weeksover history
Intelligence
Investigators find the patterns no single flight shows, across travel history and PNR.
- Travel history and companions, searched with a reason
- Travel patterns that raise insights, approved with four eyes
- PNR for the passenger information unit: masked on time, unmasked only as the law says
The controls the law asks for.
Passenger data is sensitive, and the people who use it answer for it. Each person sees only what their role and the law allow, and every look is in the audit.
Access by role
Officers, analysts and administrators each see what their role and the law allow, and nothing more.
Four-eyes approvals
Rule changes and new travel patterns are approved by a second person, then go live without a restart.
PNR masking
PNR for the passenger information unit is masked on time and unmasked only as the law says.
Tamper-evident audit
Searches carry a reason, and every look lands in one tamper-evident audit trail.
Yours, on your network.
Alastor is installed by the State, in the State’s data centre. Nothing calls home.
- Client-hosted, closed network
- No cloud service, no telemetry. Several sites, active and passive.
- Your data, always exportable
- Every record exports complete, as documented JSON lines.
- Encrypted and audited
- Passenger data sealed under your key (a file or an HSM); one tamper-evident audit trail.
- Never stops a passenger over a licence
- The licence sets modules and capacity; check-in keeps flowing.
Speaks the messages airlines already send.
Alastor follows the IATA / WCO passenger data standards and connects over the transports airlines already use.
| Messages | Transports |
|---|---|
PAXLST | Advance passenger information (API) from the airline. Editions 2010 to 2016. |
CUSRES | The answer back to the airline: board, do not board or selectee. |
PNRGOV | Passenger name record (PNR) data for the passenger information unit. |
Transports
Messages arrive on the transport the airline already works with.
HTTPSIBM MQKafkaRabbitMQ
What to try in the demo.
A day of flights at Tel Aviv, made up: no real passenger, booking or document anywhere. You are signed in with every role, so every screen is open.
- 01
The flight board
Today’s flights, a column per stage. Open a flight with a do-not-board.
- 02
A flight
Hover a passenger: their seat lights up. Click one to act, or ask for their PNR.
- 03
The work list
Decide a flagged passenger before the deadline: confirm or override.
- 04
A traveller
Search SPECIMEN: trips, companions and bookings, with a reason.
- 05
The rules
The State’s clearance workflow as a flowchart. Change it and test it.
Questions border teams ask.
What is an interactive API (iAPI)?
With an interactive API, the airline sends each passenger’s data to the State at check-in and waits for an answer before boarding: board, do not board or selectee. Alastor is the State’s side of that exchange.
Which standards does Alastor support?
IATA / WCO PAXLST (editions 2010 to 2016), CUSRES and PNRGOV, over HTTPS, IBM MQ, Kafka or RabbitMQ.
How fast is the answer?
200 ms or less per message, so check-in keeps moving.
Where does Alastor run?
On the State’s own closed network, in its own data centre, across several sites if needed (active and passive). There is no cloud service and no telemetry. Passenger data is encrypted under the State’s key, in a file or an HSM.
How does Alastor support a passenger information unit (PIU)?
Investigators search travel history and companions with a stated reason, and work with PNR that is masked on time and unmasked only as the law says. Travel patterns that raise insights are approved with four eyes.
Can a licence problem stop check-in?
No. The licence sets modules and capacity; check-in keeps flowing.
Can we export our data?
Yes. Every record exports complete, as documented JSON lines.
How can we see Alastor?
There is a live demo with synthetic data only, at alastor.alef10.ai. It is password protected: book a meeting on Calendly or write to contact@alef10.ai to ask for access.
See Alastor on a day of made-up flights.
Walk through the flight board, a passenger list with its seat map, the work list and the rules, with every role open. Then tell us about your border, and we will talk through a first step.
- Synthetic data only: no real passenger, booking or document
- Installed on your network, sealed under your key
- Your rules, approved with four eyes