Before you book.

Question 1

Who runs the infrastructure?

Accepted Answer

We do. GapHarness is fully managed — we host the runtime, the workers and the task queues, so there is nothing for you to deploy, scale or patch. You define workflows and agents; we run them, keep the execution history and absorb the retries.

Question 2

Can a human approve a step before it proceeds?

Accepted Answer

Yes. Any workflow can include a human approval step: the execution checkpoints and waits, the reviewer sees the pending step with its inputs, and approving or rejecting resumes the run down the corresponding branch. Waiting costs nothing and holds for as long as you need.

Question 3

Do agents have to be defined in code?

Accepted Answer

No — an agent can be defined entirely from the UI, or in code with the SDK, and the two produce the same definition. Teams commonly draft in the UI and move the definition into their repo once it stabilises.

Question 4

Can workflows and agents call each other?

Accepted Answer

In both directions. A workflow step can invoke an agent, and an agent can invoke a workflow as one of its tools — including nested ones. Each call appears as a child execution in the parent's step graph, so one trace covers the whole chain.

Question 5

Can we bring our own MCP servers, skills and memory?

Accepted Answer

Yes — connect your own MCP servers and their tools become available to any agent, write your own skills to package the tools and prompts your team keeps reusing, and create memory stores scoped to whichever agents should share them. Nothing is a fixed catalogue: the library is yours to extend.

Question 6

Can both be scheduled?

Accepted Answer

Yes — schedules attach to workflows and to agents alike, on a cron expression in the timezone you choose, with concurrency caps and a catch-up policy per schedule. The same definition stays callable over the API at the same time.

Question 7

Which models are supported?

Accepted Answer

Any provider you hold a key for, plus self-hosted endpoints. Models are bound per agent and per environment, so a revision can be promoted without changing its model, or re-pointed without a code change.

Question 8

How are long-running workflows handled?

Accepted Answer

Steps are checkpointed, so a workflow can wait on a human approval or an external webhook for days and resume where it stopped. Retries replay from the last durable checkpoint with the original inputs.

Question 9

What does it replace?

Accepted Answer

Typically a queue, a cron box, a bespoke agent harness and three dashboards you maintain yourself. Teams keep their existing orchestrators for data pipelines and move agentic work here.

New - Agents and workflows in one runtime. Book a demo today

Before you book.

Workflows & Agents