FAQ
Common questions.
Product
Krila is the agent-native operating layer for airline commercial decisions. We start with network planning, the most expensive recurring decision an airline makes, and consolidate the workflows that today sit fragmented across Sabre AirVision, Amadeus SkySYM, BI tools, OAG, MIDT, Cirium, and Excel.
Mid-market, neo-carrier, and ULCC network planning, scheduling, and commercial teams. Specifically operators who are underserved by legacy enterprise tools and priced out of full Palantir Foundry deployments. Typical user titles: Network Planning Analyst, Senior Network Planner, Director of Network Planning, VP Commercial Strategy.
A working analyst hands Krila a question like “Should we open MIA–SDQ daily?”, “Which competitor moves should I brief leadership on this week?”, or “What happens to RASM if we re-time the morning BOS bank by 20 minutes?” and gets a grounded, auditable answer that pulls from schedule, demand, fare, and competitive data. The agents handle the analytical legwork: spill and recapture modeling, QSI comparisons, schedule simulation, competitive monitoring. Planners stay in the loop on every decision.
Those products are decades-old planning suites built for the largest carriers and priced accordingly. Krila is agent-native rather than wizard-driven, runs in a browser without a multi-month implementation, and is built for the workflows of carriers that don’t have 80-person planning departments. We are PSS- and GDS-agnostic by design.
Data and Integration
Today: DOT T-100, DOT DB1B, OAG, Cirium, OpenSky, FlightAware, PredictHQ, and direct schedule and fare feeds from carrier-owned systems. We do not require a specific PSS or GDS. Bring what you have.
No. Design partners can run the platform on public data (T-100, DB1B) and their own internal feeds. If you already license Cirium or OAG, we plug into your existing entitlements rather than reselling data.
Yes. Most design partner deployments connect Krila to the carrier’s schedule of record, fare engine outputs, and finance system extracts. Data stays in your tenant.
AI and Trust
The agent does not invent route data, fares, or capacity figures. Every quantitative output is grounded in a queryable source (DOT, OAG, your schedule of record), and the agent shows its work. Where an answer requires judgment under uncertainty (forecasts, competitive intent), the agent says so and exposes the assumptions.
Decision support. Krila is built to compress hours of analytical work into minutes and to surface options a planner might have missed. The planner approves the decision.
Pricing and Partnerships
We are working with a small group of design partners through 2026. If you are at a Tier 1 mid-market carrier (neo-carrier, ULCC, or hybrid LCC) and want to evaluate Krila on your own network, contact vish@krila.ai.
A short paid pilot (typically one quarter) against a defined workflow, run on your data, with weekly sessions and direct access to the founding team. Pilots convert to annual contracts on outcomes you define going in.
Pricing is set per deployment based on scope and seat count. We are deliberately positioned below the enterprise planning suites and well below a Foundry deployment.
Company
Krila is led by Vish, previously at Surge AI. The company is headquartered in Arizona.
Krila is currently raising a pre-seed round.
No. Krila is airline network planning software. We are not affiliated with any consumer electronics or audio products.