Evidence tier Source Confirmed · 4 captures on record
What the publisher says
As described on AWS Marketplace.
When operating DBOS durable workflows in production, we strongly recommend connecting your application to Conductor. Conductor is the control plane for your durable workflows, providing:
- High availability: In a distributed environment with many executors running durable workflows, Conductor automatically detects when a workflow is interrupted (for example, if its executor disconnects or crashes) and recovers the workflow to another healthy executor.
- Workflow and queue observability: Conductor provides dashboards of all active and past workflows and all queued tasks as well as real-time workflow visualization.
- Workflow and queue management: From the Conductor dashboard, you can pause any workflow execution, start any stopped or enqueued workflow, or restart any workflow from a specific step. This is useful for rapidly responding to incidents or debugging.
- Managed Retention Policies: From the Conductor dashboard, manage how much workflow history each of your applications should retain and for how long to retain it.
- Observability Integrations: Conductor exposes metrics about your applications' workflows, steps, and executors from a Prometheus-compatible endpoint, so you can monitor your DBOS applications in Datadog, Grafana, or any other tool that understands the OpenMetrics format.
Highlights
Highlighted by the publisher on AWS Marketplace.
Distributed workflow recovery: In a distributed environment with many executors running durable workflows, Conductor automatically detects when a workflow is interrupted (for example, if its executor disconnects or crashes) and recovers the workflow to another healthy executor.
Workflow and queue observability: Conductor provides dashboards of all active and past workflows and all queued tasks as well as real-time workflow visualization.
Managed Retention Policies: From the Conductor dashboard, manage how much workflow history each of your applications should retain and for how long to retain it.
Agent build and provenance
See the full provenance
The layer-by-layer build, the evidence behind each claim, the risk basis and the cross-marketplace links are open to any account. Some rows are disclosed, some the source leaves Unknown; a free account shows you which.
Plans and pricing as listed
2 listed- Units
- Units
Refund terms
As stated by the publisher on AWS Marketplace.
Please reach out to support@dbos.dev for information about refunds
Sources
Linked repositories
Unknown means this listing does not publish a repository. It is not a statement that the code is closed, and a linked repository is not a claim that the publisher wrote it: the registry computes that relationship privately and does not publish it.
Evidence risk is the share of the build you cannot see before you deploy, not a security rating. Sign in to see the layer-by-layer basis for this band.