Agents in Orbit: Workflows, Not Autopilot — Eduardo Simon & Javier Casal, Flywire
Flywire introduced Orbit, an internal platform designed to integrate LLM steps into deterministic engineering workflows, ensuring control and reliability in a highly regulated payment processing environment. Orbit defines agents using YAML/JML files that undergo standard merge request reviews, allowing AI to supply judgment while keeping predictable logic in code. The architecture separates orchestration, execution, and session state, and enforces strict guardrails (timeouts, rate limits, network access) to ensure safety and compliance (PCI, DSS). This approach allows for scaling automation—such as code review and dependency fixing—while keeping human review in the loop.
Key takeaways
-
Workflows, Not Autopilot
5:00
Orbit pairs deterministic code with small LLM steps, calling the model only when reasoning is necessary. This ensures that predictable procedural logic remains in code, maintaining reliability and control.
-
Compliance and Infrastructure Control
7:20
By building the platform in-house and keeping execution within the existing Victoria infrastructure, Flywire ensures that sensitive data (PCI, PII, PHI) never leaves their controlled environment, bypassing lengthy vendor security reviews.
-
Structured Evaluation and Improvement
The platform uses isolated component evaluation by injecting historical state and context into specific workflow nodes, rather than evaluating entire end-to-end workflows. Golden datasets are versioned in the repository for on-demand testing.
-
Adoption Strategy: Skill to Workflow
18:20
The recommended adoption path is to start with a 'Skill' (which is cheap and easy to iterate on), prove its value, and then formalize it into a deterministic 'Workflow' (JML file).