Priced by the work it takes off your plate.
Start by proving one workflow, then scale across the desk. Every engagement is scoped to your workflows and the time they give back, not a per-seat license.
A single preparation workflow evaluated in a supervised shadow run. Agree inputs, review criteria, sample access and timing before starting.
- 1 workflow, end to end
- Cloud deployment
- Success metrics defined up front
- Audit logs included
Multiple workflows live in production, with continuous deployment of new ones every week as your operators teach Brend more.
- Unlimited workflow runs
- Continuous weekly deployment
- Role-based access & SSO
- Priority support & supervisor handoffs
For regulated environments that need Brend running entirely inside their own network or VPC, with no external dependency.
- On-prem / VPC deployment
- No third-party model-API calls
- Dedicated deployment team
- Security & compliance review
Questions, answered plainly.
What makes Datawall different from traditional RPA?
Datawall’s broader direction connects real-world evidence with digital workflows. An insurance pilot starts with agreed documents and evidence, a reviewable output and a human approval step. Field capture and system updates are scoped according to the capabilities demonstrated for that workflow.
Do we have to build any integrations?
Only where it helps. Where clean APIs exist, Datawall connects to them directly. Where they don't, Brend's screen-walking automation reads and writes to legacy interfaces the same way a person does, so it works with systems like Xactimate, Procore, Guidewire, and SAP without a complex integration project.
How does Brend learn a workflow?
Start by walking through representative examples with your operators. Agree the required inputs, outputs, exceptions and review criteria, then test the workflow against those examples before a supervised evaluation.
Is our data safe? Does anything leave our network?
Brend's models are fine-tuned from open-weight foundations and run on your own infrastructure, so when you deploy on-prem or in your own VPC, Brend makes no third-party model-API calls and your sensitive data stays inside your perimeter. The actions Brend takes are captured in audit logs.
Which industries is this for?
Any industry where the physical world meets a legacy system. We work across insurance, education, and manufacturing today, with construction next. The same Vision, RPA, and orchestration stack travels across all of them.
How long until it's running?
Timing is agreed after reviewing the workflow, data access and deployment requirements. The first milestone is a supervised shadow run. Production requires a separate readiness review and agreement on operating controls.
Start with one workflow.
Measure the time it gives back.