Skip to content
Promenaut

Promenaut joins forces with HSBC as strategic investor and design partner.Read More

For infrastructure

Will it run, scale and recover in our estate?

The questions a review asks of Promenaut, answered from the platform itself, and everything built for them.

01Your review

The questions, in the order they come.

Four services, the web interface, the API, the orchestrator and the agent workers, run as containers in private subnets with no public addresses.

  • Compute and data sit off the internetServices and data stores run in private subnets with no public addresses.
  • Queue-driven service architectureWork moves between the API, orchestrator and workers as queued jobs on Redis rather than direct calls between services, and a job held by a process that stops is picked up again, so a slow or restarting service delays work instead of dropping it.
  • Platform event busServices publish progress to Redis channels which the API fans out to connected browsers, so a worker reporting progress does not need to know who is listening.

The full answer is in How Promenaut Runs in Your Estate.

Each service on the signal that matters for it: the API on processor load and open real-time connections, the orchestrator on the depth of the workflow queue, and agent workers on the depth of the agent task queue, which the platform publishes itself.

  • Each service scales on its own signalServices scale on the signal that matters for each: the API on processor load and open real-time connections, the orchestrator on processor load and on the depth of the workflow queue and of the platform job queue, and agent workers on the depth of their two task queues together, one for agents that call models and one for deterministic agents, which the platform publishes itself.
  • Horizontally scaled workersAgent execution runs in worker services separate from the API, scaled by adding replicas on queue depth rather than by making one process bigger, with a budget per model route that is shared across every worker, so a burst against one provider does not use up the allowance of another.
  • Long work does not hold an orchestrator slotWhen a workflow dispatches a team of agents, the orchestrator records the batch, checkpoints its state and releases the queue slot it was holding rather than waiting.

The full answer is in How Promenaut Runs in Your Estate.

02Everything built for it

What the platform does for you, layer by layer.

Services and data

  • Queue-driven service architecture
  • Layered migration system
  • Migration safety checks
  • Platform event bus
  • Services reach the database through a pool
  • Installed modules sit on read-only storage
  • One interface over local and object storage

Estate security

  • API calls and sign-in are rate limited
  • Request bodies are limited before sign-in is checked
  • A skill script runs in the sandbox runtime the install chooses

Scaling and recovery

  • Each service scales on its own signal
  • A failed or abandoned job runs again
  • A stalled workflow is noticed and restarted
  • Horizontally scaled workers
  • Work that failed everything has somewhere to go
  • Live update connections are bounded
  • Each model route has its own token and request budget
  • A workflow waits for model capacity instead of failing
  • Workflows can run on synthetic model responses
  • Guardrail limits measured, not assumed

Builds and releases

  • Content-addressed image builds
  • Candidate and released are separate registries
  • A client release with a fixable critical flaw fails
  • Releases are cut, tested and finished on a release branch
  • One feature release at a time, patches from a shipped version
  • Release rulesets applied from code
  • A release image says exactly what it was built from
  • Profile lock files
  • Version bumps derived from commits
  • Release notes written from the tickets in a release
  • Web first-load chunking with a build-time loop check

Deploying environments

  • A client can run it in its own account
  • A merge deploys the internal environments
  • A client deploy is a reviewed change
  • Each release is rehearsed through the client pipeline
  • A deploy can be rolled back
  • Tearing down an environment needs approval
  • A surface can be switched on per environment
  • Staging only moves forward unless its database is reset
  • Test environments cannot drift from what they mirror
  • A deploy checks every artifact before changing anything
  • Each install gets the reference data meant for it
  • Schema changes land before new code runs

Operations and observability

  • A fixed set of operator actions against running infrastructure
  • Closing intake and changing capacity, separately
  • Platform X-ray operator console
  • Tracing and metrics
  • Infrastructure alarms
  • A service on a different build is flagged
  • The platform notices stalls and backlogs before a person does
  • What an environment is really running
  • An operations console for running work and the agent fleet
More on Infrastructure →

Weighing us against the tools you already know? See how we compare, with sources →

03The pack

The full answers, written for you.

How Promenaut Runs in Your EstateAbout 20 minutes

Promenaut Platform InternalsAbout 60 minutes, in four parts that stand alone

Get the infrastructure pack

Bring your platform team.

Plan how Promenaut runs, scales and recovers in your own cloud account.

Plan a deployment in your account