Talk to the people who built it.
AuroraCrew is built and run by the same small team that operates it, so a message here is not routed through a call centre. Tell us which of these you are and it lands with the right person on the first try.
Evaluating the platform
Roster building, operational control, crew self-service, and how it would fit your fleet, bases and duty rules. The platform overview covers the seven operational roles and the compliance model.
See it running on your operation
We load a month of your own routes, fleet and crew into a private workspace and walk through building it, delaying a flight, and watching the roster react. Roughly an hour.
Support for a live operator
Crew and schedulers: your airline's crew scheduling team is the first line, and they reach us directly from inside the platform. Anything affecting the platform itself comes here.
Where the data lives
What is stored, for how long, who can see it and where it runs is documented in the privacy notice. Deeper security questions — architecture, access control, audit trails — are welcome here.
Send a message
Everything except the company name is required. We usually reply within one business day.
We use what you send here only to answer you. It is never sold or added to a mailing list. See the privacy notice and terms.
What happens after you send it
It arrives as an alert, not an email
Your message is delivered inside AuroraCrew itself and pushed to the operations team's devices the moment it is sent. There is no shared inbox for it to sit unread in.
A person reads it
Not a bot, not an auto-responder, and not a sequence of nurture emails. If your question is technical it goes to whoever wrote that part of the platform.
We reply to your address
Usually within one business day. If you asked for a walkthrough we will propose a couple of times and ask what routes and fleet you would like loaded in.