# Introducing Runtime 1.5

> The moment between pressing Run and seeing something happen is now a second or two. Runtime 1.5 is the fastest and most capable engine Edgaze has ever had.

By Arjun Kuttikkat, Founder · Published October 26, 2026 · Engineering

Source: https://www.edgaze.ai/blogs/introducing-runtime-1-5

---

Every workflow on Edgaze begins the same way. You press Run.

And then, for a moment, nothing happens.

Before Runtime 1.5, that moment lasted close to eight seconds. On a paid run it could stretch to twelve, sometimes seventeen. Long enough to wonder whether you had actually pressed the button. (You had.)

Eight seconds doesn't sound like much. But it is the first thing every person feels, on every run, every single time. It is the difference between a product that feels alive and one that seems to be thinking it over.

So when we started on Runtime 1.5, we gave ourselves one goal: by the time you let go of the button, your run should already be running.

Today, we are introducing Runtime 1.5.

## The fastest Edgaze has ever been

Runtime 1.5 starts your run in a second or two, finishes it more than twice as fast, and puts your result on screen five times sooner. When Edgaze is busy, your run no longer fails. It waits its turn and starts on its own.

| What you notice                                  | Before   | Runtime 1.5 | Faster by |
| ------------------------------------------------ | -------- | ----------- | --------- |
| A six-step test workflow, start to finish        | 6.4s     | 2.8s        | 2.3×      |
| Waiting for results after a paid run's last step | 6.4–7.4s | 1.26s       | About 5×  |
| Wrapping up a paid run                           | 7.36s    | 0.30s       | 25×       |

_The test workflow makes no model calls, so it measures the runtime alone. On Runtime 1.4 its clock started once the run had begun, which leaves out the start-up wait above, so the real gap is larger. The paid-run wait is the time a finished run still showed "running". Wrapping up is settling the charge and paying the creator._

## The first second

Press Run on Runtime 1.5 and your first step starts a second or two later. Paid runs included.

To get there, we rebuilt everything between your click and your first step. The parts of Edgaze that start a run now work side by side. Every piece of start-up work happens exactly once. And anything that isn't your run, like analytics and notifications, waits until your run is already moving.

None of it came from cutting corners. Every run is still verified, every payment is still protected, and every credential is still sealed before it is used. Those checks simply don't keep you waiting anymore.

## The whole run

Speed at the start is only worth something if it carries through to the end. It does.

**The same six-step test workflow, start to finish, in seconds**

| Item | Value |
| --- | --- |
| Runtime 1.4 | 6.4 s |
| Runtime 1.5 | 2.8 s |

_Median of more than 56,000 runs on Runtime 1.4, and of 17 runs in a row on Runtime 1.5._

Steps hand off to each other faster too, so the longer your workflow, the more time you get back.

## The last second

A paid run has a little more to do when it ends. It settles the charge, pays the creator and writes your receipt. Before, all of that happened while your page still said "running", for about seven seconds after your result was ready.

Runtime 1.5 shows you the result first and finishes the paperwork in the background.

**Results on screen after a paid run's last step, in seconds**

| Item | Value |
| --- | --- |
| Before | 6.4–7.4 s |
| Runtime 1.5 | 1.26 s |

_Before is the median and the slowest of the paid runs we traced. Runtime 1.5 is the first paid run measured after the change._

The paperwork itself got faster as well. In our benchmark of a 12-step paid run, wrapping up now takes about a third of a second, 25 times faster than before (median of five runs each). The charge is still exact, the creator is still paid, and your balance still can't be spent twice.

## The busiest moment

Being fast is half of handling more. The other half is what happens when everyone presses Run at once.

Before, a run that arrived when Edgaze was at capacity simply failed. With Runtime 1.5, it waits its turn. Think of it as a very polite line: nobody cuts, and you don't have to stand in it.

- **Your run keeps its place.** The run page shows where you are in line and how long it should take, and your run starts by itself the moment there is room.
- **You can walk away.** Close the tab and we will email you when it's done. On a demo, leave your email and we send you the result.
- **Plus runs go first,** with capacity set aside for them. Everyone moves up the longer they wait, so nobody waits forever.
- **Edgaze sizes itself.** The runtime keeps an eye on its own health and takes on more runs when it can, and fewer when it shouldn't.
- **Brief hiccups don't cost you a run.** A start that can't get through tries again on its own, and a run is never started twice.
- **You only pay for runs that happen.** If a run can't start in time, it is released and you are not charged.

And when there is room, which is most of the time, none of this adds a moment. Your run starts straight away.

## Also new since Runtime 1.4

Speed is the headline, but it isn't the whole story. Since Runtime 1.4, Edgaze has also gained:

- **Connected apps.** Workflows can act in GitHub, Slack, Gmail, Google Drive, Google Docs, Google Calendar and Google Sheets, and every run asks you to approve exactly what it may do.
- **Runs that pause instead of failing.** If a connection expires mid-run, the run waits for you to reconnect and picks up where it left off.
- **The Repeat block.** Run a step a set number of times, choose how many run at once, and decide whether one failure stops the rest.
- **Runs that survive.** Runs keep going through updates and come back from crashes, and cancelling stops a run mid-step.
- **Webhooks that don't give up.** A failed delivery is retried for up to about nine hours instead of being dropped.
- **Long runs that stay connected.** Live run pages and API streams stay connected however long the run takes, without losing a thing.
- **Honest outcomes.** A run where some steps fail but the rest deliver your results says "Completed with issues", and you only pay for the steps that finished.

## Press Run

Runtime 1.5 can't make a model think any faster. What it can do is make sure the model is the only thing you are ever waiting for.

Every workflow on Edgaze still begins the same way. You press Run. The difference is what happens next.

Now, it just runs.

## Questions about Runtime 1.5

**What is Runtime 1.5?**

Runtime 1.5 is the engine that runs every workflow on Edgaze. It starts a run a second or two after you press Run, finishes a six-step test workflow 2.3 times faster than Runtime 1.4, and puts the results of a paid run on screen about five times sooner.

**Do I need to change my workflows?**

No. Every workflow on Edgaze runs on Runtime 1.5 automatically. There is nothing to update or republish.

**Does Runtime 1.5 make AI models faster?**

No. How long a model takes depends on the model. Runtime 1.5 removes the waiting around it: starting the run, moving between steps and wrapping up.

**What happens if Edgaze is busy when I press Run?**

Your run waits in line instead of failing. The run page shows your place and an estimated wait, the run starts by itself when there is room, and you are not charged if it can't start in time.

_Figures come from our production monitoring and internal benchmarks, August to October 2026._

---

Every workflow on the marketplace opens with example inputs. Pick one and watch how quickly it gets going. [Browse workflows](https://www.edgaze.ai/marketplace)