Who is behind Deliverd.

AI agents are good at proposing what to do and getting better at doing it. What they cannot do is take responsibility. A refund, a deployment, a credit decision or a message to a customer still needs a person who can say yes, and an organisation that can show later who said it and on what basis.

Deliverd is that layer. An agent makes one call when it needs a person, the right person answers wherever they are, and the record of who decided what is kept as it happens. We build it for teams putting agents into real work, and for the people who have to sign that work off.

We are early, and we would rather you heard it from us. Deliverd is built by a small independent team in Dublin. We do not hold SOC 2 or ISO 27001 yet. We do not show customer logos or quotes we have not been given. The security page lists what the product does not do yet, so you can find out before a procurement review rather than during one.

What we can show is the work. The SDKs, the CLI and Deliverd Screen are published from public repositories. Evidence packs are signed with a key anyone can fetch from /.well-known/deliverd-evidence-key, so a copy can be checked without trusting us. And everything that ships goes on the changelog.

Every message through the contact form is read by someone who can act on it. Send us your security questionnaire and we will answer it against the security page. A data processing agreement under Article 28 of the GDPR is available on request. If you want to prove one use case before committing, the governed AI pilot runs one real workflow for 30 to 45 days.