Running Custom long-running cloud agents · for work measured in weeks

Built for the long run.

Most AI answers in seconds. Ours works for days: carrying your company's hardest projects end to end, through the failures and the 3 a.m. errors, until the work is done and verified.

Work board · example jobs, simulated Running Verifying Needs sign-off Done

§ 01 — The gap

Copilots answer in thirty seconds. The work that actually moves a company — migrations, audits, reconciliations, rebuilds — takes weeks, hundreds of decisions, and someone who won't stop at the first error. Nobody on your team has a spare month. So we build the agent that does.

§ 02 — Seconds vs. days

Now zoom out.

Timeline shows 30 seconds

Illustrative run. The same run is replayed step by step below.

  • After thirty seconds, a copilot has answered; the agent has just finished reading the brief.
  • After ten minutes, the agent has mapped six systems and filed a plan.
  • After six hours, it is writing, testing and fixing while everyone has gone home.
  • After thirty-six hours, it has hit a real problem, found the cause, and kept going through the night.
  • After seventy-two hours, the work is done, verified and signed off.

§ 03 — Anatomy of a run

Watch a run.

Seventy-two hours of real-shaped work, compressed into one scroll. Pick a job: the work changes, the anatomy doesn't. Every line in the event log is something the agent does on its own.

+ Yours
Starting Elapsed 00:00:00
RUN 204 Merge an acquired company's CRM into yours HubSpot → Salesforce · 251,390 records · illustrative
01/ 08

Brief

Event log 0 events

    § 04 — Inside every agent

    An engineer that doesn't clock out.

    Every Longhaul agent is custom-built for one job at your company, and ships with the machinery to do that job for days without supervision.

    01Its own computer

    A persistent cloud machine: shell, browser, filesystem.

    It doesn't describe the work. It does it: runs your test suite, works through the vendor portal, writes the migration, reads the logs. Its desk is still there in the morning.

    02Memory that carries

    Learns your company the way a new hire does.

    Hard-won facts persist across sessions, so day nine is smarter than day one.

    03Plugged into your stack

    Works where your work already lives.

    Scoped connectors into the systems the job touches. Keys stay in a vault, never in the prompt.

    04Guardrails you ratify

    Permissions only ever get tighter.

    You sign off on exactly what it can touch. Anything irreversible waits for a person.

    05Endurance

    Runs for weeks. Survives everything.

    Continuous checkpoints mean restarts, deploys and flaky APIs are speed bumps, not the end of the run.

    06Proof, not promises

    “Done” is a claim. We ship the evidence.

    Independent verifiers check every run against the success criteria you set on day zero. Then you get the full, replayable record of every action and decision.

    § 05 — Work we take on

    If it takes your team a quarter,
    it's a job for an agent.

    Three illustrative work orders. Yours will be stranger — that's the point.

    Work order№ 204

    Post-acquisition migration

    CRMs & ERPs, merged into one of each

    Merge an acquired company's systems into yours, without breaking a single live deal.

    Usually
    A consultant team
    Records
    ~250k
    Needs sign-off
    Cutover
    Verified by
    Counts & pipeline $
    Status
    Done ✓
    Work order№ 311

    End-to-end operations

    open insurance claims, first notice to close

    Work a claims backlog end to end, with people handling only the exceptions.

    Runs
    Thousands, concurrently
    Exceptions
    To adjusters
    Needs sign-off
    Payments over $10k
    Verified by
    Ledger & audits
    Status
    Done ✓
    Work order№ 418

    Physical-world research

    candidate formulations → one verified result

    Run a closed experimental loop for weeks: design, run, measure, learn, repeat.

    Experiments
    1,152 wells
    Loop
    Nightly batches
    Needs sign-off
    Reagent spend
    Verified by
    Replicates
    Status
    Done ✓

    § 06 — Working with us

    From briefing to production in a month.

    Week 0

    Briefing

    We sit with the people who do the work today and map one painful, long-running workflow end to end, including the ugly edge cases.

    Weeks 1–3

    Build & harden

    We build a custom agent on your stack, then run it in a sandbox against your real data until it finishes the job cleanly, every time.

    Week 4 →

    In production

    It goes to work with approvals exactly where you want them. We run alongside, tune it, and scale it to the next job.

    § 07 — No black box

    Built on an open runtime.
    Yours to inspect.

    Our agents run on OpenMA, the open-source runtime we wrote specifically for agents that run for days. Durable sessions, sandboxed computers, scoped credentials, approvals and full event trails are infrastructure, not promises.

    • ↳ Open source: read every line that touches your data
    • ↳ Model-agnostic: the best model for each job, not one vendor
    • ↳ Your cloud or ours: self-host when you need to
    View the runtime on GitHub ↗

    What's the hardest thing
    on your roadmap?

    Tell us about the project nobody has time to finish. We'll come back with a scoping plan: what the agent would do, how long it would run, and exactly where a human stays in the loop.