Skip to main content

Product tour · Agentic AI runtime

Follow one agent's run through elan1 Run.

elan1's own runtime, on one signed image, in the cloud, your data centre or an appliance. It refuses before it acts. It proves what happened.

5 steps · about 3 minutes · illustrative data

An infrastructure engineer checks a server rack with a tablet in hand in a bright data hall

The tour

elan1 Run, step by step.

Step through at your own pace. Nothing moves on its own.

01 / 05 · Choose where

Choose where: cloud, your data centre, or an Edge, Department or Rack appliance.

  • AWS Mumbai by default, with no US region
  • For sites that must stay inside your walls
run.elan1.ai/fleet

1 signed image · fleet

  • Edge · Salem plant

    Healthy
  • Department · Finance, Chennai

    Healthy
  • Rack · DC-1

    Healthy
  • Cloud · ap-south-1 Mumbai

    3 zones
Fleet screen for one signed image: an Edge appliance at the Salem plant, a Department appliance for Finance in Chennai and a Rack in DC-1, all healthy, plus the cloud in ap-south-1 Mumbai across 3 zones. Illustrative data. Illustrative data.

Text alternative

The tour as text.

Every step and every screen, written out for screen readers, print and anyone who prefers to read.

  1. 01 Choose where: cloud, your data centre, or an Edge, Department or Rack appliance.

    On screen: Fleet screen for one signed image: an Edge appliance at the Salem plant, a Department appliance for Finance in Chennai and a Rack in DC-1, all healthy, plus the cloud in ap-south-1 Mumbai across 3 zones. Illustrative data.

    • AWS Mumbai by default, with no US region
    • For sites that must stay inside your walls
  2. 02 Install one signed image.

    On screen: Appliances screen: the Edge appliance at the Salem plant, the Department appliance for Finance in Chennai and the Rack in DC-1 each run the same signed image, verified, and are managed as one fleet. Illustrative data.

    • One signed image on each
    • Managed as one fleet
  3. 03 Contracts: Agents run on nine contracts.

    On screen: Contracts screen listing the nine contracts on one signed image: run.route, run.serve, run.flow, run.tools, run.sandbox, run.index, run.trace, run.identity and run.fleet. Illustrative data.

    • Nine contracts underneath every agent
    • Models from Anthropic, OpenAI, Google and open source, behind run.serve
  4. 04 Govern decides each action. Run refuses before it acts.

    On screen: Tool calls from the AP agent at Kolam Components: a payment sent to elan1 Govern and held for the finance head, and a bank detail change refused under rule 4.2 before it runs. Illustrative data.

    • Run carries, routes and records every call
    • It never decides which actions happen
  5. 05 Proof: Every run is traced and proven.

    On screen: Trace screen for the AP agent at Kolam Components: a traced model call, a payment held for the finance head by elan1 Govern, and a bank detail change refused under rule 4.2, each with the agent's identity. Illustrative data.

    • Every call traced
    • Identity on every agent
    • Records that leave with you

What you just saw

Run carries. Govern decides.

Run carries, routes and records every call. It never decides which actions happen. That is elan1 Govern's job.

Start with one process.

Name the place. We'll show you the run.

  • Allowed · Approved by Asha R.
  • Held for CFO
  • Refused · rule 4.2
Illustrative data.

Questions

The Run tour, answered.

Yes. These are elan1 Run's own screens, rebuilt for the web, with illustrative data: Kolam Components and the people named are fictional. The tour is ungated and takes about 3 minutes, and its last screen offers Book a demo with elan1 Run pre-filled, so you can see the same screens on one process of your own.

No. The elan1 Run tour is ungated: no form, no sign-up and no email address. It takes about 3 minutes, and nothing you click changes a real system, because the data is illustrative. When you reach the last screen, Book a demo opens with elan1 Run pre-filled, if you want to see it on your own process.

AWS Mumbai by default, with no US region. It can also run in your data centre or on an appliance.

Models from Anthropic, OpenAI, Google and open source, behind run.serve.

Below about 1 billion tokens a month, usually yes, and we will tell you so.

They sit underneath every agent on one signed image: run.route, run.serve, run.flow, run.tools, run.sandbox, run.index, run.trace, run.identity and run.fleet. Models from Anthropic, OpenAI, Google and open source run behind run.serve. elan1 Run carries, routes and records every call; it never decides which actions happen, which is elan1 Govern's job.

You choose where it runs: the cloud, on AWS Mumbai by default with no US region, your own data centre, or an Edge, Department or Rack appliance for sites that must stay inside your walls. Each place gets one signed image, and every installation is managed as one fleet, with every call traced and an identity on every agent.

Add the next when it holds.

Approvals · Kolam ComponentsIllustrative
  • Allowed · Approved by Asha R.
  • Held for CFO
  • Refused · rule 4.2
RCPT-0042 · signed · chained
A product view with three decisions: allowed and approved by Asha R., held for the CFO, and refused under rule 4.2. Illustrative data.