WARDALE
HOW WARDALE FITS

Keep your existing systems. Add clear authority around AI work.

WARDALE is designed to work alongside your cloud, CRM, identity provider, agent framework, workflow platform or payment network. It focuses on whether AI is authorised to act, where approval is required and what should be verifiable afterwards.

Build my integration blueprintChoose how WARDALE fitsFor technical teams

Where WARDALE sits

YOUR PEOPLE & BUSINESS RULES → WARDALE AUTHORITY → AI WORKERS & AGENTS → YOUR EXISTING SYSTEMS → VERIFIABLE EVIDENCE WHEN REQUIRED
Your organisation stays in charge

Your people define the business responsibility, limits and approval points.

WARDALE checks the authority to act

Before supported governed actions, WARDALE can evaluate whether the action is allowed, needs approval, must be changed or should be stopped.

Your systems still do their jobs

Salesforce can remain Salesforce. AWS can remain AWS. Visa or Mastercard can remain the payment rail. WARDALE governs the AI authority around them.

Evidence is a defined boundary, not a blanket storage claim

Supported decisions and actions can produce verifiable receipts. Storage location, retention period and access are configured separately according to the deployment and customer policy.

Choose the way you want to use WARDALE

Use WARDALE with AI we already have

Your organisation already uses agents, copilots or automated workflows.

You define: Which AI systems are in use, what they are expected to do, who owns the outcome and where the highest-risk actions are.

WARDALE gives you: A clear operating map showing what the AI may do, what needs approval, how authority can be changed or revoked and what evidence should be produced.

Continue →Add WARDALE workers to our business

You want digital workers for specific business duties.

You define: Your industry, the job to be done, the systems involved and the result you expect.

WARDALE gives you: A recommended worker set, the duties of each worker, the systems they need and the limits under which they should operate.

Continue →Connect WARDALE to our applications

Your product or internal platform needs WARDALE to check, control or verify important AI actions.

You define: Which application is calling WARDALE, what action is being requested and who is accountable for that action.

WARDALE gives you: A clear integration pattern and a hand-off to the technical contract your engineering team needs.

Continue →Use WARDALE for AI payments and purchasing

AI may buy, pay, refund, approve invoices, procure from suppliers or trigger other transactions.

You define: What may be purchased or paid, spending limits, approved counterparties and when a human must approve.

WARDALE gives you: A transaction-control model that keeps the payment rail in place while WARDALE governs whether the AI is allowed to act.

Continue →Build the plan myself first

You want to define the use case before involving anyone else.

You define: Your answers stay in the browser-based planner rather than being submitted through the planning form.

WARDALE gives you: A self-service blueprint covering the outcome, systems, owner, AI actions, approval points and evidence boundary.

Continue →

What should be decided before production

1. Business outcome

What does the organisation actually want AI to accomplish?

2. People and systems

Which people, AI workers, applications and transaction systems are involved?

3. Authority and limits

What may happen automatically, what needs approval and what is outside the current mandate?

4. Evidence requirement

What needs to be verifiable after an important decision or action?

5. Retention and access

Where should evidence live, who may access it and how long should it be retained?

6. Technical hand-off

Translate the agreed business model into the integration contract your engineering team needs.

For technical evaluators

Engineers can inspect APIs, machine-readable discovery, verification and evidence interfaces from the Developer area after the business integration pattern is clear.

Open developer information

Ready to move beyond evaluation?

If every item below is clear, the pre-production planning stage has done its job.

  • We know the business outcome WARDALE is being considered for.
  • We know whether we are governing existing AI, adding WARDALE workers, connecting an application or governing transactions.
  • We know which systems and AI workers are involved.
  • We know who inside the organisation is accountable.
  • We know which actions can happen automatically and which need approval.
  • We know the limits that should apply.
  • We know what evidence should be produced after important actions.
  • We have decided where evidence should be retained and for how long, or have marked that as a deployment decision.
  • Our technical team knows where to find the detailed integration contract if we proceed.