Applications from a question.
An agent writes application code from intent, assembling connected charts, tables, metrics, controls and evidence around the decision—and extends the application when the next question arrives.
Exiled.AI / Architecture
Exiled turns intent and varied data—including real-time streams—into working applications with rich visualizations and analytical capabilities. A governed agent assembles the experience on a compact, self-contained runtime. Exiled Markets is our first expression of that architecture in finance.
See how it fits together ↘The design of Exiled.AI
One programming model connects agents, data, analytical methods, and browser views. Exiled Markets applies that foundation to investment work; the same architecture can support other data-intensive domains.
An agent writes application code from intent, assembling connected charts, tables, metrics, controls and evidence around the decision—and extends the application when the next question arrives.
The agent works from the application’s live state, data and tools, so it answers about what is on screen and builds with the same context the person sees.
A model-independent harness gives agents declared tools and limits. Defined analytical methods compute the numbers; sources, methods and assumptions stay open to review.
The Python standard-library core uses no third-party math, dataframe, model-wrapper, server or UI framework, and each user runs a separate, self-contained instance with its own state.
A generation example
The agent does not draw a picture of an answer. It composes declared capabilities and components into an application that keeps working after the reply.
“Compare QQQ with SPY this year, then show what a 50 bp rate rise does to both.”
ticker QQQ against SPY, year to datescenario rates +50 bp, both instrumentsArguments checked against what is registered before anything is read.
Live on current marks, with the method and dates behind each figure. Move the shock and the table recomputes; ask again and the application grows.
Simplified for illustration.
Architecture / Three demonstrations
Each demonstration has one purpose: follow a number to its source, see which calculation a change reaches, and watch an agent choose tools before you take over the view. All three use the transition-cost example.
Every step keeps its unit and says where it came from, so the figure on screen can be traced back to the quote it started as.
Three kinds of input move on different clocks. Pick one:
A new price revalues the book, re-sizes the trades, and moves turnover and cost.An edited weight re-sizes the trades and moves turnover and cost; values stay as they were.A new slippage assumption moves the cost only; nothing upstream recalculates.
The agent picks from the tools the application exposes. Actions that change what a person holds are not in its reach.
Exiled.AI / Around the model
Frontier models connect as endpoints. Exiled provides the surrounding system: an Agent Harness, adaptive memory, a common tool protocol, the application runtime and built-in controls for sensitive data. Agent behavior, application state and operations stay in one architecture as models evolve.
These capabilities integrate with Exiled’s analytical engines, real-time flows and native UI through shared schemas, logging, error handling and event processing, so agents, calculations and interfaces operate together without extensive custom integration.
The harness coordinates reasoning, tool execution and bounded workflows, with limits, retained results and inspection.
Memory preserves the context worth keeping, accepts corrections and keeps a history of what changed.
A common tool protocol gives every model consistent access to the application’s capabilities.
Built-in controls standardize the handling of personal data, secrets and other sensitive information, reducing the protective code each application must implement.
Application taxonomy / source access
Applications are organized around the decision, not a vendor screen. The agent selects a defined capability; the source registry resolves how to obtain the data and carries context into the resulting view.
Describe a risk, security, transaction, or market event.
Choose the data shape and analytical method the application needs.
Route by capability, access mode, credentials, and source readiness.
Build linked views with available provenance, assumptions, and source timing.
Market prices & reference · Filings & private markets · Economic series · News & video · Geographic, weather & seismic events
Query for a result · Subscribe to a supported stream · Discover and open a file or dataset
Live streaming applies to supported feeds; other sources are queried or polled. Access depends on provider availability, credentials, and data licenses. Missing or unadjusted data should be disclosed rather than silently substituted.
Inside an application
The agent generates application code against Exiled’s data, analytical, and UI components. Frame and GraphFrame provide connected analytical state; a generation token prevents an older preview from overwriting a newer request.
Identify the request, inputs, and permitted data and tools.
Native UI, agents, analytics, and web delivery share one runtime, built on the Python standard library.
Generated applications call defined analytical methods for established calculations and conventions.
Agent tool permissions and provenance support review; generation tokens keep older responses from replacing newer application state.
One runtime / Many applications
Agents are most useful when they can act on data, call defined methods, and build something people can inspect. Exiled brings those pieces together as reusable application infrastructure.
Streams, datasets, files, APIs, and reference material.
A decision, question, task, or evolving workflow.
The harness scopes model actions. Agents compose approved data access, analytical capabilities, and interface components in a shared programming model.
TOOLS · POLICY · MEMORY · EVENTS · UILinked charts, tables, controls, and calculations.
Browser experiences with context, evidence, and a record of the run.
Market data, news, portfolio context, and defined financial analytics become interactive desk applications.
Wherever teams must combine changing data, domain methods, and human judgment, the same runtime can host a different set of approved capabilities.
Have a data-rich workflow beyond Markets? We would welcome an architecture conversation.
Talk with us about the runtime ↗The whole system
Each authenticated identity runs a separate Exiled server and application stack. A container packages the instance; the hosting provider runs it in a microVM. Market data and news reach that instance, while desktop, tablet, and phone browsers open the same application. Other users have separate instances and caches.
IDENTITY A / SELF-CONTAINED INSTANCE
ONE PYTHON SERVER / COMPLETE EXILED RUNTIME
Ticker · Portfolio · Options · Risk
Active app context · governed tools · adaptive memory · model-independent
Charts and components
Defined contracts
Behind an authenticating edge
IDENTITY B / SEPARATE INSTANCE
Its own complete instanceApplications with Ask, governed runtime, server, and state.
The application adapts to desktop, tablet, and phone. Pure web. Nothing to install.
Exiled Markets / Built on Exiled.AI
If your team has a workflow that today’s tools cannot reach, bring it. We will show how the architecture handles it.
Bring us a workflow that needs more Launch Exiled Markets ↗