— Automation Cloud

Coming soon

Host and run automations at scale.

Automation Cloud is UBIO’s platform for running A3-powered workflows in production — the same stage scripts and playbooks you learn locally, executed deterministically without an LLM in the loop.

Not available yet. We are building the managed runtime that pairs with the open-source A3 toolchain. The capabilities below describe the direction; timelines and pricing will be announced later.
— Planned platform

What Automation Cloud is for.

Today you author workflows in git, learn sites in the UI, and run sessions on your own infrastructure. Automation Cloud will close the gap to production: schedule runs, fan out across sites and datasets, and operate thousands of deterministic playbacks from one control plane.

Hosted execution for learned workflows at production scale.
RUNTIME

Managed A3 runner.

Execute workflows on UBIO-hosted runners with Playwright, the stage engine, and your project layout — no bespoke worker images to maintain.

DETERMINISTIC

LLM-free replay.

Production runs use learned stages only; models stay in the learning phase, keeping cost and latency predictable at high concurrency.

TARGETS

Sites & datasets.

Declare per-site input fixtures and scale-out targets from config — the same sites/<hostname>/ model you use in development.

ORCHESTRATION

Queues & schedules.

Trigger runs on a cron, from an API, or via webhooks; configure concurrency limits, retries, and backoff for flaky targets.

SECRETS

Environment & credentials.

Inject API keys, proxy settings, and per-tenant secrets without committing them to git — scoped to workflows and environments.

OBSERVABILITY

Runs, logs & traces.

Central history for each execution: structured logs, Playwright traces, stage match failures, and output artifacts for downstream systems.

ARTIFACTS

Outputs & playbooks.

Collect validated workflow outputs and optional playbook snapshots after runs — ready for diffing, warehousing, or audit.

INTEGRATION

API & deploy hooks.

Connect CI/CD so a merged workflow repo promotes a new version; invoke runs from your product backend with typed inputs and outputs.

GOVERNANCE

Teams & environments.

Separate dev, staging, and production; role-based access to workflows, run history, and cloud configuration.

— Config sketch

Familiar from local runs.

Infrastructure config is likely to mirror what you already declare for self-hosted runners — workflow path, runtime provider, concurrency, and per-site inputs — so promoting to the cloud is a small step, not a rewrite.

Planned: cloud runtime Configuration
infra/ubio-runner.yaml
version: '1'
workflow: src/workflows/scrape-rates/scrape-rates.workflow.ts
runtime:
  provider: ubio-automation-cloud
  mode: deterministic
  llmInLoop: false
  concurrency: 60
targets:
  - site: be-synxis-com
    inputs: src/workflows/scrape-rates/sites/be-synxis-com/inputs.yaml
outputs:
  artifactDir: ./.runs/scrape-rates
Build locally today. Use the Docs to scaffold a workflow, the Product tour to learn sites in the UI, and Deploy for self-hosted patterns until Automation Cloud opens.